Missing implementation of timestamp feature to set modification date on uploaded files

[cyberduck]

27aeff2 created the issue

In Cyberduck and Mountain Duck, the date created field is reported as the date modified field rather than the date modified field. This means that you cannot use synchronization software which depends on timestamps, such as FreeFileSync. This is not a defect in Cryptomator in this case, as opening the same vault in Cyrptomator from OneDrive Files On-Demand in Windows 10 produces the expected result. A comparison image and the version numbers tested are attached. As an example, the first file (3.8MB) was added to the vault on 12/6 but was actually last modified on 11/27

---

Attachments

• 2017-12-6_cyberduck-cryptomator-issue.jpg (248.2 KiB)
• 2017-12-6_cyberduck-cryptomator-versions.PNG (176.0 KiB)

[cyberduck]

@dkocher commented

Currently modification dates of files uploaded to OneDrive are not preserved regardless of the Cryptomator vault. For other protocols, make sure to have Preferences → Transfers → Timestamps → Uploads → Preserve modification date checked.

[cyberduck]

27aeff2 commented

That option only appears to be available in Cyberduck, but not Mountain Duck

[cyberduck]

@dkocher commented

In Mountain Duck, timestamps are set depending on the application that is writing files and updating attributes. There will be a fix in version 2.2.1 that timestamps were not always applied correctly.

[cyberduck]

@AliveDevil commented

Thanks for pointing out.
Reported dates were those of OneDrive keeps internally for creation and modification dates. We have performed necessary steps to implement the timestamp feature for OneDrive component.

[cyberduck]

@dkocher commented

In b58108c.

[cyberduck]

@dkocher commented

Milestone renamed