OK, I'll take a look at this.
I may be able to extend this one a little for you.
I'm running the latest version (3.5.6 - build 213) and I'm based in AUS (GMT+10)
When I look at files stored on our server (also GMT+10) all the files are shown with datestamps 20 hours forward of the correct date/time.
For reference, my machine is Win2kPro, and is set at GM+10.
The server returns the following in reply to date;hwclock
Tue Apr 20 16:27:18 GMT+10 2004
Tue 20 Apr 2004 04:20:36 PM GMT+10 -0.858586 seconds
So it looks like the hardware clock is in local time as well. My best guess is that somehow we're ending up with a flawed double-dereferencing of the time (trying to go back to a GMT baseline or similar)
As an example a file on the server that has a correct Last updated of "10am 10-Oct-2000" would be reported as "6am 11-Oct-2000"
Anyway, I'd love to see it fixed, and will help any way I can.