SFTP error "unable to open file XXX" on Win8 RDP host

classic Classic list List threaded Threaded
31 messages Options
12
Reply | Threaded
Open this post in threaded view
|

SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
I set up OpenSSH for Windows by advice of Erik Berndt and connected succesfully, but I am not able to upload files, only download.
Here is the error I get



And here is what I see in log
Jun 15 16:45:20 ip-172-31-21-70 guacd[4156]: Unable to close file
Jun 15 16:45:20 ip-172-31-21-70 guacd[4156]: Unable to open file "/D:/HA300_EN_Col97_FV_A4.pdf"
Jun 15 16:46:48 ip-172-31-21-70 guacd[4156]: Unable to close file
Jun 15 16:46:48 ip-172-31-21-70 guacd[4156]: Unable to open file "./putty.exe"
Jun 15 16:55:05 ip-172-31-21-70 guacd[4156]: Unable to close file
Jun 15 16:55:05 ip-172-31-21-70 guacd[4156]: Unable to open file "/D:/RegistryCleaner.reg"
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
Nobody ever faced such error?
Reply | Threaded
Open this post in threaded view
|

SFTP error "unable to open file XXX" on Win8 RDP host

Erik Berndt
Is the SFTP server set to allow passive or active transfers?

Are you able to upload files or view directories with an ftp client? If not, It may be a firewall issue on the RDP host.

On Friday, June 16, 2017, Suncatcher16 <[hidden email]> wrote:
> Nobody ever faced such error?
>
>
>
> --
> View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1169.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
>

--
Erik Berndt / Systems Administrator
5551 Wellington Rd, Gainesville, VA 20155
703.631.0004 x520 (Phone) / 703.257.1725 (Fax)
http://www.superiorpaving.net

Need to open an IT support ticket?  
http://FixIT.superiorpaving.net/portal or [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
Erik Berndt wrote
Is the SFTP server set to allow passive or active transfers?
How to check that?
I tried WinSCP client and it both downloads and uploads files like a charm. I investigated Passive/Active setting and wasn't able to change it, as it stated here, Passive mode is relevant only for FTP, whilst SFTP connection is always active.
And if it is firewall issue, then WinSCP client will be blocked too. Any other suggeestions?
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
The same error is throwing on Win7 RDP host. It looks like some (mis)configuration of the server, when it tries to open with wrong slash (like in Linux) or so-so.
 Unable to open file "//
Nobody have meet this?
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
Could anybody help? The problem is still unsolved. It affects both on Win8 and Win7.
Upload/download via linux scp goes fine, WInSCP also goes OK. The reason is in Guacamole.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Marko Nikolić

Maybe it is related to https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222. The file was remaining locked after download and no operation on this file were possible any more.

Regards,
Marko


On Wed, 12 Jul 2017, 18:50 Suncatcher16, <[hidden email]> wrote:
Could anybody help? The problem is still unsolved. It affects both on Win8
and Win7.
Upload/download via linux scp goes fine, WInSCP also goes OK. The reason is
in Guacamole.



--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1280.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Mike Jumper
Another possibility is https://issues.apache.org/jira/browse/GUACAMOLE-303, which was recently merged. Guacamole's SFTP implementation assumes "/" exists and is listable, which is not necessarily the case, particularly on Windows.

- Mike


On Jul 12, 2017 10:49, "Marko Nikolić" <[hidden email]> wrote:

Maybe it is related to https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222. The file was remaining locked after download and no operation on this file were possible any more.

Regards,
Marko


On Wed, 12 Jul 2017, 18:50 Suncatcher16, <[hidden email]> wrote:
Could anybody help? The problem is still unsolved. It affects both on Win8
and Win7.
Upload/download via linux scp goes fine, WInSCP also goes OK. The reason is
in Guacamole.



--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1280.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
In reply to this post by Marko Nikolić
Marko Nikolić wrote
Maybe it is related to
https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222.
The file was remaining locked after download and no operation on this file
were possible any more.
I download and upload different files, so it's probably not an issue.

Another possibility is https://issues.apache.org/jira/browse/GUACAMOLE-303, which was recently merged. Guacamole's SFTP implementation assumes "/" exists and is listable, which is not necessarily the case, particularly on Windows.
Even when I specify /C:/Users/UserXXX as a root folder, it gives me in the log

Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open file "//Sketch.png"

When I forward to specific directory (not root) it gives as usual

Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file "/C:/64/Sketch.png"
Jul 13 08:37:41 ip-172-31-21-9 guacd[21147]: Unable to close file
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Mike Jumper
When you're uploading the file, are you uploading by dragging the file into the browser window, or through clicking the upload button in Guacamole's file browser?


On Thu, Jul 13, 2017 at 1:22 AM, Suncatcher16 <[hidden email]> wrote:
Marko Nikolić wrote
> Maybe it is related to
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222.
> The file was remaining locked after download and no operation on this file
> were possible any more.

I download and upload different files, so it's probably not an issue.


> Another possibility is
> https://issues.apache.org/jira/browse/GUACAMOLE-303, which was recently
> merged. Guacamole's SFTP implementation assumes "/" exists and is
> listable, which is not necessarily the case, particularly on Windows.

Even when I specify */C:/Users/UserXXX* as a root folder, it gives me in the
log

*Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open file
"//Sketch.png"*

When I forward to specific directory (not root) it gives as usual

*Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file
"/C:/64/Sketch.png"
Jul 13 08:37:41 ip-172-31-21-9 guacd[21147]: Unable to close file*



--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1289.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
When you're uploading the file, are you uploading by dragging the file into
the browser window, or through clicking the upload button in Guacamole's
file browser?
It doesn't work either way.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Mike Jumper
On Thu, Jul 13, 2017 at 7:48 AM, Suncatcher16 <[hidden email]> wrote:
>
>> When you're uploading the file, are you uploading by dragging the file
>> into
>> the browser window, or through clicking the upload button in Guacamole's
>> file browser?
>
> It doesn't work either way.
>

Understood, but it's not clear to me which method you're using in each
case, and some of the specifics of the log messages don't match up
with what would be expected.

From what you posted previously:

>
> Even when I specify */C:/Users/UserXXX* as a root folder, it gives me in
> the log
>
> *Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open
> file "//Sketch.png"*
>

This is odd, as specifying the root folder as "/C:/Users/UserXXX"
would result in uploads via the file browser going to that directory,
or subdirectories of that directory, like
"/C:/Users/UserXXX/Sketch.png". It shouldn't be "//Sketch.png".

If uploaded via dragging the file into the window, which would use the
default upload directory (which is independent of the file browser
root), this would be possible, and it would make sense that it fails
(as "//" is no doubt non-existent).

>
> When I forward to specific directory (not root) it gives as usual
>
> *Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file
> "/C:/64/Sketch.png"
>

I'm not sure exactly what you're saying here. What do you mean by
"forward to a specific directory (not root)"? Is this different from
what you were doing previously when specifying a specific folder like
"/C:/Users/UserXXX" for the root?

Is the "/C:/64/" folder writable by the account being used for SFTP?

Does the SSH server list any errors in its logs when these operations fail?

Thanks,

- Mike
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
I'm not sure exactly what you're saying here. What do you mean by
"forward to a specific directory (not root)"?
Forward to specific directory means "changing directory in built-in browser dir explorer". In my understanding when I specify dir in this built-in browser, the upload should go into this particular directory.
For example, this picture denotes that upload will go into the root of C folder.



Am i right?

but it's not clear to me which method you're using in each
case, and some of the specifics of the log messages don't match up
with what would be expected.
Here is table of tests I made just now. Two sets of tests were made: w/ set default dir in connection and w/o. Terms:
Current directory is C:\64. This is directory specified in the opened inline file browser, default upload directory in connection settings is empty in this case.
Default directory is also /C:/64, it is a default upload directory in connection settings, built-in file browser is not opened in this case.

Current directory drag'n'drop:  
Jul 14 16:12:00 ip-172-31-21-9 guacd[1185]: Unable to open file "./file.docx"
Current directory button upload:  
Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to close file
Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to open file "/C:/64/file.docx"
Default directory drag-n-drop:
Jul 14 16:18:16 ip-172-31-21-9 guacd[1264]: Unable to open file "./file.docx"
Default directory button upload:
Jul 14 16:23:26 ip-172-31-21-9 guacd[1264]: Unable to close file
Jul 14 16:23:26 ip-172-31-21-9 guacd[1264]: Unable to open file "//file.docx"
As you noticed, specifying directory gives nothing and upload goes into root folder anyway.
This is odd, as specifying the root
So yes, this is odd for me too.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Mike Jumper
On Fri, Jul 14, 2017 at 9:08 AM, Suncatcher16 <[hidden email]> wrote:

>
>> I'm not sure exactly what you're saying here. What do you mean by
>> "forward to a specific directory (not root)"?
>
> Forward to specific directory means "changing directory in built-in browser
> dir explorer". In my understanding when I specify dir in this built-in
> browser, the upload should go into this particular directory.
> For example, this picture denotes that upload will go into the root of C
> folder.
>
> <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1302/Sketch.png>
>
> Am i right?
>

Yes, that's correct.

>
>> but it's not clear to me which method you're using in each
>> case, and some of the specifics of the log messages don't match up
>> with what would be expected.
>
> Here is table of tests I made just now. Two sets of tests were made: w/ set
> default dir in connection and w/o. Terms:
> *Current directory* is *C:\64*. This is directory specified in the opened
> inline file browser, default upload directory in connection settings is
> empty in this case.
> *Default directory* is also */C:/64*, it is a default upload directory in
> connection settings, built-in file browser is not opened in this case.
>
> Current directory drag'n'drop:
>
>> Jul 14 16:12:00 ip-172-31-21-9 guacd[1185]: Unable to open file
>> "./file.docx"
>
> Current directory button upload:
>
>> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to close file
>> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to open file
>> "/C:/64/file.docx"
>

As the path is correct in these cases, there must be something else
preventing the upload from succeeding. My first guess would be
permissions, but the SSH server logs may have specifics on what is
failing.

>
> As you noticed, specifying directory gives nothing and upload goes into root
> folder anyway.
>
>> This is odd, as specifying the root
>
> So yes, this is odd for me too.
>

Is it possible that you're only using a recent build of
guacamole-client, and not guacamole-server, thus the new SFTP root
directory parameter is being ignored?

- Mike
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
Is it possible that you're only using a recent build of
guacamole-client, and not guacamole-server, thus the new SFTP root
directory parameter is being ignored?
What do you mean by guacamole-server? WAR-file?
My guacd is
Starting guacd: guacd[1889]: INFO:      Guacamole proxy daemon (guacd) version 0.9.12-incubating started
SUCCESS
And my Tomcat app is 0.9.12 too.



