Ok, I got it working. It is though not because of Fuse which I updated from version 2.7.2 to 2.7.3 but because I created the encfs folder with cryptkeeper before which might have used the paranoia option by default, I'm not sure. Creating with "encfs <folder> <folder>" and then selecting standard mode works fine. Are there combinations of settings which can give this result or is this still a bug which then probably occurs under certain conditions?
Below are the outputs of encfsctl info for a folder created with cryptkeeper and the one that works that is created using standard mode cryptkeeper: Version 6 configuration; created by EncFS 1.4.2 (revision 20080813) Dateisystem-Verschlüsselung: "ssl/aes", Version 2:1:0 (verwende 2:1:1) Dateinamenkodierung: "nameio/block", Version 3:0:0 (verwende 3:0:1) Schlüssellänge: 256 Bits Blockgröße: 512 Bytes, enthält 8 Bytes MAC-Kopf Jede Datei enthält 8 Bytes Vorspann mit einmaligen IV-Daten. Dateinamenkodierung benutzt IV-Verkettungsmodus. Dateidaten-IV ist mit Dateinamen-IV verkettet. standard mode: Version 6 configuration; created by EncFS 1.4.2 (revision 20080813) Dateisystem-Verschlüsselung: "ssl/aes", Version 2:1:0 (verwende 2:1:1) Dateinamenkodierung: "nameio/block", Version 3:0:0 (verwende 3:0:1) Schlüssellänge: 192 Bits Blockgröße: 1024 Bytes Jede Datei enthält 8 Bytes Vorspann mit einmaligen IV-Daten. Dateinamenkodierung benutzt IV-Verkettungsmodus. -- rsync timestamp bug on encfs/fuse https://bugs.launchpad.net/bugs/81080 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
