The host company has since changed its configuration and is no longer exhibiting the issue. I've gotten at least one other report of the same behavior, but have not confirmed what host company the user is using. I am working with host and TJ Saunders (the mod_sftp author) to try and reproduce this issue and to get some logging. I'll let you know what you find.
On May 26, 2012, at 11:43 AM, Alexander Lamaison wrote:
> On 25 May 2012 20:42, Will Cosgrove <will_at_panic.com> wrote:
>> Hi Guys,
>> We've run into a curious problem with libssh2 (1.4.1) with users using proFTPD (1.3.4) and mod_sftp. What is happening is when we open a remote handle for *reading* like so:
>> remoteHandle = libssh2_sftp_open(session, file, LIBSSH2_FXF_READ, 0);
>> The server wipes out the file permissions. I.e., sets them to 000. According to the docs, if the file exists on disk it should ignore the mode bits. But it seems not to be the case.
>> Before I continue tracking this down, do you guys have any ideas what the differences would be between openssh's sftp implementation and libssh2 which would be causing this?
> Can you enable debugging and send us the trace?
> Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)
> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2012-05-26