My first guess would be
permissions, but the SSH server logs may have specifics on what is
failing.
sshd server log contains no SFTP-related strings at all. It looks like this:
876 12:24:44:934 Accepted password for JohnDoe from 52.52.52.52 port 35256 ssh2
2432 12:25:11:287 Accepted password for JohnDoe from 52.52.52.52 port 35252 ssh2
2432 12:25:11:569 Received disconnect from 52.52.52.52 port 35252:11: Bye
2432 12:25:11:569 Disconnected from user JohnDoe 52.52.52.52 port 35252
876 14:17:51:136 Received disconnect from 52.52.52.52 port 35256:11: Bye
876 14:17:51:136 Disconnected from user JohnDoe 52.52.52.52 port 35256
1860 14:18:02:308 Received signal 8; terminating.
1768 14:16:33:352 Server listening on :: port 95.
1768 14:16:33:352 Server listening on 0.0.0.0 port 95.
600 14:23:08:025 Accepted password for JohnDoe from 52.52.52.52 port 35626 ssh2
1768 18:38:26:763 Received signal 8; terminating.
1872 18:38:42:227 Server listening on :: port 95.
1872 18:38:42:227 Server listening on 0.0.0.0 port 95.
2704 19:22:30:922 Accepted password for JohnDoe from 52.52.52.52 port 36236 ssh2
812 19:33:52:611 Accepted password for JohnDoe from 192.168.137.122 port 42868 ssh2
812 19:36:25:345 Received disconnect from 192.168.137.122 port 42868:11: disconnected by user
812 19:36:25:345 Disconnected from user JohnDoe 192.168.137.122 port 42868
1976 19:38:15:657 Accepted password for JohnDoe from 192.168.137.122 port 42870 ssh2
1976 19:39:39:845 Received disconnect from 192.168.137.122 port 42870:11: disconnected by user
1976 19:39:39:845 Disconnected from user JohnDoe 192.168.137.122 port 42870
2524 19:40:59:876 Accepted password for JohnDoe from 192.168.137.122 port 42876 ssh2
2524 19:40:59:954 Received disconnect from 192.168.137.122 port 42876:11: disconnected by user
2524 19:40:59:954 Disconnected from user JohnDoe 192.168.137.122 port 42876
1668 19:41:32:423 Accepted password for JohnDoe from 192.168.137.122 port 42878 ssh2
1668 19:41:39:548 Received disconnect from 192.168.137.122 port 42878:11: disconnected by user
1668 19:41:39:548 Disconnected from user JohnDoe 192.168.137.122 port 42878
1232 19:42:20:751 Accepted password for JohnDoe from 192.168.137.122 port 42880 ssh2
1232 19:42:20:861 Received disconnect from 192.168.137.122 port 42880:11: disconnected by user
1232 19:42:20:861 Disconnected from user JohnDoe 192.168.137.122 port 42880
2704 19:44:34:780 Received disconnect from 52.52.52.52 port 36236:11: Bye
2704 19:44:34:780 Disconnected from user JohnDoe 52.52.52.52 port 36236
1872 19:44:41:484 Received signal 8; terminating.
1804 19:45:04:882 Server listening on :: port 95.
1804 19:45:04:882 Server listening on 0.0.0.0 port 95.
1848 19:58:27:493 Accepted password for JohnDoe from 52.52.52.52 port 36306 ssh2
1848 20:00:11:456 Received disconnect from 52.52.52.52 port 36306:11: Bye
1848 20:00:11:456 Disconnected from user JohnDoe 52.52.52.52 port 36306
1804 20:00:17:816 Received signal 8; terminating.
1828 11:18:47:748 Server listening on :: port 95.
1828 11:18:47:748 Server listening on 0.0.0.0 port 95.
872 11:29:25:329 Accepted password for JohnDoe from 192.168.137.153 port 60476 ssh2
2852 11:30:23:127 Accepted password for JohnDoe from 52.52.52.52 port 38010 ssh2
2852 11:31:26:315 Received disconnect from 52.52.52.52 port 38010:11: Bye
2852 11:31:26:315 Disconnected from user JohnDoe 52.52.52.52 port 38010
2836 11:31:30:779 Accepted password for JohnDoe from 52.52.52.52 port 38016 ssh2
2836 11:33:41:022 Received disconnect from 52.52.52.52 port 38016:11: Bye
2836 11:33:41:022 Disconnected from user JohnDoe 52.52.52.52 port 38016
2892 11:33:43:273 Accepted password for JohnDoe from 52.52.52.52 port 38028 ssh2
2892 11:34:56:569 Received disconnect from 52.52.52.52 port 38028:11: Bye
2892 11:34:56:569 Disconnected from user JohnDoe 52.52.52.52 port 38028
348 11:34:59:531 Accepted password for JohnDoe from 52.52.52.52 port 38034 ssh2
348 11:37:44:273 Received disconnect from 52.52.52.52 port 38034:11: Bye
348 11:37:44:273 Disconnected from user JohnDoe 52.52.52.52 port 38034
280 11:37:49:240 Accepted password for JohnDoe from 52.52.52.52 port 38046 ssh2
280 11:41:58:959 Received disconnect from 52.52.52.52 port 38046:11: Bye
280 11:41:58:959 Disconnected from user JohnDoe 52.52.52.52 port 38046
872 11:42:02:297 Received disconnect from 192.168.137.153 port 60476:11: disconnected by user
872 11:42:02:297 Disconnected from user JohnDoe 192.168.137.153 port 60476
1828 19:03:31:465 Received signal 8; terminating.
1824 19:03:45:773 Server listening on :: port 95.
1824 19:03:45:773 Server listening on 0.0.0.0 port 95.
800 19:06:13:305 Accepted password for JohnDoe from 52.52.52.52 port 41844 ssh2
800 19:08:55:160 Received disconnect from 52.52.52.52 port 41844:11: Bye
800 19:08:55:160 Disconnected from user JohnDoe 52.52.52.52 port 41844
1832 19:08:58:192 Accepted password for JohnDoe from 52.52.52.52 port 41850 ssh2
1832 19:18:00:793 Received disconnect from 52.52.52.52 port 41850:11: Bye
1832 19:18:00:793 Disconnected from user JohnDoe 52.52.52.52 port 41850
2916 19:18:03:279 Accepted password for JohnDoe from 52.52.52.52 port 41868 ssh2
1824 19:33:53:857 Received signal 8; terminating.
1820 19:34:06:612 Server listening on :: port 95.
1820 19:34:06:612 Server listening on 0.0.0.0 port 95.
1820 19:44:10:451 Received signal 8; terminating.
1848 21:02:44:275 Server listening on :: port 95.
1848 21:02:44:291 Server listening on 0.0.0.0 port 95.
3608 21:09:34:737 Accepted password for JohnDoe from 52.52.52.52 port 49830 ssh2
If this is a permissions issue on server, why do all other clients work fine? For me it's clearly guacamole issue, as empty server log tells use that SFTP requests from Guacamole are not even reached the server.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Mike Jumper
On Fri, Jul 14, 2017 at 11:10 AM, Suncatcher16 <[hidden email]> wrote:
>
>> Is it possible that you're only using a recent build of
>> guacamole-client, and not guacamole-server, thus the new SFTP root
>> directory parameter is being ignored?
>
> What do you mean by /guacamole-server/? WAR-file?

