Forum » Feature Requests »

Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Shell "/bin/sh" to be supported by default

WinSCP uses the LANG only to tell if the shell uses UTF-8 encoding.
Guest

Re: Shell "/bin/sh" to be supported by default

martin wrote:

stephaner wrote:

The problem seems to be related to WinSCP relying on the existence of the LANG environment variable.

What do you mean by that?


I mean the debug output of WinSCP show the following: 

...

echo $LANG ; echo "WinSCP: this is end-of-file:$status"

Sent 56 bytes

...

Received 26 bytes (1)

LANG: Undefined variable.

...


Regards,
--
Stéphane
martin

Re: Shell "/bin/sh" to be supported by default

stephaner wrote:

The problem seems to be related to WinSCP relying on the existence of the LANG environment variable.

What do you mean by that?

But setting this variable (setenv LANG C, as the default shell is csh) lead to WinSCP complaining about unexpected directory listing line 'drwxr-xr-x 10 admin wheel 512 22 mai 09:31 .'.

WinSCP does not understand the "mai".

WinSCP requires an English environment when using SCP protocol.
stephaner

Re: Shell "/bin/sh" to be supported by default

The problem seems to be related to WinSCP relying on the existence of the LANG environment variable. But setting this variable (setenv LANG C, as the default shell is csh) lead to WinSCP complaining about unexpected directory listing line 'drwxr-xr-x 10 admin wheel 512 22 mai 09:31 .'.

Any hint?

Stéphane
martin

Re: Shell "/bin/sh" to be supported by default

There's no default list in WinSCP. It's the server that picks the default (the default shell for the account you are connecting with).
Laurenta

Shell "/bin/sh" to be supported by default

Hi,

Could it be possible that future releases of WinSCP does include "/bin/sh" as one of the default "Shell" to try for ?

I don't know if it is something related to the "Bash Bug / Shellshock", but the latest releases of "StormShield Firewall Appliance" (FreeBSD based) needs us to manually change the WinSCP "Advanced Site Settings"/"Shell" to "/bin/sh" in order to the connection to succeed (in "default" mode, we get the famous "Host is not communicating for more than 15 seconds" message).

I think that adding "/bin/sh" in the default list (so that it is automaticaly tried by WinSCP) can help people connect to such Appliance (and surely to some other related UNIX system), and could prevent users from raising some "false" bug reports (it's not a bug indeed, simply changing the Shell make it works, but finding the "fix" can be somehow tricky).

Kind Regards and Long Live to WinSCP !

Laurent A.

Documentation

Support

Associations

Follow Us