Subject: [libssh2] #264: SCP send not properly setting mtime or atime

[libssh2] #264: SCP send not properly setting mtime or atime

From: libssh2 Trac <trac_at_libssh2.stuge.se>
Date: Mon, 29 Apr 2013 18:41:38 -0000

#264: SCP send not properly setting mtime or atime
--------------------------+--------------------
 Reporter: wguynes | Owner:
     Type: defect | Status: new
 Priority: normal | Milestone: 1.4.3
Component: examples | Version: 1.4.2
 Keywords: scp examples | Blocked By:
   Blocks: |
--------------------------+--------------------
 When using libssh2_scp_send_ex() or libssh2_scp_send64() with non-zero
 mtime or atime parameters the time stamp does not get set.

 This is not so much a fault with the library, but that the scp send
 examples are misleading. After the data is actually sent the remote side
 is expecting one NULL byte. This will trigger the remote side to actually
 set the timestamp on the now fully received file. At present the examples
 merely slam the channel closed which the remote side meekly accepts.

 This will also be critical to implementation of any recursive SCP feature
 in the future. Multiple file transfers over one, open channel will require
 the NULL byte after each write data phase. 

-- 
Ticket URL: <https://trac.libssh2.org/ticket/264>
libssh2 <https://trac.libssh2.org/>
C library for writing portable SSH2 clients
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2013-04-29