rfjakob

No mountpoints inside?

Version v2.1 right? ( https://github.com/rfjakob/gocryptfs/releases/tag/v2.1 )

Hmm, looks good here: ``` $ ./gocryptfs -version gocryptfs v2.1 without_openssl; go-fuse v2.1.1-0.20210802120645-15a8bb029a4e; 2021-08-18 go1.17 linux/amd64 $ tree --inodes plain plain └── [143969475] Test └── [143969476] test.txt $ ./gocryptfs -reverse...

Can you run tree --inodes plain please?

Good point, but no: ``` $ ./gocryptfs -reverse plain cipher Password: Decrypting master key Filesystem mounted and ready. $ tree --inodes cipher/8Zscd3_NV5YtsYE8Foe-ww cipher/8Zscd3_NV5YtsYE8Foe-ww ├── [281475120680131] gocryptfs.diriv └── [143969476] Xc1BUkX5f65xYtftpodE6w ```

Wow, negative inode numbers! That's something new! What kind of filesystem is this?

Oh I see. I forgot the 2nd condition for persistent inode numbers. So https://github.com/rfjakob/gocryptfs/issues/606#issuecomment-925001282 should have read: --- The inode numbers are always unique for one reverse mount. Under the...

Yes, 281474976710655 is the max having 48 bits. Values above this are reserved for other things: * gocryptfs.diriv files * gocryptfs.longname files * files on other mountpoints I read about...

> does gocryptfs guarantee uniques inodes number in the cipher view (reverse mode) even if the data in the plain folder are on mergerfs and so doesn't guarantee unique inodes?...

Hi, nice analysis so far! But i think you have to adjust the offset in the encrypted file due to overhead (https://github.com/rfjakob/gocryptfs/blob/master/Documentation/file-format.md) Alternatively, can you run gocryptfs-xray on the encrypted...