<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Secure Remote Access from Your Desktop</title>
	<link>http://www.linux-mag.com/id/4523/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sun, 06 Jul 2008 00:38:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Indra Tjahjono</title>
		<link>http://www.linux-mag.com/id/4523/#comment-675</link>
		<pubDate>Wed, 12 Dec 2007 04:34:25 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-675</guid>
					<description>Here is the script that I use to connect to my client.

#!/bin/sh

# $REMOTE_HOST is the name of the remote system
CLIENT=linux.client.com

# $REMOTE_PORT is the remote port number that will be used to tunnel
# back to this system
REMOTE_PORT=5000

# $COMMAND is the command used to create the reverse ssh tunnel
COMMAND="ssh -N -R $REMOTE_PORT:localhost:22 $CLIENT"

# Is the tunnel up? Perform two tests:

# 1. Check for relevant process ($COMMAND)
pgrep -f -x "$COMMAND" &#124;&#124; $COMMAND

# 2. Test tunnel by looking at "netstat" output on $CLIENT
ssh $CLIENT netstat -an &#124; egrep "tcp.*:$CLIENT.*LISTEN" \
   &#62; /dev/null 2&#62;&#38;1
if [ $? -ne 0 ] ; then
   pkill -f -x "$COMMAND"
   $COMMAND
