Re: Two keys for the same encrypted file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



kinto wrote:
> Alle 18:31, domenica 9 ottobre 2005, Jari Ruusu ha scritto:
> > Above "head -c 15 /dev/urandom | uuencode -m - | head -n 2 | tail -n
> > 1" is completely unnecessary and unused here.
> 
> Ok, but why? In LoopAes.README this is the procedure for a physical
> device. Aren't it valid for a file backed loop?

Because the "head ... | uuencode ... | head ... | tail ..." pipe sends a
random passphrase to stdin of losetup. By default, losetup prompts and reads
a passphrase from controlling terminal, not stdin. If losetup is given a
"-p0" command line parameter, then losetup reads a passphrase from stdin.

In your example, if losetup were to read a random passphrase from stdin,
then losetup would not be able to decrypt the gpg encrypted key file. Random
passphrase is not same as the one you used to encrypt the key file.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux