Re:Going IPv6 Only [pdf]
by Symbiote on Wednesday June 27, 2018 @06:58PM
(#17412619)
Statistics since 1 June:
An SSH server on port 22, home broadband connection: 212k failed IPv4 login attempts, zero failed IPv6 login attempts.
An SSH server on port 22, university connection: 269k failed IPv4 login attempts, zero on IPv6.
> If you just choose a completely arbitrary IPv6 address in your subnet for the server, random bad guys won't find it.
So that is true, but it also seems they won't even bother looking. My computer is as obvious as I can make it, it's listening on 2001:xxxx:xxx0::1/44, and still has had no attempts. Nothing on port 80 either.
And of course, there's nothing to prevent having several IPs on one machine, each for a different service. A DNS name for a web server then isn't revealing a possible SSH server.
An SSH server on port 22, home broadband connection: 212k failed IPv4 login attempts, zero failed IPv6 login attempts.
An SSH server on port 22, university connection: 269k failed IPv4 login attempts, zero on IPv6.
> If you just choose a completely arbitrary IPv6 address in your subnet for the server, random bad guys won't find it.
So that is true, but it also seems they won't even bother looking. My computer is as obvious as I can make it, it's listening on 2001:xxxx:xxx0::1/44, and still has had no attempts. Nothing on port 80 either.
And of course, there's nothing to prevent having several IPs on one machine, each for a different service. A DNS name for a web server then isn't revealing a possible SSH server.