Thanks for reporting. This is due to fuse not passing through the
noatime parameter to the filesystem implementation, so CryFS can't
figure out whether noatime is enabled or not. However, to alleviate the
problem a bit, the default behavior of CryFS will be switched from
strictatime to relatime in the upcoming 0.10 release series.
On 22/09/17 08:56, Kiko Piris wrote:
Package: cryfs
Version: 0.9.7-2
Severity: normal
If the cryfs filesystem is mounted with noatime, it should not modify files’
access times when they are read:
$ mount | grep cryfs
cryfs@/home/kiko/Dropbox/safe/.cryfs on /home/kiko/Dropbox.safe type fuse.cryfs
(rw,nosuid,nodev,noatime,user_id=1000,group_id=1000,allow_other)
^^^
$ stat Dropbox.safe/.placeholder
File: Dropbox.safe/.placeholder
Size: 60 Blocks: 0 IO Block: 16384 regular file
Device: 2fh/47d Inode: 41 Links: 1
Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko)
Access: 2017-09-22 09:30:51.261363123 +0200
^^^
Modify: 2010-06-10 10:38:53.0 +0200
Change: 2017-09-20 19:17:16.072335331 +0200
Birth: -
$ cat Dropbox.safe/.placeholder
# DO NOT EDIT OR REMOVE
# This file is a simple placeholder
$ stat Dropbox.safe/.placeholder
File: Dropbox.safe/.placeholder
Size: 60 Blocks: 0 IO Block: 16384 regular file
Device: 2fh/47d Inode: 41 Links: 1
Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko)
Access: 2017-09-22 09:48:34.843560115 +0200
^^^
Modify: 2010-06-10 10:38:53.0 +0200
Change: 2017-09-20 19:17:16.072335331 +0200
Birth: -
Obviously, the corresponding block file in the encrypted directory also gets
modified (and needlesly synced to Dropbox).
Thanks.