Re:Engineer distributes resume via IPv6 traceroute
by tyingq on Friday August 26, 2022 @02:38PM
(#32611142)
Sure, another way to do it, though the python would have to get the peer address, extract 64 bits of the incoming msg, table lookups of hop count -> forged address, decrement hop counts, etc. A shell script creating virtual interfaces and routing wouldn't likely be much longer than 20-30 lines either.
[ Parent
| on HN ]
Re:Engineer distributes resume via IPv6 traceroute
by mrb on Friday August 26, 2022 @05:31PM
(#32612994)
There is no need to do "table lookups of hop count" or to "decrement hop counts". The IP TTL value is just a field that can be read from the IP header, which is trivial since the Python would get the entire IP header from the raw socket. If you see a TTL=1 you send back the forged response as coming from $IP_1, if you see a TTL=2 you forge the response as coming from $IP_2, etc. The forged response can always contain the same default TTL.
Re:Engineer distributes resume via IPv6 traceroute
by tyingq on Friday August 26, 2022 @08:16PM
(#32614263)
> table lookups of hop count -> forged address
>> There is no need to do "table lookups of hop count"
>> If you see a TTL=1 you send back the forged response as coming from $IP_1, if you see a TTL=2 you forge the response as coming from $IP_2
You're describing a table lookup of the forged address using the hop count.