Comment 3 for bug 1359776

Thanks, Germar, for your reply. Unfortunately I don't see how I could tell backintime to use non-default encryption parameters without resorting to manually building a new encfs backup destination. It'd take some digging to find the parameters used by backintime and adapting them.

IMHO the default settings shouldn't fail for obscure technical reasons. Maybe the default for new encfs backups could be changed to stream encoding of filenames? Additionally a short security notecould be added informing the user that a more secure filename encryption is possible but that it artifically restricts filename length. (Maximum filename length is even further reduced due to utf-8 encoding. Bytes vs. characters)

I've also noticed that encfs has moved. So here's the updated link to the encfs issue: https://github.com/vgough/encfs/issues/7