Topic: Timestamps still in UTC

First off Thank you very much for providing this very useful tool !
Opennssh's inbuilt sftp is just not flexible at all.

One thing I noticed is that it logs in UTC. I'm in PST (Califormia) and when I set GMTTime -8
The timestamps are still one hour off.
I saw a post saying that was a bug . You meant GMT but actually coded UTC ?
Why can't I just use the local OS time ? It appears MSS doesn't honour TZ either.

I'm a bit confused about this. If I set GMTTime -8 I get the wrong time (one hour behind).
If I set it to GMTTime -7 I get the correct time but won't that get messed up again
when DST kicks in ?

The post was from 2010 so I'd assume this has been fixed ?

Re: Timestamps still in UTC

Hi,

MySecureShell 1.25 still use UTC Time sad

But next release would support local time (with timezone!) yeah ! smile smile

Re: Timestamps still in UTC

Hi Teka

Thanks for the update. Any ETA on the new version ?

teka wrote:

Hi,

MySecureShell 1.25 still use UTC Time sad

But next release would support local time (with timezone!) yeah ! smile smile

Re: Timestamps still in UTC

Hi,

No but you can test the non-finale release from the CVS of SourceForge wink

Re: Timestamps still in UTC

Found new problem:
If I use "DisableSetAttribute true", user upload file's modified time will change to the upload time. It can't keep the original modified time. Is that any way to figure out it?

pimsleur    http://www.pimsleur.me

Re: Timestamps still in UTC

Hi,

Some SFTP client change rights/date after the creation of file, but with "DisableSetAttribute" they can't do this...
It's a SFTP client restriction not a bug smile