https://sourceforge.net/p/knockit/wiki/Introduction/Recent changes to IntroductionenMon, 30 Jun 2014 22:55:24 -0000https://sourceforge.net/p/knockit/wiki/Introduction/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -1,9 +1,9 @@ -Why is port knocking useful? +Why is port knocking (PN) useful? ---------------------------- firewalling is great... but it lacks some flexibility port knocking brings you easily. 1. You might need to access your services from places you did not configure access for -2. You might want to prevent brute players to try repeatedly your services ports again and again. They're closed, except for you. +2. You might want to prevent brute players to try repeatedly your services ports again and again. With PN they're closed, except for you. What port knocking is not ------------------------- </pre> </div>SamirMon, 30 Jun 2014 22:55:24 -0000https://sourceforge.nete9b57abae059e09eae7cea67e82ecc91b0e4012chttps://sourceforge.net/p/knockit/wiki/Introduction/<div class="markdown_content"><h2 id="why-is-port-knocking-useful">Why is port knocking useful?</h2> <p>firewalling is great... but it lacks some flexibility port knocking brings you easily.</p> <ol> <li>You might need to access your services from places you did not configure access for</li> <li>You might want to prevent brute players to try repeatedly your services ports again and again. They're closed, except for you.</li> </ol> <h2 id="what-port-knocking-is-not">What port knocking is not</h2> <p>It's not THE ultimate securing solution. It's just another layer preventing DIRECT access to specified port(s). After knocking you still might want to use good security practices to enable access to your services (i.e. disable root login w/ SSH, force certificate usage as much as possible, VPN your connections, etc.)</p></div>SamirMon, 30 Jun 2014 22:53:22 -0000https://sourceforge.netbf200b10a28d11931143342d7f46ad5b100f4bc9