encfs-1.5 unable to (re)mount filesystem after unmounting it

[Markus.Ueberall@…]

With the above configuration, it's currently impossible to mount an existing encrypted filesystem; the following test case fails:

$ mkdir -p ~/test/fs.crypt ~/test/fs; encfs ~/test/fs.crypt ~/test/fs
[...]
$ touch ~/test/fs/file.ext; ls -la ~/test/fs.crypt | grep "\-\-"
-rw-r--r--  1 ueberall  staff  1073 16 Feb 22:47 .encfs6.xml
-rw-r--r--  1 ueberall  staff     0 16 Feb 22:54 U9Ua6b8iKFBtuyTYUBJU9P02
$ umount ~/test/fs; encfs ~/test/fs.crypt ~/test/fs
22:55:56 (FileUtils.cpp:375) Archive exception: class version
[...] (.encfs6.xml found, but cannot be loaded; i.e., old contents are inaccessible)

(NB this may be related to an intermittent boost update (to v1.42.0) which happened after the encfs setup for OS X 10.6.2)

[chris.madden@…]

Cc Me!

[valient@…]

Replying to Markus.Ueberall@…:

(NB this may be related to an intermittent boost update (to v1.42.0) which happened after the encfs setup for OS X 10.6.2)

Boost 1.42 has apparently broken backward compatibility with the serialization/archive format. This silently brakes encfs's configuration file. Any new encfs filesystem created with a build against boost 1.42 will not load by any version of encfs. After reverting to boost 1.41, the config file still needs to be manually edited to be recognized.

Macports should restrict encfs to boost 1.41 if possible.

See also: ​http://bbs.archlinux.org/viewtopic.php?pid=721858

[valient@…]

Cc Me!

[ryandesign@…]

Replying to valient@…:

Macports should restrict encfs to boost 1.41 if possible.

The only way that would be possible would be to create a new boost141 port. Wouldn't it be better to fix boost 1.42 though? Are the developers of boost working on that?

[and.damore@…]

Replying to ryandesign@…:

The only way that would be possible would be to create a new boost141 port. Wouldn't it be better to fix boost 1.42 though? Are the developers of boost working on that?

Is there anything against creating such a temporary port?

[and.damore@…]

Cc Me!

[valient@…]

Replying to ryandesign@…:

Are the developers of boost working on that?

Boost 1.43 does not appear to be fixed. Here is the open ticket:

​https://svn.boost.org/trac/boost/ticket/3990

In the archlinux link above is a post with a short patch that fixes the problem by reverting the shortening of version type in boost/archive/basic_archive.hpp.

[macports@…]

Cc Me!

[valient@…]

Workaround added to Encfs-1.6 release. See ticket #25427