On Mon, Dec 17, 2007 at 09:50:37AM -0600, Michael Halcrow wrote:
> > With ecryptfs-utils-33, and 2.6.23.9, we don't even get that far:
> > 
> > # mount -t ecryptfs -o 
> > key=openssl:keyfile=/home/jayjwa/crypto/atr2-jayjwa-key.pem
> > /var/cache/ecryptfs/100 /home/jayjwa/.ecrypt_mp
> > Passphrase:
> > Select cipher:
> > Selection: 1
> > Select cipher:
> > Selection: 2
> > ...
> 
> I rewrote the cipher selection code for release 33. It parses
> /proc/crypto and the contents of /lib/modules/`uname
> -r`/kernel/crypto/ for the available ciphers. Unexpected contents
> for either location may cause this strange behavior; I will run some
> more tests to make sure everything works right for corner cases.

Release 35 has more reasonable cipher detection/selection code in
it. If you are still having problems, mount with '-o verbose' to get
more details in your syslog and send that portion of your syslog to
me.

Thanks,
Mike

Attachment: signature.asc
Description: Digital signature

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
eCryptfs-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecryptfs-users

Reply via email to