search for: ssh_fxp_status

...; *.php*; *.cgi; *.c; *.cpp; *.h; *.pas; *.bas; * .tex; *.pl; .htaccess; *.xtml; *.css; *.cfg; *.ini; *.sh; *.xml . File: "C:\Documents and Settings\bgu\Dokumenter\pdf" . Trying to open directory "/h580/avl/bg/pdf/". > Type: SSH_FXP_OPENDIR, Size: 27, Number: 2571 < Type: SSH_FXP_STATUS, Size: 29, Number: 2571 < Status/error code: 2, Message: 2571, Server: No such file, Language: . Creating directory "/h580/avl/bg/pdf/". . Canonifying: "/h580/avl/bg/pdf/" . Getting real path for '/h580/avl/bg/pdf/' > Type: SSH_FXP_REALPATH, Size: 28, Number: 3088...

...and has already been fixed, there seems to be some unfortunate interaction with what I believe is an OpenSSH bug: As far as I can tell, when sending a SSH_FXP_OPEN request with SSH_FXF_WRITE (i.e., opening the file write only), and then following up with a SSH_FXP_READ, the server responds with a SSH_FXP_STATUS indicating that all data has been read. Shouldn't the server signal some kind of error instead? Or am I making a mistake in parsing the response? Thanks, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F ?Time flies like an arrow, fruit flies like...

I am currently running OpenSSH 4.3. I would like to restrict the commands SFTP users can run to a list. For example, "put, get, mput, mget, mkdir, rmdir, and rm". Is this possible with OpenSSH? I have seen many posts concerning chroot'ing and the Forced Command option, but none of these solution address restricting the commands actually available inside the SFTP subsystem. Any

...ile. This +request is implemented as a SSH_FXP_EXTENDED request with the +following format: + + uint32 id + string "link at openssh.com" + string oldpath + string newpath + +On receiving this request the server will perform the operation +link(oldpath, newpath) and will respond with a SSH_FXP_STATUS message. +This extension is advertised in the SSH_FXP_VERSION hello with version +"1". + $OpenBSD: PROTOCOL,v 1.11 2008/07/05 05:16:01 djm Exp $