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

Author Message
Laurenta
[View user's profile]

Joined: 2015-04-21
Posts: 1
Location: France
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.
Advertisements
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24991
Location: Prague, Czechia
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).
stephaner

Guest


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
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24991
Location: Prague, Czechia
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?

Quote:
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.
Guest




prikryl 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:

Code:
...
echo $LANG ; echo "WinSCP: this is end-of-file:$status"
Sent 56 bytes
...
Received 26 bytes (1)
LANG: Undefined variable.
...


Regards,
--
Stéphane
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 24991
Location: Prague, Czechia
WinSCP uses the LANG only to tell if the shell uses UTF-8 encoding.
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License