similar to: [Bug 2902] New: Shellcheck reports on ssh-copy-id

https://bugzilla.mindrot.org/show_bug.cgi?id=2765 Bug ID: 2765 Summary: ssh-copy-id appears to hang indefinitely when the target user has no password Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: Linux Status: NEW Severity: trivial Priority: P5

The 1.4.6 version of Shorewall makes additional demands on the shell. I have found that both the RH9.0 version of ash and the version of ash that has long been available from the Shorewall download sites are *not* suitable for use with Shorewall 1.4.6. The LEAF Bering version of ash on the other hand works fine. Attached is a small shell program that will allow you to test your shell for

https://bugzilla.mindrot.org/show_bug.cgi?id=3158 Bug ID: 3158 Summary: ssh-copy-id raises "expr: syntax error" when double-hyphen is passed ("--") Product: Portable OpenSSH Version: 8.2p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=3201 Bug ID: 3201 Summary: provide an option to use sftp instead of ssh 'exec sh -c ?' for installing ssh-keys via ssh-copy-id Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: enhancement

On Fri, Aug 11, 2023, at 2:58 PM, Rowland Penny via samba wrote: > On Fri, 11 Aug 2023 14:03:01 +0200 > Kasper Brandt via samba <samba at lists.samba.org> wrote: > > > Hello > > I was directed to discuss this issue here. As I understand the issue > > with using the unquoted variable is that it expand globs unless > > noglob is set. E.g. > > > >

On Fri, 11 Aug 2023 14:03:01 +0200 Kasper Brandt via samba <samba at lists.samba.org> wrote: > Hello > I was directed to discuss this issue here. As I understand the issue > with using the unquoted variable is that it expand globs unless > noglob is set. E.g. > > root at dy3:/# test="b*" > root at dy3:/# a=($test) > root at dy3:/# echo ${a[0]} > bin

Hello I was directed to discuss this issue here. As I understand the issue with using the unquoted variable is that it expand globs unless noglob is set. E.g. root at dy3:/# test="b*" root at dy3:/# a=($test) root at dy3:/# echo ${a[0]} bin It does seem a bit hypothetical that the output of sambatool dns query ... for an A record should contain a glob, but for the sake of robustness it

https://bugzilla.mindrot.org/show_bug.cgi?id=2350 Bug ID: 2350 Summary: ssh-copy-id doesn't handle keys with missing trailing newline Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component:

So others have commented about the particulars of bash and shell quotes, etc. I wanted to suggest you take a look at ShellCheck [1,2] and BATS [3]. I have been doing syntax, lint, and acceptance testing for Puppet code for about a year...and love it... but I recently came across these and have been working to apply the same principles to my shell script projects. The sheer number of fringe bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=2575 Bug ID: 2575 Summary: ssh-copy-id fails when it can not find any key file in ~/.ssh Product: Portable OpenSSH Version: 7.2p1 Hardware: All OS: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh-copy-id

Hi, some guy on the Cygwin mailing list found that ssh-copy-id chokes on directories with spaces, which are quite common on Windows. He also provided an easy fix, basically just adding quotes, which I attached to this mail. Would that be ok to apply upstream? Thanks, Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat -------------- next part -------------- diff --git

https://bugzilla.mindrot.org/show_bug.cgi?id=2105 Bug ID: 2105 Summary: ssh-copy-id leads to rm -f * (local vs. dash) Classification: Unclassified Product: Portable OpenSSH Version: 6.2p1 Hardware: Other URL: http://bugs.debian.org/708419 OS: Linux Status: NEW Severity: major

https://bugzilla.mindrot.org/show_bug.cgi?id=1980 Bug #: 1980 Summary: use updated ssh-copy-id Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Miscellaneous AssignedTo:

https://bugzilla.mindrot.org/show_bug.cgi?id=3527 Bug ID: 3527 Summary: ssh-copy-id broken for dropbear Product: Portable OpenSSH Version: 9.1p1 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh-copy-id Assignee: unassigned-bugs at mindrot.org

https://bugzilla.mindrot.org/show_bug.cgi?id=2110 Bug ID: 2110 Summary: ssh-copy-id fails on nonexisting private key Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=2284 Bug ID: 2284 Summary: ssh-copy-id option to replace one key with another key (or ssh-replace-id command) Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=2488 Bug ID: 2488 Summary: "ssh-copy-id -o ControlPath=/tmp/foo" hangs Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: ssh-copy-id Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=2349 Bug ID: 2349 Summary: ssh-copy-id transfer keys into current directory instead of home folder Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

https://bugzilla.mindrot.org/show_bug.cgi?id=2794 Bug ID: 2794 Summary: ssh-copy-id should use the same default identity file as ssh Product: Portable OpenSSH Version: 7.6p1 Hardware: Other OS: Linux Status: NEW Severity: minor Priority: P5 Component: ssh-copy-id

Hi, i have the same problem. Trying to use the dialplan function CONNECTEDLINE() this way Set(CONNECTEDLINE(name)=${SIPPEER(${EXTEN},callerid_name)}) Set(CONNECTEDLINE(num)=${EXTEN}) ends with [Jul 1 16:30:50] ERROR[3954]: pbx.c:2902 ast_func_write: Function CONNECTEDLINE not registered Same happens trying function CALLEDID. I am using Asterisk 1.6.1.20. What do i