Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows : Format 3 modification timestamp issue #54

Open
Achim16 opened this issue Mar 6, 2018 · 1 comment
Open

Windows : Format 3 modification timestamp issue #54

Achim16 opened this issue Mar 6, 2018 · 1 comment

Comments

@Achim16
Copy link

Achim16 commented Mar 6, 2018

The following strange issue has been observed using Win7 SP1 Enterprise ans SecureFS 0.81 (same in 0.80, 0.73) / WinFsp 1.3 (also with WinFsp 1.2).
In essence file format 3 produces strange modification timestamps (creation & last access dates are fine), see below .
I understand that this format stores timestamps, unfortunately I couldn't reproduce this behaviour though on Win7 SP1 Ultimate (works as expected there) nor does the logfile indicate anything (to me)
When for instance copying files to SecureFS folder, one for a half a second sees in explorer the expected filedate before it refreshes and shows blank
I enclose the filesystem itself (password : test / lockfile needs to be deleted first,sorry) and the logfile.
This issue of course can be specific to the setup of the (work) PC but maybe you've got an idea

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

h:\Crypt\SecureFS>securefs v
securefs 0.8.1
Crypto++ 5.65
WinFsp 1.3

Hardware features available:
SSE2: true
SSE3: true
SSE4: false
AES-NI: false
CLMUL: false

h:\Crypt\SecureFS>securefs c --format 3 e:\SecureFS
Password:
Again:

h:\Crypt\SecureFS>securefs m e:\SecureFS W: --log b:\log --trace -v
Password:
[Trace] [0000000000001448] [2018-03-06 12:52:18.267997300 UTC] Opening file o
n a NTFS volume
[Verbose] [0000000000001448] [2018-03-06 12:52:18.272997300 UTC] Setting the
password key derivation function to scrypt
[Verbose] [0000000000001448] [2018-03-06 12:52:18.623997300 UTC] Raising the
number of file descriptor limit to 65535
[Verbose] [0000000000001448] [2018-03-06 12:52:18.627997300 UTC] Filesystem p
arameters: format version 3, block size 4096 (bytes), iv size 12 (bytes)
[Verbose] [0000000000001448] [2018-03-06 12:52:18.627997300 UTC] Master key:
253b5cd7eda0ec6ff3cc3b67cf48edc0b3fd70605d0f65c300747682893b0cb5
[Trace] [0000000000001448] [2018-03-06 12:52:18.628997300 UTC] Opening file o
n a NTFS volume
Filesystem mounted successfully
The service securefs has been started.
Filesystem unmounted successfully
The service securefs has been stopped.

w:>dir w:\

log.txt
SecureFS_filesystem.zip

Verzeichnis von w:\

01/01/1601 01:00 16 xxx.txt
01/01/1601 01:00 16 yyy.txt
2 Datei(en), 32 Bytes
0 Verzeichnis(se), 129,510,547,456 Bytes frei

@netheril96
Copy link
Owner

So the issue occurs under Windows 7 Enterprise but not Ultimate? I am afraid that I don't have the resources to test it then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants