On Tue, Oct 5, 2010 at 19:12, Daniel Stenberg <[email protected]> wrote: > On Tue, 5 Oct 2010, Ezequiel Ruiz wrote: > >> Yes I understand, but I don't want to change it, just want to "read" it >> with the stat() based functions. Would it be possible to add support for >> reading that value with stat() ? > > No, I don't think that field is sent by the server. See section "5. File > Attributes" of the draft-ietf-secsh-filexfer-02.txt for full details. > > http://tools.ietf.org/wg/secsh/draft-ietf-secsh-filexfer/draft-ietf-secsh-filexfer-02.txt
Indeed, there is no ctime in there.. it's a bit strange that it's so, I can definitely see the point of checking the ctime value of a remote file: if it had been copied into the remote location with e.g. cp -p you won't be able to figure out when the file was placed there without it. Is there some other mechanism in the protocol to do the equivalent thing of checking ctime? -Tor _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