fi</description>
		<content:encoded><![CDATA[<p>Here is the script that I use to connect to my client.</p>
<p>#!/bin/sh</p>
<p># $REMOTE_HOST is the name of the remote system<br />
CLIENT=linux.client.com</p>
<p># $REMOTE_PORT is the remote port number that will be used to tunnel<br />
# back to this system<br />
REMOTE_PORT=5000</p>
<p># $COMMAND is the command used to create the reverse ssh tunnel<br />
COMMAND=&#8221;ssh -N -R $REMOTE_PORT:localhost:22 $CLIENT&#8221;</p>
<p># Is the tunnel up? Perform two tests:</p>
<p># 1. Check for relevant process ($COMMAND)<br />
pgrep -f -x &#8220;$COMMAND&#8221; || $COMMAND</p>
<p># 2. Test tunnel by looking at &#8220;netstat&#8221; output on $CLIENT<br />
ssh $CLIENT netstat -an | egrep &#8220;tcp.*:$CLIENT.*LISTEN&#8221; \<br />
   &gt; /dev/null 2&gt;&amp;1<br />
if [ $? -ne 0 ] ; then<br />
   pkill -f -x &#8220;$COMMAND&#8221;<br />
   $COMMAND<br />
fi
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: yossis</title>
		<link>http://www.linux-mag.com/id/4523/#comment-674</link>
		<pubDate>Tue, 11 Dec 2007 07:31:14 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-674</guid>
					<description>Thx All Very Useful</description>
		<content:encoded><![CDATA[<p>Thx All Very Useful
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: kuri0s</title>
		<link>http://www.linux-mag.com/id/4523/#comment-673</link>
		<pubDate>Mon, 10 Dec 2007 19:19:11 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-673</guid>
					<description>Hi,

About changing the port number... Is there a real threat in brute-force atacks trhough ssh? I mean if you have a strong md5 password, nobody knows your username and root access is denied... By the other side, unless you have tons of ports opened (which is the least probable in a secured system) you can figure out the ssh port in less than a minute. In my opinion, that is pointless.

By the way, I use

x11vnc -usepw -display :0

to stablish a tunneled vnc connection to my default KDM opened X-session.

Thank you, very nice article.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>About changing the port number&#8230; Is there a real threat in brute-force atacks trhough ssh? I mean if you have a strong md5 password, nobody knows your username and root access is denied&#8230; By the other side, unless you have tons of ports opened (which is the least probable in a secured system) you can figure out the ssh port in less than a minute. In my opinion, that is pointless.</p>
<p>By the way, I use</p>
<p>x11vnc -usepw -display :0</p>
<p>to stablish a tunneled vnc connection to my default KDM opened X-session.</p>
<p>Thank you, very nice article.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: wcw</title>
		<link>http://www.linux-mag.com/id/4523/#comment-672</link>
		<pubDate>Sat, 08 Dec 2007 06:01:54 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-672</guid>
					<description>Thanks! It's very useful.</description>
		<content:encoded><![CDATA[<p>Thanks! It&#8217;s very useful.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Little</title>
		<link>http://www.linux-mag.com/id/4523/#comment-671</link>
		<pubDate>Fri, 07 Dec 2007 13:48:23 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-671</guid>
					<description>donatello,

I am firewalled with masquerading using iptables.  Most firewalls allow port forwarding.  Simply forward the ssh port that you are using to the ssh server to which you want to connect. That way you can log into your network and then ssh to any of the other computers that you need to access.</description>
		<content:encoded><![CDATA[<p>donatello,</p>
<p>I am firewalled with masquerading using iptables.  Most firewalls allow port forwarding.  Simply forward the ssh port that you are using to the ssh server to which you want to connect. That way you can log into your network and then ssh to any of the other computers that you need to access.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: geertvc</title>
		<link>http://www.linux-mag.com/id/4523/#comment-670</link>
		<pubDate>Fri, 07 Dec 2007 07:40:44 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-670</guid>
					<description>Title of Figure Three should be:

"How to configure a session in Putty", not "FreeNx".

Next to this, it would have been nice if there was also explained how to set up a public/private key using Putty and Puttygen (the app from the Putty suite that allows you to generate both the private and public keys).

Otherwise, nice article and overview!</description>
		<content:encoded><![CDATA[<p>Title of Figure Three should be:</p>
<p>&#8220;How to configure a session in Putty&#8221;, not &#8220;FreeNx&#8221;.</p>
<p>Next to this, it would have been nice if there was also explained how to set up a public/private key using Putty and Puttygen (the app from the Putty suite that allows you to generate both the private and public keys).</p>
<p>Otherwise, nice article and overview!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: srart</title>
		<link>http://www.linux-mag.com/id/4523/#comment-669</link>
		<pubDate>Fri, 07 Dec 2007 03:38:55 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-669</guid>
					<description>for you folks with brute force attacks on you ssh servers, try a nice little program called denyhosts it's a python program, very easy to setup, and it's aptitude (or apt-get) gettable from debian's main repository

Description: an utility to help sys admins thwart ssh hackers
 DenyHosts is a program that automatically blocks ssh brute-force attacks by
 adding entries to /etc/hosts.deny. It will also inform Linux administrators
 about offending hosts, attacked users and suspicious logins. 
 
 Syncronization with a central server is possible too. 
 
 Differently from other software that do same work, denyhosts doesn't need
 support for packet filtering or any other kind of firewall in your kernel

Tags: admin::configuring, admin::logging, implemented-in::python,
      interface::daemon, protocol::ssh, role::program, scope::utility,
      security::forensics</description>
		<content:encoded><![CDATA[<p>for you folks with brute force attacks on you ssh servers, try a nice little program called denyhosts it&#8217;s a python program, very easy to setup, and it&#8217;s aptitude (or apt-get) gettable from debian&#8217;s main repository</p>
<p>Description: an utility to help sys admins thwart ssh hackers<br />
 DenyHosts is a program that automatically blocks ssh brute-force attacks by<br />
 adding entries to /etc/hosts.deny. It will also inform Linux administrators<br />
 about offending hosts, attacked users and suspicious logins. </p>
<p> Syncronization with a central server is possible too. </p>
<p> Differently from other software that do same work, denyhosts doesn&#8217;t need<br />
 support for packet filtering or any other kind of firewall in your kernel</p>
<p>Tags: admin::configuring, admin::logging, implemented-in::python,<br />
      interface::daemon, protocol::ssh, role::program, scope::utility,<br />
      security::forensics
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: sigmon</title>
		<link>http://www.linux-mag.com/id/4523/#comment-668</link>
		<pubDate>Fri, 07 Dec 2007 02:34:35 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-668</guid>
					<description>When I allow SSH into by Debian box every once in a while, it only takes 8 hours before the brute force attacks show up. I'd very very learly opening up 22. I like the idea of changing the port to something else. The bad guys will eventually find it, but if you only need it for a couple of days.....</description>
		<content:encoded><![CDATA[<p>When I allow SSH into by Debian box every once in a while, it only takes 8 hours before the brute force attacks show up. I&#8217;d very very learly opening up 22. I like the idea of changing the port to something else. The bad guys will eventually find it, but if you only need it for a couple of days&#8230;..
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Guillermo Ruiz</title>
		<link>http://www.linux-mag.com/id/4523/#comment-667</link>
		<pubDate>Fri, 07 Dec 2007 00:08:22 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-667</guid>
					<description>To prevent brute force attacks on the SSH server, I would recommend to change the default port 22 to something like, for example, port 2002. Also, you need to make sure that root access is disabled via ssh and use public/private key pair authentication instead of encrypted plain passwords to access the server remotely... My two cents...</description>
		<content:encoded><![CDATA[<p>To prevent brute force attacks on the SSH server, I would recommend to change the default port 22 to something like, for example, port 2002. Also, you need to make sure that root access is disabled via ssh and use public/private key pair authentication instead of encrypted plain passwords to access the server remotely&#8230; My two cents&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Thomas Baumann</title>
		<link>http://www.linux-mag.com/id/4523/#comment-666</link>
		<pubDate>Thu, 06 Dec 2007 21:32:49 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/4523/#comment-666</guid>
					<description>donatello, if you look at my article at &lt;a href="http://inhalt.serviert.de/wissen/security/ssh/reverse_tunnel" rel="nofollow"&gt;inhalt.serviert.de&lt;/a&gt;
you see that this might not be a restriction if you use the feature of SSH Reverse Tunneling.
Any further Questions via &lt;a href="www.tiri.li" rel="nofollow"&gt;tiri.li - our company&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>donatello, if you look at my article at <a href="http://inhalt.serviert.de/wissen/security/ssh/reverse_tunnel" rel="nofollow">inhalt.serviert.de</a><br />
you see that this might not be a restriction if you use the feature of SSH Reverse Tunneling.<br />
Any further Questions via <a href="www.tiri.li" rel="nofollow">tiri.li - our company</a>.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
