similar to: [Bug 433] Allow "ProxyCommand none" in ssh_config

http://bugzilla.mindrot.org/show_bug.cgi?id=433 Summary: Allow "ProxyCommand none" in ssh_config Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Miscellaneous AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=433 ------- Additional Comments From binder at arago.de 2002-11-12 02:35 ------- Created an attachment (id=177) --> (http://bugzilla.mindrot.org/attachment.cgi?id=177&action=view) Patch as discussed in openssh-unix-dev's thread 'Allow "ProxyCommand none" in ssh_config' ------- You are receiving this mail because:

Hi! As discussed in the thread "Question regarding patch for ProxyCommand setting". The patch is rather straight forward; maybe it would be a good idea to improve it in a way that it uses a list of string options that may have a "none" value to reset it to NULL. Ciao Thomas -------------- next part -------------- Index: readconf.c

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

https://bugzilla.mindrot.org/show_bug.cgi?id=3175 Bug ID: 3175 Summary: ssh_config(5) - ProxyCommand should explain semantics Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee:

http://bugzilla.mindrot.org/show_bug.cgi?id=528 Summary: ProxyCommand none breaks ssh Product: Portable OpenSSH Version: 3.6p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: arjones at

Hi! I recently started using ProxyCommand and noticed that it's not possible to specify a "none" value for it. I've already written a patch for that, but wanted to discuss the issue before posting the patch. The problem is the following: I'd like to use a ProxyCommand by default, but exclude some hosts. But as soon as I have Host * ProxyCommand /some/proxy/command %h %p

http://bugzilla.mindrot.org/show_bug.cgi?id=596 Summary: "ProxyCommand none" doesn't work Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=528 mouring at eviladmin.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ProxyCommand none breaks ssh|ProxyCommand none is | |sensitive to extra |

The following message From: Thomas Binder <binder at arago.de> Subject: Re: Call for release testing To: openssh-unix-dev at mindrot.org Message-ID: <20050304103859.GA7104817 at ohm.arago.de> Content-Type: text/plain; charset="us-ascii" Hi! On Fri, Mar 04, 2005 at 07:34:59PM +1100, Darren Tucker wrote: > > Otherwise we could use grep -q "$PID" > >

I would like to create an ssh_config file with two basic groups of settings: A default "Host *" settings group with: Proxycommand=/my/helper/binary %h %p And another specific "Host specialServer" settings group with ProxyCommand= or ProxyCommand='' And yes, my current ssh_config file is setup in the correct order with the "Host *" declaration last. Host

Hello, While testing recent snapshots (20131023 and 20131024) I encountered a problem with ProxyCommand. The regression tests all passed, but the use of ProxyCommand's in my ~/.ssh/config resulted in name resolution errors; even if CanonicalizeHostname was explicitly set to "no." The patch included inline below fixed the issue: Index: ssh.c

http://bugzilla.mindrot.org/show_bug.cgi?id=566 Summary: ssh-keygen -l does not print key comment for rsa/dsa keys Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: ssh-keygen AssignedTo:

Hi all, I noticed a bit of an odd issue with maintaining `known_hosts` when the target machine is behind a bastion using `ProxyJump` or `ProxyCommand` with host key clashes. Client for me right now is OpenSSH_9.3p1 on Gentoo Linux/AMD64. I'm a member of a team, and most of us use Ubuntu (yes, I'm a rebel). Another team who actually maintain this fleet often access the same machines

http://bugzilla.mindrot.org/show_bug.cgi?id=439 ------- Additional Comments From binder at arago.de 2002-11-20 00:37 ------- Created an attachment (id=178) --> (http://bugzilla.mindrot.org/attachment.cgi?id=178&action=view) Proposed patch This patch returns the keyfile's comment if there is one, the keyfile's path otherwise. ------- You are receiving this mail because:

http://bugzilla.mindrot.org/show_bug.cgi?id=439 Summary: key_try_load_public() always sets pathname as the keyfile's comment Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P2 Component: Miscellaneous

https://bugzilla.mindrot.org/show_bug.cgi?id=1977 Bug #: 1977 Summary: ProxyCommand seems to no execute shell commands Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh

Hello, My usage of ProxyCommand just calls the nc utility with various parameters. That in turn after the initial setup just copies copies the data from the network socket to stdin/stdout. This useless coping can be avoided if ssh has an option to receive the socket from the proxy command. I suppose it can improve network error reporting as ssh would talk directly to the network socket rather

On 18/8/23 15:39, Darren Tucker wrote: >> Host mytarget >> Hostname 172.16.1.2 >> ProxyJump user2 at bastion2 > I think you just need "HostKeyAlias mytarget" here. Ahh, in my scanning through the `ssh_config` manpage, I missed this, and change logs seem to indicate this feature has been around since at least 2017, so should not cause

On Fri, 18 Aug 2023 at 17:18, Stuart Longland VK4MSL <me at vk4msl.com> wrote: > On 18/8/23 15:39, Darren Tucker wrote: [...] > > I think you just need "HostKeyAlias mytarget" here. > > Ahh, in my scanning through the `ssh_config` manpage, I missed this, and > change logs seem to indicate this feature has been around since at least > 2017, so should not cause