gocryptfs/internal, branch v2.5.1

reverse: lookupDiriv: use deriveDirIV helper

2025-01-18T18:57:44+00:00

reverse: advance mtime & ctime for virtual files by 10 seconds

2025-01-18T13:13:52+00:00

With inode number reuse and hard links, we could have returned wrong data for gocryptfs.diriv and gocryptfs.xyz.longname files, respectively (https://github.com/rfjakob/gocryptfs/issues/802). Now that this is fixed, ensure that rsync and similar tools pick up the new correct files by advancing mtime and ctime by 10 seconds, which should be more than any filesytems' timestamp granularity (FAT32 has 2 seconds).

passfile: drop byte counter from trailing garbage warning

2024-12-04T18:06:56+00:00

We don't know the exact value as we only read 2kiB. Relates-to: https://github.com/rfjakob/gocryptfs/discussions/882

Report inode number for the root node

2024-11-11T21:33:07+00:00

Now that https://github.com/hanwen/go-fuse/issues/399 has landed we can report an inode number for the root node. Fixes https://github.com/rfjakob/gocryptfs/issues/580

reverse: fix import sorting in root_node.go

2024-11-11T21:33:07+00:00

ctlsock: delete colliding orphaned socket file

2024-09-03T14:01:46+00:00

Detect and delete an orphaned socket file that collides with the ctlsock we want to create. Fixes https://github.com/rfjakob/gocryptfs/issues/776

ctlsocksrv: move Listen() call here

2024-09-02T14:31:23+00:00

Prep for solving https://github.com/rfjakob/gocryptfs/issues/776

reverse: fix force_owner

2024-08-23T20:32:46+00:00

Fixes https://github.com/rfjakob/gocryptfs/issues/809

readpassword: show where stdin is connected

2024-08-23T10:29:12+00:00

Should make debugging situations like https://github.com/rfjakob/gocryptfs/issues/852 Empty stdin in mkinitcpio hook easier. Examples: $ echo -n "" | ./gocryptfs -init a Choose a password for protecting your files. Reading Password from stdin (connected to "pipe:[749878]") Got empty Password from stdin $ ./gocryptfs -init a < /dev/null Choose a password for protecting your files. Reading Password from stdin (connected to "/dev/null") Got empty Password from stdin $ ./gocryptfs -init a < /dev/zero Choose a password for protecting your files. Reading Password from stdin (connected to "/dev/zero") fatal: maximum password length of 2048 bytes exceeded $ ./gocryptfs -init a < /dev/full Choose a password for protecting your files. Reading Password from stdin (connected to "/dev/full") fatal: maximum password length of 2048 bytes exceeded $ jakob@brikett:~/go/src/github.com/rfjakob/gocryptfs$ ./gocryptfs -init a < /dev/urandom Choose a password for protecting your files. Reading Password from stdin (connected to "/dev/urandom") Your master key is: 4e45a317-595d8a2d-46493a30-97de86ef- 540c7364-f0acc297-dd6f2592-7d9a5c97 If the gocryptfs.conf file becomes corrupted or you ever forget your password, there is only one hope for recovery: The master key. Print it to a piece of paper and store it in a drawer. This message is only printed once. The gocryptfs filesystem has been created successfully. You can now mount it using: gocryptfs a MOUNTPOINT

stupidgcm: detect AES-GCM acceleration like crypto/tls

2024-06-06T08:07:08+00:00

Instead of just looking for AES, also look for PCLMULQDQ, like crypto/tls does. Fixes: https://github.com/rfjakob/gocryptfs/issues/822