<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Proxycommand on Simon Žekar — unix, communications, stupidities</title><link>https://simon.zekar.com/tags/proxycommand/</link><description>Recent content in Proxycommand on Simon Žekar — unix, communications, stupidities</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 Mar 2013 01:02:16 +0000</lastBuildDate><atom:link href="https://simon.zekar.com/tags/proxycommand/index.xml" rel="self" type="application/rss+xml"/><item><title>SSH bouncing update – getting rid of Killed by signal 1</title><link>https://simon.zekar.com/2013/03/07/ssh-bouncing-update-killed-by-signal-1/</link><pubDate>Thu, 07 Mar 2013 01:02:16 +0000</pubDate><guid>https://simon.zekar.com/2013/03/07/ssh-bouncing-update-killed-by-signal-1/</guid><description>&lt;p>If you read my &lt;a href="https://simon.zekar.com/2008/09/01/ssh-bouncing/">article on ssh bouncing&lt;/a>, you surely use it.&lt;/p>
&lt;p>One annoying thing is “Killed by signal 1” when exiting the bounced session.&lt;/p>
&lt;pre tabindex="0">&lt;code>dolfi:~ simon$ ssh supercoolserver
Permission denied (publickey,keyboard-interactive).
Killed by signal 1.
&lt;/code>&lt;/pre>&lt;p>So the solution is to change the ~/.ssh/config file and add the “2&amp;gt;/dev/null” to the very end of the ProxyCommand line.&lt;/p>
&lt;pre tabindex="0">&lt;code>Host hostalias
User root
ProxyCommand ssh bouncer.server -p 2222 &amp;#39;nc destination.server 2222&amp;#39; 2&amp;gt;/dev/null
&lt;/code>&lt;/pre>&lt;p>Found the solution &lt;a href="http://www.undeadly.org/cgi?action=article&amp;amp;sid=20070925181947">here&lt;/a>. Thanks to &lt;a href="http://www.erdelynet.com/">merdely&lt;/a>.&lt;/p>
&lt;p>S.&lt;/p></description></item></channel></rss>