Remote machine OS Debian Linux
Current timezones GMT (UTC +0000), Not in DST.
Winscp version 4.1.9
Protocol in use SCP
Environment Timezone offset 0
Environment DST mode - adjust remote timestamp to local conventions (UNIX)
Transfer Preferences - Preserve timestamp
GUI Interface: Norton Commander style
Transferring from local to remote files with various dates but all with 10:00 timestamps:
Files dated shortly before 25th Oct are correctly stored on remote server with dst adjustment as 10:00 +0100 e.g.
-rw-r--r-- 1 pete pete 39 2009-10-24 10:00:00.000000000 +0100 24.bin
Files dated after 31st October are also correctly store without dst adjustment e.g.
-rw-r--r-- 1 pete pete 39 2009-11-01 10:00:00.000000000 +0000 01.bin
However, files dated between 25th and 31st October 2009 correctly loose the +0100 dst offset but the UTC time is decremented by one hour e.g.
-rw-r--r-- 1 pete pete 39 2009-10-26 09:00:00.000000000 +0000 26.bin
-rw-r--r-- 1 pete pete 39 2009-10-31 09:00:00.000000000 +0000 31.bin
Subsequent local to server file synchronisation fails as WinSCP always thinks these local files are 1 hour newer.
(The transition to DST in March was handled correctly.)
Using SFTP protocol gives the same result on the server but in the WinSCP GUI the remote server display times are corrected and synchronisation works as expected.
This happens with two different remote servers, though both run Debian Linux, and using another WinXP machine on another network to the same servers.
Comparing SCP & SFTP actions, as the end result on the server is the same but WinSCP display & synchronisation behaviour is different, this leads me to suspect a bug in WinSCP rather than Debian Linux or WinXP.
Is this repeatable on other Win/Linux systems & timezones?
Timestamps shifted 1 hour between 25th & 31st Oct - DST bug?