Weird behavior of remote timestamps
i have some trouble with timestamps.
My setup ist winscp 5.11.3 build 7995 on windows server 2016 build 1607 and corresponding FTP Server ist vsftpd 3.0.2 on CentOS7, both in Germany, so timezone is GMT+1, and i use FTPS protocol in this context.
WinSCP shows files in the GUI which are already on the FTP Server and which have last modification time (LMT) in december (for example) with correct timestamps (the LMT in WinSCP in the right pane is the same time as with "ls -al" in the linux shell). But files on the FTP Server with LMT in summer 2017 are shown in WinSCP with an offset of -1 hour compared to linux shell.
My origin was using default session properties (MLSD=AUTO), then, because vsftpd has no MLSD feature, i fiddled with MLSD=off and some timezonedifferences, but got only a time shift for all files and on top the same -1h offset for files last modified while DST.
In contrast, FileZilla shows all timestamps consistent as with "ls -al".
I do *not* set vsftpd config option use_localtime=yes, so vsftpd uses UTC timestamps internally, which is the preferred setup. use_localtime=yes is no choice because it would break other dependencies.
I thoroughly read the FAQ about timestamps but i found no reason for this behavior.
Many thanks for a useful explanation.