Bug#390344: ssh-copy-id: Should specify that the remote command must be ran with /bin/sh

Package: openssh-client Version: 1:6.0p1-4 Followup-For: Bug #390344 With the recent addition of the restorecon commands, ssh-copy-id also fails on tcsh, due to the sh/bashisms in the command line. The above patch works for me, though I've updated it to include the latest changes: { eval

Bug#390344: ssh-copy-id: Should specify that the remote command must be ran with /bin/sh

found 390344 1:5.1p1-5 thanks There's another way to run the command without making assumptions about the remote shell: use mkdir -p Xr --- ssh-copy-id.orig 2009-05-18 13:43:58.0 +0200 +++ ssh-copy-id 2009-05-18 13:44:21.0 +0200 @@ -38,7 +38,7 @@ exit 1 fi -{ eval $GET_ID ;

Bug#390344: ssh-copy-id: Should specify that the remote command must be ran with /bin/sh

found 390344 1:4.7p1-8 tag 390344 patch thanks I second this. fish is still exotic but gaining popularity (at least as far as I know). The patch is simple and since ssh-copy-id already relies on /bin/sh for local execution, it could as well rely on it for remote execution. Cheers, Xr ---

Bug#390344: ssh-copy-id: Should specify that the remote command must be ran with /bin/sh

Package: openssh-client Version: 1:4.3p2-3 Severity: normal When the remote login shell isn't bash, the command at line 41 of ssh-copy-id umask 077; test -d .ssh || mkdir .ssh ; cat .ssh/authorized_keys may fail. This is the case with fish because it doesn't support ||. We should specify