\r
<h2><a name="sec1" id="sec1"></a>News</h2>\r
<dl>\r
+<dt>2005-07-08</dt>\r
+<dd>\r
+Rev. 1.95. Buf fix for previous change. The bug causes the fail of\r
+ basic authentication. And also fixed bug of parameter file handling.\r
+ Thanks reporting, Johannes Schindelin <Johannes.Schindelin at gmx.de>.\r
+</dd>\r
+<dt>2005-07-07</dt>\r
+<dd>\r
+Rev. 1.94. Changed to use snprintf()/vsnprintf() for security issue\r
+ that gcc complained them on OpenBSD 3.7/x86. The features are not\r
+ changed.\r
+</dd>\r
<dt>2005-03-04</dt>\r
<dd>\r
Updated compile option for Mac OS X.\r
</p>\r
\r
<pre class="example">\r
-## Outside of the firewall, use connect command with SOCKS conenction.\r
-Host *\r
- ProxyCommand connect -S socks.local.net %h %p\r
-\r
## Inside of the firewall, use connect command with direct connection.\r
Host *.local.net\r
ProxyCommand connect %h %p\r
+\r
+## Outside of the firewall, use connect command with SOCKS conenction.\r
+Host *\r
+ ProxyCommand connect -S socks.local.net %h %p\r
</pre>\r
\r
<p>\r
</p>\r
\r
<pre class="example">\r
-## Outside of the firewall, with HTTP proxy\r
-Host *\r
- ProxyCommand connect -H proxy.local.net:8080 %h %p\r
-\r
## Inside of the firewall, direct\r
Host *.local.net\r
ProxyCommand connect %h %p\r
+\r
+## Outside of the firewall, with HTTP proxy\r
+Host *\r
+ ProxyCommand connect -H proxy.local.net:8080 %h %p\r
</pre>\r
\r
<h3><a name="sec7" id="sec7"></a>Use SSH</h3>\r
\r
</p>\r
\r
-<blockquote>\r
-<p>\r
- poll mail-server\r
- protocol pop3\r
- plugin "ssh %h connect localhost %p"\r
- username "username"\r
- password "password"\r
-\r
-</p>\r
-</blockquote>\r
+<pre class="example">\r
+poll mail-server\r
+ protocol pop3\r
+ plugin "ssh %h connect localhost %p"\r
+ username "username"\r
+ password "password"\r
+</exmaple>\r
\r
-<h2><a name="sec23" id="sec23"></a>Break The More Restricted Wall</h2>\r
+* <a name="sec23" id="sec23"></a>Break The More Restricted Wall\r
\r
-<p>\r
If firewall does not provide SOCKS nor HTTPS other than port 443, you\r
cannot break the wall in usual way. But if you have you own host\r
which is accessible from internet, you can make ssh connection to your\r
own host by configuring sshd as waiting at port 443 instead of\r
standard 22. By this, you can login to your own host via port 443.\r
Once you have logged-in to extenal home machine, you can execute\r
-<strong>connect</strong> as second hop to make connection from your own host to\r
+**connect** as second hop to make connection from your own host to\r
final target host, like this:\r
\r
-</p>\r
-\r
-<pre class="example">\r
+<example>\r
$ cat ~/.ssh/config\r
Host home\r
ProxyCommand connect -H firewall:8080 %h 443\r
<table width="100%" border="0" summary="Footer navigation">\r
<tbody><tr>\r
<td width="50%" align="left">\r
- <span class="footdate">Last Updated: 2005-03-07</span><br/>\r
+ <span class="footdate">Last Updated: 2005-07-18</span><br/>\r
</td>\r
<td width="50%" align="right">\r
This page is authored by <a href="mailto:gotoh@taiyo.co.jp">Shun-ichi GOTO</a>\r