bugzilla-daemon at mindrot.org
2003-May-20 10:52 UTC
[Bug 572] No Effect "ProxyCommand none" in ssh_config
http://bugzilla.mindrot.org/show_bug.cgi?id=572 Summary: No Effect "ProxyCommand none" in ssh_config Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: sasajima at pc.fujitsu.com It has written to "man ssh_config" as follows:> Setting the command to ``none'' disables this option entirely.It writes to ssh_config as follows:> Host * > ProxyCommand noneHowever, "ProxyCommand none" does not effect. ssh is going to execute the command "none."> localhost:/home/sasajima% /usr/local/bin/ssh -v localhost > OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090702f > debug1: Reading configuration data /usr/local/etc/ssh_config > debug1: Applying options for * > debug1: Rhosts Authentication disabled, originating port will not be trusted. > debug1: Executing proxy command: exec none > > debug1: identity file /home/sasajima/.ssh/identity type -1 > debug1: identity file /home/sasajima/.ssh/id_rsa type -1 > debug1: identity file /home/sasajima/.ssh/id_dsa type -1 > /bin/sh: none: not found > ssh_exchange_identification: Connection closed by remote host > debug1: Calling cleanup 0x2bcf0(0x0)Vriable options.proxy_command is not "none" but is "none\n." in ssh.c:605. It causes that. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2003-May-20 11:12 UTC
[Bug 572] No Effect "ProxyCommand none" in ssh_config
http://bugzilla.mindrot.org/show_bug.cgi?id=572 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From djm at mindrot.org 2003-05-20 21:12 ------- Already fixed *** This bug has been marked as a duplicate of 528 *** ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.