similar to: [Bug 572] No Effect "ProxyCommand none" in ssh_config

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:

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=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 OpenSSH'lers! While using OpenSSH for quite a while, I became annoyed with the inflexible config-file parsing algorithm. I special it did not alow me to express: "Use *no* proxy for host xyz, but *this* proxy for all other hosts". So I had a look at the source an make a quick-n-dirty change, allowing me to use the special ProxyCommand "None" to express "don't

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:

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=528 mouring at eviladmin.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ProxyCommand none breaks ssh|ProxyCommand none is | |sensitive to extra |

For some odd reason, one line was removed from the handling of ProxyCommand in readconf.c. As a result, ssh crashes on strlen(string) when it parses this option. --- readconf.c:X Mon Aug 6 23:35:52 2001 +++ readconf.c Wed Aug 15 16:11:44 2001 @@ -475,6 +475,7 @@ case oProxyCommand: charptr = &options->proxy_command; + string = xstrdup(""); while ((arg =

http://bugzilla.mindrot.org/show_bug.cgi?id=433 ------- Additional Comments From binder at arago.de 2003-02-06 05:10 ------- Created an attachment (id=218) --> (http://bugzilla.mindrot.org/attachment.cgi?id=218&action=view) Patch for ProxyCommand's description in ssh_config.5 I have to admit I've never edited nroff-files before, so here's my first attempt ... -------

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:

Hi, the attached patch adds support for the keywords "OpenCommand" and "CloseCommand" to ssh_config. They are commands which are executed before the connection is established (or ProxyCommand started) and after the connection has been closed (or ProxyCommand ended). this is usefull for stuff like portknocking or (that's what I wrote the patch for) talking with trapdoor2

Hi, I am facing a problem in migrating to SFTP from FTP for an unix based application. I have got 2 m/c, SRC (Source) m/c and TRG (Target) m/c. For SFTP connectivity, I created a Public-Key (ssh-keygen -t dsa) in src_usr1(user-id) at SRC m/c . Which created the necessary identification file (id_dsa & id_dsa.pub) andthen, I copied the id_dsa.pub into the file authorized_keys in

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

Hi, I cant log into my Fedora core 2 box from another linux machine or an OSX machine It worked the very first time I tried then never since. I have downl?oaded the newest openssh sources, and done ./configure make make install as root but seems to still use the old openssh. I stopped and restarted the sshd any Ideas? cheers Dan I get this message with the -v flag on [daniel:~] dan%

Hi all I was thinking maybe other ppl need this small hack :) So ssh supports ProxyCommand which use a separate proccess for in/out chans to remote sshd. But sometimes this extra proc is not desired but ssh should use a specific socket (in below patch is fd 3 and 4) for same thing.. For example a reverse ssh connection where sshd connects back to ssh(which is executed by a a script that binds to

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

https://bugzilla.mindrot.org/show_bug.cgi?id=2577 Bug ID: 2577 Summary: Port Forwarding on Proxy with ProxyCommand ssh -W does not work / bad file descriptor Product: Portable OpenSSH Version: 7.2p1 Hardware: amd64 OS: Linux Status: NEW Severity: major Priority: P5

Hi, I'm not a subscriber to this list so please CC: me in any replies. I found myself in a situation where I was behind a corporate firewall that allowed only web requests to the outside world (and furthermore those requests had to be via their proxy server). Therefore, I couldn't SSH to the outside world. However, the HTTP proxy 'CONNECT' method, which is normally used to

When using a ProxyCommand, it appears that the arguments to it are passed in an unsafe manner: % ssh -o ProxyCommand='nc %h %p' '$(not found)' zsh:1: command not found: not nc: you must specify the address/port couple of the remote endpoint ssh_exchange_identification: Connection closed by remote host This is not zsh specific (e.g. it happens with bash). One can resolve the