News for hackers. Stuff that matters.

A comment on IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 address. Parent comment

Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by jacob019 on Thursday January 06, 2022 @12:05AM (#29819661)
A /80 prefix is equivalent to 65536 ipv4 Internets. Not so brute-forceble.
[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by lmz on Thursday January 06, 2022 @12:17AM (#29819737)
The random part is six digits. I'd say pretty brute-forceable.
[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by AaronFriel on Thursday January 06, 2022 @02:45AM (#29820579)
The TOTP spec (rfc6238) allows up to 10 digits or 10 billion unique values, a bit bigger than IPv4's space.

Running anything like fail2ban on IP address misses would stop brute forcing in its tracks.

[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by kadoban on Thursday January 06, 2022 @03:00AM (#29820673)
Both good ideas.

None of this fixes even a passive mitm attack, but it's still better.

[ Parent | on HN ]