| Summary: | sftp-server run although Subsystem disabled | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Fabrice PLATEL <fplatel> |
| Component: | sftp-server | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED INVALID | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 4.3p1 | ||
| Hardware: | Other | ||
| OS: | All | ||
|
Description
Fabrice PLATEL
2006-11-08 23:57:09 AEDT
It seems like it is related to the fact that the command sftp-server is in the PATH : I have made the same test on a 3.4p1 openssh sshd server on linux and at first I found its behaviour was normal because I couldn't connect either with sftp command line client or filezilla in SFTP mode... but after that I just have copied sftp-server binary from the default location (which is not on the PATH) to /usr/sbin which is on the PATH, and I could connect with Filezilla again. (In reply to comment #0) [...] > subsystem request for sftp > subsystem request for sftp failed, subsystem not found > debug1: server_input_channel_req: channel 0 request > exec reply 1 > debug1: session_by_channel: session 0 channel 0 > debug1: session_input_channel_req: session 0 req exec This indicates that after the subsystem request fails, the client sends a normal exec request (basically running the equivalent of "ssh server sftp-server". You can work around this by, eg, removing execute permission from sftp-server (or maybe making a "sftp" group, chgrp'ing sftp-server and making it owner and group execute only) but be aware that this does not stop people transfering files via other means (or even copying up another sftp-server binary as it's just a normal user-level process and doesn't require any privileges). OK thank you for this clarification, so you can close the case as it's not really a bug. Fabrice Thanks Close resolved bugs after release. |