Encfs on current
 

Just a warning / question about Encfs on Slackware current. I doesn't work due to the upgrade to boost 1.4.2.

Has anyone found a work-around?

I ran encfs on an old install of 13.0 to get at my data, but I'd prefer to access it right from current. A big warning: if you try to access your encrypted data on current it will corrupt your encfs6.xml file and I don't know if it is recoverable (I had a backup of mine).

Yes. I just tried encfs and have the same problem.

Found this bugreport which has more info about the problem:
http://code.google.com/p/encfs/issues/detail?id=60

It seems the boost guys changed something about serialization in 1.4.2.

Im back to 1.4.1 now, that works for me.
I used the slackbuild for boost from slackware-current/source/l/boost, works
without changes for 1.4.1 and then added boost to my slackpkg blacklist ...

After that you probably have to recompile encfs because of shared library error :)

I think I read somewhere that parts of KDE 4.4 need boost 1.4.2 (not 1.4.1) so KDE users might need to choose between encfs and KDE. I'm going to leave encfs behind because it has shown itself to be a bit risky to use:
1) website puts requirements as boost 1.34 or higher, with no warning about the latest boost library
2) it corrupts the xml file needed to decrypt your file system if you use the wrong library

Damn, I think you are right with KDE. It's compiled against boost 1.4.2,
so downgrading boost breaks some stuff, like Akonadi ...

Did anybody already reported to Pat about this issue ? Is going to be fixed somehow ? I've found some but ugly fixes to boost 1.42 sources.

JFYI even the bleeding-edge distro like Archlinux has downgraded to boost version 1.41, because it breaks more things. They have in repos KDE 4.4.3 but built against this older library version so I guess it would work on Slackware also.

Does it break anything except encfs? Since it isn't an official Slackware package, whereas KDE is, I'd guess that Slackware 13.1 will stick with 1.42.