<?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: How to safely connect from anywhere to your closed Linux firewall</title> <atom:link href="http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/feed/" rel="self" type="application/rss+xml" /><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/</link> <description>The Journal Of A Linux Sysadmin</description> <lastBuildDate>Thu, 09 Feb 2012 03:50:59 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3</generator> <item><title>By: My Personal Blog &#187; Blog Archive &#187; How to safely connect from anywhere to your closed Linux firewall &#124; MDLog:/sysadmin</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-182047</link> <dc:creator>My Personal Blog &#187; Blog Archive &#187; How to safely connect from anywhere to your closed Linux firewall &#124; MDLog:/sysadmin</dc:creator> <pubDate>Sat, 03 Jul 2010 23:00:30 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-182047</guid> <description>[...] How to safely connect from anywhere to your closed Linux firewall &#124; MDLog:/sysadmin: &#8220;In general all the great ideas are the simple ones. Many times we see a great idea in practice and we wander why didn’t we thought of that before? It is just so simple… The first time I have seen the knockd project I liked it instantly. The idea is so simple, and though so effective. Knockd is a port-knocking application that silently runs on a server passively listening to network traffic. Once it will see a port sequence it has an action configured for it, it will run that action. We can see this as a remote control to our server: once we hit the right button it will take the appropriate action!&#8221;  Filed under: Tech Stuff &#124; Permalink [...]</description> <content:encoded><![CDATA[<p>[...] How to safely connect from anywhere to your closed Linux firewall | MDLog:/sysadmin: &#8220;In general all the great ideas are the simple ones. Many times we see a great idea in practice and we wander why didn’t we thought of that before? It is just so simple… The first time I have seen the knockd project I liked it instantly. The idea is so simple, and though so effective. Knockd is a port-knocking application that silently runs on a server passively listening to network traffic. Once it will see a port sequence it has an action configured for it, it will run that action. We can see this as a remote control to our server: once we hit the right button it will take the appropriate action!&#8221;  Filed under: Tech Stuff | Permalink [...]</p> ]]></content:encoded> </item> <item><title>By: mazziblog &#187; Blog Archive &#187; knock knock</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-168492</link> <dc:creator>mazziblog &#187; Blog Archive &#187; knock knock</dc:creator> <pubDate>Thu, 29 May 2008 20:19:39 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-168492</guid> <description>[...] [Link ] [...]</description> <content:encoded><![CDATA[<p>[...] [Link ] [...]</p> ]]></content:encoded> </item> <item><title>By: Debian SSH Problems &#124; etbe</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-160978</link> <dc:creator>Debian SSH Problems &#124; etbe</dc:creator> <pubDate>Sun, 18 May 2008 08:08:43 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-160978</guid> <description>[...] of packets (from this host). For example SYN packet on ports 1000, 2000, 3000, 4000. More on: http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/ Package is included in Debian, work very well. Not recommended on weak machines with lots of [...]</description> <content:encoded><![CDATA[<p>[...] of packets (from this host). For example SYN packet on ports 1000, 2000, 3000, 4000. More on: <a
href="http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/" rel="nofollow">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/</a> Package is included in Debian, work very well. Not recommended on weak machines with lots of [...]</p> ]]></content:encoded> </item> <item><title>By: Linux: What Is Port Knocking? &#124; Hackosis</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-124699</link> <dc:creator>Linux: What Is Port Knocking? &#124; Hackosis</dc:creator> <pubDate>Sun, 20 Jan 2008 00:03:12 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-124699</guid> <description>[...] has written a tutorial if you are interested in implementing port knocking.           Tags: Linux, Networking, Open source, Port knocking, Security  Like this post? Subscibe [...]</description> <content:encoded><![CDATA[<p>[...] has written a tutorial if you are interested in implementing port knocking.           Tags: Linux, Networking, Open source, Port knocking, Security  Like this post? Subscibe [...]</p> ]]></content:encoded> </item> <item><title>By: Corran</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-108071</link> <dc:creator>Corran</dc:creator> <pubDate>Thu, 29 Nov 2007 21:40:38 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-108071</guid> <description>I use it, as some has stated, as an EXTRA layer of security for production servers. I have locked SSH, and to open it I have to do the knockd-sequence to at all open SSH. Thus - it is not &quot;false security&quot; - it is extra. I change the sequence at random, but since I still believe in SSH-security, I wouldn&#039;t quite mind if someone sniffs it either. It&#039;s like using greylisting at an smtp gateway - it is not security I use it for, but nmap-scanners can&#039;t see my SSH port at all. And that means that maybe I have saved a few nasty OpenSSH-bugs. Only time will tell.</description> <content:encoded><![CDATA[<p>I use it, as some has stated, as an EXTRA layer of security for production servers. I have locked <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym>, and to open it I have to do the knockd-sequence to at all open <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym>. Thus &#8211; it is not &#8220;false security&#8221; &#8211; it is extra. I change the sequence at random, but since I still believe in <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym>-security, I wouldn&#8217;t quite mind if someone sniffs it either. It&#8217;s like using greylisting at an smtp gateway &#8211; it is not security I use it for, but nmap-scanners can&#8217;t see my <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym> port at all. And that means that maybe I have saved a few nasty OpenSSH-bugs. Only time will tell.</p> ]]></content:encoded> </item> <item><title>By: Top Linux News &#187; How to safely connect from anywhere to your closed Linux firewall</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-103788</link> <dc:creator>Top Linux News &#187; How to safely connect from anywhere to your closed Linux firewall</dc:creator> <pubDate>Sat, 17 Nov 2007 13:09:49 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-103788</guid> <description>[...] read more &#124; digg story [...]</description> <content:encoded><![CDATA[<p>[...] read more | digg story [...]</p> ]]></content:encoded> </item> <item><title>By: clsox</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-98956</link> <dc:creator>clsox</dc:creator> <pubDate>Mon, 05 Nov 2007 10:34:06 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-98956</guid> <description>iam thinking... maybe you need linux system to enter... What occurs if the is a windows or something other operating system...?thanksI will try out this</description> <content:encoded><![CDATA[<p>iam thinking&#8230; maybe you need linux system to enter&#8230; What occurs if the is a windows or something other operating system&#8230;?</p><p>thanks</p><p>I will try out this</p> ]]></content:encoded> </item> <item><title>By: New Linux User &#187; Geeky Fun: Knockd</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-15636</link> <dc:creator>New Linux User &#187; Geeky Fun: Knockd</dc:creator> <pubDate>Tue, 23 Jan 2007 02:47:19 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-15636</guid> <description>[...] In this example, Marius uses knockd to modify his iptables when he pings ports 7000, 8000, and 9000 in sequence. The modification involves adding the IP address that the pings came from to allow that IP to SSH into the system. When he&#8217;s done, he pings the ports in reverse order and knockd then removes that IP&#8217;s access. This allows him to keep his box secure by not allowing anyone except a single internal IP to SSH in except for the brief period of time when he uses knockd to change that. Bloody brilliant. [...]</description> <content:encoded><![CDATA[<p>[...] In this example, Marius uses knockd to modify his iptables when he pings ports 7000, 8000, and 9000 in sequence. The modification involves adding the IP address that the pings came from to allow that IP to <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym> into the system. When he&#8217;s done, he pings the ports in reverse order and knockd then removes that IP&#8217;s access. This allows him to keep his box secure by not allowing anyone except a single internal IP to <acronym
class="uttAcronym" title="Secure Shell">SSH</acronym> in except for the brief period of time when he uses knockd to change that. Bloody brilliant. [...]</p> ]]></content:encoded> </item> <item><title>By: me</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-13307</link> <dc:creator>me</dc:creator> <pubDate>Sat, 30 Dec 2006 13:56:37 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-13307</guid> <description>sounds like a safe. you dail 5647,3456,2746 and the safe show all his nice secrets.but remember: http://web.mit.edu/kvogt/www/safecracker.html</description> <content:encoded><![CDATA[<p>sounds like a safe. you dail 5647,3456,2746 and the safe show all his nice secrets.</p><p>but remember: <a
href="http://web.mit.edu/kvogt/www/safecracker.html" rel="nofollow">http://web.mit.edu/kvogt/www/safecracker.html</a></p> ]]></content:encoded> </item> <item><title>By: Linux Unix &#187; How to safely connect from anywhere to your closed Linux firewall</title><link>http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/comment-page-2/#comment-1479</link> <dc:creator>Linux Unix &#187; How to safely connect from anywhere to your closed Linux firewall</dc:creator> <pubDate>Fri, 01 Sep 2006 12:45:05 +0000</pubDate> <guid
isPermaLink="false">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/#comment-1479</guid> <description>[...] The idea is so simple, and though so effective. Knockd is a port-knocking application that silently runs on a server passively listening to network traffic. Once it will see a port sequence it has an action configured for it, it will run that action. Once we hit the right button it will take the appropriate action!read more&#160;&#124;&#160;digg story [...]</description> <content:encoded><![CDATA[<p>[...] The idea is so simple, and though so effective. Knockd is a port-knocking application that silently runs on a server passively listening to network traffic. Once it will see a port sequence it has an action configured for it, it will run that action. Once we hit the right button it will take the appropriate action!read more&nbsp;|&nbsp;digg story [...]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: www.ducea.com @ 2012-02-08 19:57:46 by W3 Total Cache -->
