first level gocryptfs.diriv file is always same when init in reverse mode about gocryptfs HOT 2 CLOSED

Hi, yes, you are correct, the first level gocryptfs.diriv is always the same.

As seen in https://nuetzlich.net/gocryptfs/reverse_mode_crypto/#derived-ivs , it's computed as

sha256(path + \0 + DIRIV)

And on the first level, path = "", so we have only

sha256(\0 + DIRIV)

In bash:

$ printf "\\0DIRIV" | sha256sum 
a8f7bac432ddc1cb3dc74e684d6ae48bc71acbd28683297e5e870270be90f248  -

That matches what we see in gocryptfs.diriv:

$ hexdump -C b/gocryptfs.diriv 
00000000  a8 f7 ba c4 32 dd c1 cb  3d c7 4e 68 4d 6a e4 8b  |....2...=.NhMj..|
00000010

from gocryptfs.

As for your question, no, this is not a problem. The only important thing thing about gocryptfs.diriv (Dir IV = Directory Initialisation Vector) is that you use different values for different directories within one file system.

from gocryptfs.