I mean the body of code which builds guacd, libguac, the various
supported protocols, etc.:

http://guacamole.incubator.apache.org/doc/gug/installing-guacamole.html#building-guacamole-server

The WAR file (part of guacamole-client) is somewhat relevant, too, as
only an up-to-date web application would have the definition of the
new "sftp-root-directory" parameter, but that would only make defining
a connection which uses that parameter more difficult for users of the
database authentication. The key piece which determines whether the
parameter works is guacamole-server. If too old, the
"sftp-root-directory" parameter will not exist for the protocol
plugins loaded by guacd, and specifying it will have no effect.

> My guacd is
>
>> Starting guacd: guacd[1889]: INFO:      Guacamole proxy daemon (guacd)
>> version 0.9.12-incubating started
>> SUCCESS
>
> And my Tomcat app is 0.9.12 too.
>
> <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1309/Sketch.png>
>

Ah, OK - that definitely would not have the necessary parameter then.
The changes from GUACAMOLE-303 were merged in after the version
numbers were bumped to 0.9.13-incubating in anticipation of the first
RC. To be able to use the new parameter, you will need to build from
git master.

The new "sftp-root-directory" parameter only affects the directories
displayed in the file browser, however. If you are already able to
navigate through the file browser without error, then that isn't the
problem.

I agree that if the only SFTP client that fails in your case is
Guacamole, then that suggests the problem is within Guacamole. It is
unlikely that the SFTP requests are not reaching your SSH server at
all - if the SFTP connection had failed, then Guacamole would have
aborted the connection entirely.

When testing Guacamole vs. other SFTP clients, are you using the same
user account on the RDP server in all cases?

- Mike
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
Mike Jumper wrote
When testing Guacamole vs. other SFTP clients, are you using the same
user account on the RDP server in all cases?

- Mike
Yes, indeed.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
I mean the body of code which builds guacd, libguac, the various
supported protocols, etc.:
I built them, guacd and guacamole-server at the same time, so they definitely match each other.
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

Suncatcher16
So what I steps I can take further to narrow the problem?
Reply | Threaded
Open this post in threaded view
|

Re: SFTP error "unable to open file XXX" on Win8 RDP host

halcyon
This post was updated on .
I have been running into this issue. In my case it is an incompatibility
between libssh2 and openssh (Win32 ). To get around this I downloaded the
libssh2 code from Github and made the following changes:

around line 1060 in sftp_open in sftp.c

change:

        attrs.permissions = mode |
            (open_file ? LIBSSH2_SFTP_ATTR_PFILETYPE_FILE :
             LIBSSH2_SFTP_ATTR_PFILETYPE_DIR);

to
        attrs.permissions = mode;

Run automke tools, run configure, make libssh2, make install libssh2. Then
recompile guacamole server from source against this modified libssh2
library, install guacamole server, restart guacamole client and everything
worked. Issue is current libssh2 performing this OR with
LIBSSH2_SFTP_ATTR_PFILETYPE_FILE makes the permissions something like
0100755 instead of 0755 and the Win32 OpenSSH server can't cope. Turn on
logs in Win32 OpenSSH to see what the sftp server is doing. Add l VERBOSE to
the sftp-server command line args in sshd_config.

You may also need to change Windows permission on the sftp-server.log file
if anyone other than Administrator or NTSERVICE\sshd is performing the file
transfer. Ironically, the OpenSSH sftp client works.



--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
12