-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > I'd recommend fail2ban or equivalent instead.
Right, thanks. I planned on mentioning SSH-protecting daemons, but forgot. I've had better luck with SSHGuard, but fail2ban is the most common option. On 11/18/2014 11:45 AM, Zack Weinberg wrote: > On Tue, Nov 18, 2014 at 11:15 AM, Toralf Förster > <toralf.foers...@gmx.de> wrote: >> On 11/18/2014 04:28 PM, Jeroen Massar wrote: >>> People should realize though that it is not 'safer' in any way >>> running SSH on another port. >> >> But it is (slightly) more expensive - which counts, or ? > > In my limited experience, moving SSH to another port made no > apparent difference to the number of random attempts to break in. > I'd recommend fail2ban or equivalent instead. > > zw _______________________________________________ tor-relays > mailing list tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUa4xDAAoJELxHvGCsI27Nd9UP/2sXNuxrmhcgii45VX+Jj17l 3XFMyCd4bT9gSyjVeO6TKaLsnWZaiIGkZq6P0HfzRylfKfaPCsSTvbV1kTTcrWKo LMQCmJIEmYHll6yCwfW/yWNFWhBiKSs8zccynw/hDXtKg0aN0ibWFUIF0jfV8O/R npu5JsDMbf98O+oJ08Y3lWH54z7fzsPzisvlERu+Q3exUDErlOBsENPyt6IlAe7k mrij/5xd3hed3LcMepWZyV1JGB4yEfQYa5Kx06O4wQ9by4uuhNV/Y1P2qLXUhzX3 Sx7ZrYzSXP3gsgr6icItxf4sWLZMLcdQxnvdGY8x9SWWh8w8GzTHqQvnwFGr06H+ tjmYuHbowgFjHaFxKal362UiJRNxFBZSExuV4RcTX3Nt4bmdTTQNfBZAZHMpKyay XVX7dIMhs6oNa9q+PxmBFCXvn5cK25i36TrnDQU1JdMo6YQf6wkbgctRwTqiVlA+ V0OE9dSQVMsp5GlCOJhAYFYEdE8A+kTJq3hZjfzrlE00GX5bjcCHz/m0Srty3gU/ hvzRe+CzbinIKowwlvljfbU7xaQbo2XYspdSHw3sIuhuyRTMJYp5ToXI2n71w/ED eU1lALWKIN9UM2kf/oMOJYWRzkOazwnav9pb1NVTfeqD+DC8uDrAJt5zYzkGdOfh 1J6gjitEaUxhZENrlPlH =iUZD -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
