Encrypted data on an untrusted Linux device can be accessed by another instance of syncthing with the known password connecting to the encrypted folder. In this case, as expected, the original timestamps are applied to the decrypted and synced files.
Or by accessing the encrypted data and using the command syncthing decrypt --to /path/to/decrypted/files/ --password xxxx /path/to/encrypted/folder/ In this case the timestamps are applied as the current time of the OS used to decrypt the folder.
Question: is there anyway the second method can access the original timestamps for each file?
I downloaded the github code (956c44c) and complied it, syncthing worked as normal but I got the same results with decrypt, so I suspect I stuffed it up and got the code for main instead of your PR.
Maybe Iāll wait for #8412 to merge into the next RC release.
You can just download the binary built by CI from the pull request for testing. Itās a bit hard to find the files (called artifacts) but somewhere under Checks there should be appropriate binaries I believe.
The fix (#8412) didnāt make it into release 1.20.3, so I rolled my own binary from main (v1.20.4-dev.1.gabea3d75, Linux (64-bit Intel/AMD) and all is working again.