Can't get "pwd" and promptly dies

First off, hats off to the development team of WinSCP!

If a directory does not have the "read" bit set (e.g. rwx--x--x) and one tries to change into
that directory, WinSCP2 (up to Version #110) dies, complaining it cannot execute "pwd"

Would it be possible so that WinSCP does not die when it can't get its pwd? But instead
trust that the directory one enters is the one that was typed in? In other words, in directories
where permission hasn't been given to "ls" or "pwd", one can still "cd" around without problems.
There seems to be no reason for WinSCP to die.

WinSCP is an incredible product, and I recommend it to everybody! Keep up the good work!

User wrote:

If a directory does not have the "read" bit set (e.g. rwx--x--x) and one tries to change into
that directory, WinSCP2 (up to Version #110) dies, complaining it cannot execute "pwd"

What is you server? I have tried this and I can 'pwd' even if I do not have "read" bit set.

I am having a similar problem with winSCP. I am using opensshd on a windows server, and the terminal it uses is called switch.exe. This terminal does not have a command called pwd. I cannot connect using winSCP because it hangs after the authentication.

Here is a copy of the log file. I tried a hack, by making a batch file called pwd.bat. No luck, as my batch file programmins skills are lacking. Is there any fix for this I can use? Do you recommend anything? Thanks for your help, I'm pasting the winSCP log if you'd like to look at it.

******
. --------------------------------------------------------------------------
. WinSCP Version 2.3.0 (Build 146)
. Login time: Thursday, May 01, 2003 11:36:35 AM
. --------------------------------------------------------------------------
. Session name: jeremy@10.200.10.40
. Host name: 10.200.10.40 (Port: 22)
. User name: jeremy (Password: Yes, Key file: No)
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping interval: 0 sec (0 = off); Timeout: 15 sec
. SSH Bugs: A,A,A,A,A,A,A,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: Yes
. Clear aliases: Yes, Unset nat.vars: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. --------------------------------------------------------------------------
. Looking up host "10.200.10.40"
. Connecting to 10.200.10.40 port 22
. Server version: SSH-2.0-OpenSSH_3.6.1p1
. We claim version: SSH-2.0-PuTTY-Local: Apr 23 2003 11:38:40
. Using SSH protocol version 2
. Doing Diffie-Hellman group exchange
. Doing Diffie-Hellman key exchange
. Host key fingerprint is:
. ssh-rsa 1024 bb:64:1a:c1:3f:a6:68:a0:24:d4:5a:c2:7d:de:80:6e
. Initialised AES-256 client->server encryption
. Initialised AES-256 server->client encryption
! Using username "jeremy".
! ****USAGE WARNING****
! This is a private computer system. This computer system, including all
! related equipment, networks, and network devices (specifically including
! Internet access) are provided only for authorized use. This computer system
! may be monitored for all lawful purposes, including to ensure that its use
! is authorized, for management of the system, to facilitate protection against
! unauthorized access, and to verify security procedures, survivability, and
! operational security. Monitoring includes active attacks by authorized entities
! to test or verify the security of this system. During monitoring, information
! may be examined, recorded, copied and used for authorized purposes. All
! information, including personal information, placed or sent over this system
! may be monitored.
! Use of this computer system, authorized or unauthorized, constitutes consent
! to monitoring of this system. Unauthorized use may subject you to criminal
! prosecution. Evidence of unauthorized use collected during monitoring may be
! used for administrative, criminal, or other adverse action. Use of this system
! constitutes consent to monitoring for these purposes.
. Keyboard-interactive authentication refused
. Sent password
. Access granted
. Opened channel for session
. Started a shell/command
. --------------------------------------------------------------------------
. Doing startup conversation with host.
. Skipping host startup message (if any).
> echo "WinSCP: this is end-of-file:0"
< Microsoft Windows 2000 [Version 5.00.2195]

< (C) Copyright 1985-2000 Microsoft Corp.

<

< c:\>"WinSCP: this is end-of-file:0"

. Getting current directory name.
> pwd ; echo "WinSCP: this is end-of-file:0"
<

< c:\>/home

<

. Waiting for data timed out, asking user what to do.
. Asking user:
. Host hasn't answered for 15 seconds.
.
. Wait for another 15 seconds? Pressing 'Abort' button will close session. ()
. Attempt to close connection due to fatal exception:
* Terminated by user.
. Closing connection.
* (ESshFatal) Error getting name of current remote directory.

Anonymous wrote:

I am having a similar problem with winSCP. I am using opensshd on a windows server, and the terminal it uses is called switch.exe. This terminal does not have a command called pwd. I cannot connect using winSCP because it hangs after the authentication.

WinSCP does not work with switch.exe. You must specify /bin/sh directly on Shell tab of login dialog.

That work on a windows server (/bin/...)? or I shall specify a command shell or \cmd or something like that?

OpenSSH for Windows has /bin, /etc and similar directories (they are virtual).