Conversation

Notices

1. MMN-o ✅⃠ (mmn)'s status on Sunday, 08-May-2016 15:32:41 EDT MMN-o ✅⃠

   • maiyannah
   @maiyannah your site doesn't even ask for a captcha but just kills the connection for us #tor users ;)
   • MMN-o ✅⃠ (mmn)'s status on Sunday, 08-May-2016 16:37:45 EDT MMN-o ✅⃠

     • maiyannah
     @maiyannah Protip: If ssh is bruteforced you can block just port 22. :)
     Evenproertip: Don't run ssh on port 22 in the first place!
   • MMN-o ✅⃠ (mmn)'s status on Monday, 09-May-2016 07:26:58 EDT MMN-o ✅⃠

     • maiyannah
     @maiyannah No, but it'll make your logs much less spammy. So it's a practical solution not a secure solution.
   • MMN-o ✅⃠ (mmn)'s status on Monday, 09-May-2016 07:28:57 EDT MMN-o ✅⃠

     • bob
     • maiyannah
     @bob But regardless of authentication method you're still vulnerable to 0days, which are less likely to strike on non-port-22 ports.
     (though as @maiyannah said changing ports isn't a secure solution, as there are search engines indexing services on all ports).