Description of problem: This commit broke scp: commit f2c2687ca6c6c7e25c9a547227027ab28eb4fc16 Author: Oliver Stöneberg <oliverst> Date: Fri Oct 18 14:58:04 2013 +0200 scp: Fixed result of ssh_scp_string_mode() to get SCP working. Reviewed-by: Andreas Schneider <asn> diff --git a/src/scp.c b/src/scp.c index 6838a3c..db07aed 100644 --- a/src/scp.c +++ b/src/scp.c @@ -814,7 +814,7 @@ int ssh_scp_integer_mode(const char *mode){ */ char *ssh_scp_string_mode(int mode){ char buffer[16]; - snprintf(buffer,sizeof(buffer),"%.4o",mode); + snprintf(buffer,sizeof(buffer),"%.4d",mode); The mode does need to be an octal numeric string. Mode 0600 now gets sent on the wire as 0384, triggering a "scp: protocol error: bad mode" response, and an "scp status code 1d not valid" message from libssh. Version-Release number of selected component (if applicable): libssh-0.6.0-1
Looks like this one is really easy to fix, shouldn't we push a libssh update with that fixed? (Maybe x2go would then at least work with the "ignore the key mismatch" workaround?)
I plan to do libssh 0.6.1 release today or tomorrow. It will have this issue fixed!
libssh-0.6.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libssh-0.6.1-1.fc19
libssh-0.6.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/libssh-0.6.1-1.fc20
libssh-0.6.1-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
libssh-0.6.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.