Bug 254905 - encfs incompatible after update
Summary: encfs incompatible after update
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: Other (show other bugs)
Version: Alpha 2
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User sLJ7K2dvxj
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 408791
  Show dependency tree / graph
 
Reported: 2007-03-15 12:00 UTC by Takashi Iwai
Modified: 2008-07-14 06:43 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Takashi Iwai 2007-03-15 12:00:47 UTC 
encfs can no longer mount the old encrypted directory after upgrading from 10.2.

% encfs ~/.memo/ ~/memo/
EncFS Password: xxxxxx
Error decoding volume key, password incorrect

It seems like the upgrade of openssl affects the behavior.  Downgrading openssl (and encfs.rpm to remove some dependency) resolves the problem.

The packages used are:
encfs-1.3.2-3
openssl-0.9.8e-2
Comment 1 Forgotten User sLJ7K2dvxj 2007-03-21 10:01:59 UTC 
Here's some info from the author:

http://sourceforge.net/mailarchive/forum.php?thread_id=31842732&forum_id=38877

Takashi, can you please post output of

  encfsctl info ~/.memo

?
Comment 2 Takashi Iwai 2007-03-21 10:37:46 UTC 
It's not the case, I'm afraid...

% encfsctl info ~/.memo

Version 5 configuration; created by EncFS 1.2.2 (revision 20040813)
Filesystem cipher: "ssl/blowfish", version 2:1:1
Filename encoding: "nameio/block", version 3:0:1
Key Size: 160 bits
Block Size: 512 bytes
Each file contains 8 byte header with unique IV data.
Filenames encoded using IV chaining mode.
Comment 3 Forgotten User sLJ7K2dvxj 2007-04-12 07:14:32 UTC 
It's been confirmed to be a bug in openssl.

This commit should fix it:
   http://cvs.openssl.org/chngview?cn=15978

Compliments to Valient Gough for tracking it down.

Closing bug.