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 yardstick on Thursday January 06, 2022 @12:34AM (#29819874)
> There's no way to lock out after N failures or even to rate limit attempts.

Given it’s a single machine with a /80, couldn’t the machine rate limit attempts to any IP in the /80? Ie rate limit by source, and separately rate limit by destination. Cover both bases.

[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by kadoban on Thursday January 06, 2022 @12:48AM (#29819937)
The way I understood it, only the correct IP address would even be connected to anything, the rest would just fail. You probably could do something like that, yeah.
[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by yardstick on Thursday January 06, 2022 @01:52AM (#29820261)
Good point, just had a look at the code. The NF queue will receive packets from all IPs in the /80 and they are all processed and validated by the ghost program that reads from the queue. So it could do the rate limiting there with full visibility.

https://github.com/aidansteele/ipv6-ghost-ship/blob/main/mai...

[ Parent | on HN ]