<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SSL to SSH tunneling (stunnel)</title>
	<atom:link href="http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/</link>
	<description>Consulting/Development in Java, Objective-C for web based systems and iPhone</description>
	<lastBuildDate>Wed, 14 Jul 2010 20:54:16 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-4401</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 08 Apr 2010 08:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-4401</guid>
		<description>My blog post explains how to run SSH in SSL, which I believe is the same as your SSH in HTTPS.</description>
		<content:encoded><![CDATA[<p>My blog post explains how to run SSH in SSL, which I believe is the same as your SSH in HTTPS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-4397</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Thu, 08 Apr 2010 01:17:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-4397</guid>
		<description>This works but is a bit of a &#039;middle-ground&#039; fudge and certainly won&#039;t work in all environments. If you want to get your SSH through a web-proxy, it&#039;s better to completely wrap your SSH in HTTPS - e.g. 

http://www.saulchristie.com/bypass-firewalls

A little bit more effort but completely indetectable even by full network traffic analysis.</description>
		<content:encoded><![CDATA[<p>This works but is a bit of a &#8216;middle-ground&#8217; fudge and certainly won&#8217;t work in all environments. If you want to get your SSH through a web-proxy, it&#8217;s better to completely wrap your SSH in HTTPS &#8211; e.g. </p>
<p><a href="http://www.saulchristie.com/bypass-firewalls" rel="nofollow">http://www.saulchristie.com/bypass-firewalls</a></p>
<p>A little bit more effort but completely indetectable even by full network traffic analysis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amaël</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-1968</link>
		<dc:creator>amaël</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-1968</guid>
		<description>is there a way to use stunnel with a proxy that allow https (CONNECT)? The proxy needs the client to be authenticated. I &#039;ve seen savvard patch but it doesn&#039;t work with latest version (4.28) of stunnel.</description>
		<content:encoded><![CDATA[<p>is there a way to use stunnel with a proxy that allow https (CONNECT)? The proxy needs the client to be authenticated. I &#8216;ve seen savvard patch but it doesn&#8217;t work with latest version (4.28) of stunnel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nalply</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-1860</link>
		<dc:creator>nalply</dc:creator>
		<pubDate>Sun, 01 Nov 2009 14:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-1860</guid>
		<description>It&#039;s neccessary if you are limited by a stupid firewall not allowing outgoing SSH. With SSH over SSL you can trick out the firewall . :-)</description>
		<content:encoded><![CDATA[<p>It&#8217;s neccessary if you are limited by a stupid firewall not allowing outgoing SSH. With SSH over SSL you can trick out the firewall . <img src='http://www.jakeri.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pants</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-1295</link>
		<dc:creator>Pants</dc:creator>
		<pubDate>Thu, 03 Sep 2009 13:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-1295</guid>
		<description>Great post.  I &#039;get&#039; exactly why you need to tunnel SSH over stunnel as you&#039;ve described here.  I&#039;m currently working with a very tricky proxy server that won&#039;t allow a connection directly to an SSHD server because it requires SSL handshaking, otherwise it drops the connection.  Using stunnel I can now get the correct SSL protocol and still use SSH too.</description>
		<content:encoded><![CDATA[<p>Great post.  I &#8216;get&#8217; exactly why you need to tunnel SSH over stunnel as you&#8217;ve described here.  I&#8217;m currently working with a very tricky proxy server that won&#8217;t allow a connection directly to an SSHD server because it requires SSL handshaking, otherwise it drops the connection.  Using stunnel I can now get the correct SSL protocol and still use SSH too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-317</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 02 Apr 2009 06:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-317</guid>
		<description>Yes, SSH is very safe! 
And I am quite aware of how alternate ports for the sshd.

Most of the time this guide is like reinvent the wheel. :-)

I did not do the tunneling due to security issues in ssh but to pass through tightly secured proxies and firewalls. On larger companies, security department usually only allow internet traffic on http and https (ssl) through a forward proxy.

Then you have two ways to go.

1. Tunnel ssh over http; Then you must cope with all strange hacks a forward proxy might do. Adding headers etc.

2. Or do some tricks over https proxy connect with ssl, one could be my solution above.</description>
		<content:encoded><![CDATA[<p>Yes, SSH is very safe!<br />
And I am quite aware of how alternate ports for the sshd.</p>
<p>Most of the time this guide is like reinvent the wheel. <img src='http://www.jakeri.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>I did not do the tunneling due to security issues in ssh but to pass through tightly secured proxies and firewalls. On larger companies, security department usually only allow internet traffic on http and https (ssl) through a forward proxy.</p>
<p>Then you have two ways to go.</p>
<p>1. Tunnel ssh over http; Then you must cope with all strange hacks a forward proxy might do. Adding headers etc.</p>
<p>2. Or do some tricks over https proxy connect with ssl, one could be my solution above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ammon</title>
		<link>http://www.jakeri.net/2009/01/ssl-to-ssh-tunneling-stunnel/comment-page-1/#comment-316</link>
		<dc:creator>Ammon</dc:creator>
		<pubDate>Wed, 01 Apr 2009 23:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.jakeri.net/?p=99#comment-316</guid>
		<description>For the love of... Why? Seriously. Why?

SSH is already SSL encrypted. That&#039;s kind of the entire point. You can even tunnel other apps through SSH just like you are doing with raw SSL here.

If you want to be able to SSH to an alternate port on your home machine, just tell your sshd to listen to another port and save yourself the wasted complexity, cpu, and bandwidth.</description>
		<content:encoded><![CDATA[<p>For the love of&#8230; Why? Seriously. Why?</p>
<p>SSH is already SSL encrypted. That&#8217;s kind of the entire point. You can even tunnel other apps through SSH just like you are doing with raw SSL here.</p>
<p>If you want to be able to SSH to an alternate port on your home machine, just tell your sshd to listen to another port and save yourself the wasted complexity, cpu, and bandwidth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
