cd to dir in tree w/ read protect fails

[anonymous]

This is similar, but not the same as bug #515812. That
bug report deals with not being able to change dir into
a directory with list protect. My bug report refers to
trying to change dir into a directory _further_ below a
directory with list protect.

For example, dir /var/log has list disabled (via
disabling read), but has navigation enabled (via
enabling execute). Subdirs (and subsubdirs, etc.)
below /var/log allow both reading and navigation. So,
I should be able to use Filezilla to get to
/var/log/foo and /var/log/foo/bar and even
/var/log/foo/bar/baz. Indeed, Filezilla will show me
the contents of /var/log/foo, but it will not show me
the contests of either /var/log/foo/bar, nor
/var/log/foo/bar/baz. Filezilla stops at 1 level down.

If it can do 1 level down, why not 2 and 3? Using

WS_FTP works (though it does complain about not being
able to set the directory identifier; but at least I
can get a listing and transfer the needed files).

An example from the log:

Command: CD /var/log/foo/bar/
Response: Remote working directory is now /var/log/foo
Status: Directory listing successfull

In this example from the log, the directory listing is
that of /var/log/was, which is interesting because it
shows that Filezilla can list dir contents 1 level
below a read-protected dir. It can not list dir
contents more levels down.

[Tim Kosse]

From what I see, you're connected to an SFTP server, right?
(else the command would be CWD ... instead of CD ...)
In my opinion, the problem is not caused by FileZilla:
FileZilla sends the command to change the directory
to /var/log/foo/bar/, but the server only changes the directory
to /var/log/foo
To clarify this issue, could you please post a full message
log? (Enable all debug settings on the debug page in FileZilla)

[anonymous]

Logged In: NO

This sounds like a problem I recently reported. The issue is
that when you click on the fiolder, it tries to list the contents
of the folder. Because there is no drag-and-drop capability in
FZ, the only wat to copy files to a folder is to open the
folder. However, opening it fails because the user has no list
access to the folder.

This works fine with some other clients, such as VanDyke's
SecureFX and CoreFTP.

Here is a log excerpt from a session that shows this problem
when trying to get to a folder called "upload."

Status: Connecting to 1.2.3.4:22 ...
Status: Connected with 1.2.3.4:22, initializing SFTP
connection...
Command: CONNECT username@1.2.3.4:22
Response: Remote working directory is Public:/
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: Remote directory is Public:/
Command: LIST
Response: Sucessfully received 1 items
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CD upload
Response: Directory Public:/upload: permission denied
Error: Could not retrieve directory listing

[anonymous]

Logged In: NO

Here is a full debug log of my previous example:

Status: Connecting to 1.2.3.4:22 ...
Trace: FzSFtp.exe: FzSFtp started and initialized.
Trace: SftpControlSocket.cpp(2160): OnConnect(0)
caller=0x00b09688
Status: Connected with 1.2.3.4:22, initializing SFTP
connection...
Command: CONNECT username@1.2.3.4:22
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(1949): Server version: SSH-2.0-VShell_2_2_2_547 VShell
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(1985): We claim version: SSH-2.0-PuTTY-FZ-Local: Oct 15
2003 00:11:47
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(1987): Using SSH protocol version 2
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(4216): Doing Diffie-Hellman group exchange
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(675): Initialised AES-256 client->server encryption
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(675): Initialised AES-256 server->client encryption
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(5284): Sent password
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(4684): Access granted
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(5364): Opened channel for session
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: FzSFtp.exe: cvsroot\FileZilla\source\FzSFtp\SSH.C
(5714): Started a shell/command
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Response: Remote working directory is Public:/
Status: Connected
Trace: SftpControlSocket.cpp(2278): ResetOperation(1)
caller=0x00b09688
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",1)
caller=0x00b09688
Status: Retrieving directory listing...
Command: PWD
Response: Remote directory is Public:/
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0)
caller=0x00b09688
Command: LIST
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0)
caller=0x00b09688
Response: Sucessfully received 1 items
Trace: SftpControlSocket.cpp(289): List(FALSE,0,"","",0)
caller=0x00b09688
Trace: 0 Nov 05, 2003 14:39 upload/
Status: Directory listing successful
Trace: SftpControlSocket.cpp(2278): ResetOperation(1)
caller=0x00b09688
Trace: SftpControlSocket.cpp(289): List
(FALSE,0,"/Public:/","upload",9) caller=0x00b09688
Status: Retrieving directory listing...
Command: CD upload
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2442): OnReceive(0)
caller=0x00b09688
Response: Directory Public:/upload: permission denied
Trace: SftpControlSocket.cpp(289): List(FALSE,1,"","",0)
caller=0x00b09688
Trace: SftpControlSocket.cpp(2278): ResetOperation(4)
caller=0x00b09688
Error: Could not retrieve directory listing

[Tim Kosse]

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).