Protecting signing key]

[Roscoe]

loop-aes is not in the vanilla kernel sources.
dm-crypt and cryptoloop are.
cryptoloop is depreciated, use dm-crypt instead.

dm-crypt'd main advantage is that it's already in the kernel, whereas
loop-aes is a add-on. Look at the different modes of encryption
supported and make a decision from there.

I use dm-crypt for what its worth, though I wouldn't have any problems
with using loop-aes instead.

On 8/3/05, Kara <karadenizi at earthlink.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> ====
> 
> Reference:
> 
>     Subject: Re: Protecting signing key
>     Date: Tue, 02 Aug 2005 23:23:59 +0000
>     From: cdr <cedar at 3web.net>
>     To: gnupg-users at gnupg.org
> 
> > One solution (free, with full source) can be found here:
> > http://www.truecrypt.org/
> 
> What would be an equally good equivalent
> for those of us using a Linux distro?
> 
> - --
> 
> Ciao
> 
> Kara
> 
>     "As long as algebra is taught in school, there
>     will be prayer in school." - Cokie Roberts
> 
> ====
> .
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2rc2 (GNU/Linux)
> Comment: Using Fedora and Enigmail
> Comment: OpenPGP keyID and URL in Message Headers
> 
> iD8DBQFC8CZW15k+1L3RO5ARArR5AKDD5Nsh8GbxH2MSYY3m4ntizuXgWQCgtOUg
> Y0woRWQlkN+fO9EIbOda5JI=
> =/tfT
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>