similar to: [Bug 472] scp won't accept 'hash' character in usernames, ssh will

http://bugzilla.mindrot.org/show_bug.cgi?id=472 Summary: scp won't accept 'hash' character in usernames, ssh will Product: Portable OpenSSH Version: 3.5p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=634 Summary: scp incompatibility with ssh.com scp Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: wgs3 at

http://bugzilla.mindrot.org/show_bug.cgi?id=638 Summary: scp: wrong exit status Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: scp AssignedTo: openssh-bugs at mindrot.org ReportedBy: koenig at

http://bugzilla.mindrot.org/show_bug.cgi?id=105 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2002-02-07 06:54 ------- could you please try this without scp? e.g.

Here is a patch to add the missing scp -1 and -2 options to eliminate confusion for users familiar with the commercial version of SSH. This patch and others are maintained on the secure nfs (SNFS) web page: http://www.math.ualberta.ca/imaging/snfs/ -- John Bowman University of Alberta diff -ur openssh-3.0.2p1/scp.c openssh-3.0.2p1J2/scp.c --- openssh-3.0.2p1/scp.c Sun Oct 21 18:53:59 2001 +++

http://bugzilla.mindrot.org/show_bug.cgi?id=1193 Summary: Open ssh will not allow changing of passwords on usernames greater than 8 characters. Product: Portable OpenSSH Version: 3.9p1 Platform: Sparc OS/Version: Solaris Status: NEW Keywords: help-wanted Severity: major Priority: P2

Hello, Some hosting companies insist on having usernames of the form user#account(@example.com). The ssh client is quite happy with such usernames, but scp fails with 'invalid user name'. Looking at the source code, scp rejects ' " ` # and ' ', whereas ssh apparently enforces no such restriction. My question is twofold: Firstly, why do ssh and scp behave differently?

Hi, we are using usernames on our systems that contain a point '.', like "r.john". We found it necessary to patch the source to make the "scp" command work with those usernames. Cheers Kai --- openssh-2.2.0p1/scp.c Wed Aug 30 01:11:30 2000 +++ withpoint/scp.c Mon Dec 11 02:06:35 2000 @@ -1042,7 +1042,7 @@ c = *cp; if (c & 0200) goto bad; - if

Hello, scp(1) doesn't allow copying files to a remote host with a username containing utf-8 characters. It just returns "invalid user name". While traditionally usernames were restricted to printable us-ascii, nowadays there's little problem in allowing them. In fact, it is allowed by ssh, and even scp when copying _from_ such username. The limitation seems to lie on the if

Hi, Is there some know problem between the 'scp' client in OpenSSH 2.5.1p1 and F-Secure's SSH 2.4.0 server? The client is running on a Linux (2.2.17) box and server is running on Win2K. When I try to transfer files it asks me for the password (which I provide) then it hangs. Using 'scp -v' didn't provide any helpful info; it's as though the problem happened before

http://bugzilla.mindrot.org/show_bug.cgi?id=557 Summary: scp over ssh-relay insists in asking passphrase Product: Portable OpenSSH Version: 3.4p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: scp AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses

http://bugzilla.mindrot.org/show_bug.cgi?id=369 ------- Additional Comments From markus at openbsd.org 2002-07-25 04:25 ------- 0 for success and >0 for failure _is_ standard on unix. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=996 Summary: Fatal error in xfree() when scp invokes ssh with a LocalForward config Product: Portable OpenSSH Version: 4.0p1 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

http://bugzilla.mindrot.org/show_bug.cgi?id=248 ------- Additional Comments From liug at mama.indstate.edu 2002-05-18 07:14 ------- I tried several different versions of openssh, and got the same problem with scp. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hello list, right now SSH Tunnel / scp is reaches just around 76Mb/s on my E5 Xeon using AES-NI but openssl reaches around 600-700Mb/s using 128aes-cbc cipher. As far as i understand http://www.psc.edu/index.php/hpn-ssh this is due to very small buffers in ssh / scp. Is there any work on this? Like autotuning the buffer size? Are there plans to integrate the hpn patches? Greets, Stefan

http://bugzilla.mindrot.org/show_bug.cgi?id=587 Summary: ssh returns non-zero return code but appears to work Product: Portable OpenSSH Version: -current Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=369 ------- Additional Comments From devel at pitux.com 2002-09-10 19:19 ------- I confirm that this bug does exist. It's especially annoying since we use here a lot of scripts which check for the return values of scp to indicate success or failure. In fact it does the good thing on nonexistent files/dirs/etc, but fails in case of auth

Dear People, I have following situation with "OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f": a) I will send files via scp to: "OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004" b) used command: scp [-vvv] -p -B -C /home/gdg/generation/cr/test_lnx50/lnx50.test2.000001 gdg at lnx50:/home/gdg/EMPFANG/lnx50.test2 Login without PW runs fine,

If the source and destination file are identical, the receiving scp truncates the file. On the sending end, read() returns 0, and garbage is sent instead of actual data, and the receiving end puts it into the file, which at least confuses the users. -- Florian Weimer Florian.Weimer at RUS.Uni-Stuttgart.DE University of Stuttgart http://cert.uni-stuttgart.de/