Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

41–50 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

#41
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

Oh noes you just doxxed their email address on the https

Re: Engineer distributes resume via IPv6 traceroute

#42
post #21
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

So is that mail.jobs@ or mail+jobs@... or jobs@ A total flop on the last line

Not really. From the lines above one can deduce that the dot represents space or colon, for obvious technical reasons. As such, I'd interpret

  mail.jobs.at.poinsignon.org
as

  mail: jobs@poinsignon.org

Re: Engineer distributes resume via IPv6 traceroute

#43
post #18
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

Why have you traceroute ip instead of domain?

you could have multiple IPs attached to a domain which could mess up this trick.

I also wonder why not use use the domain, much easier.

Re: Engineer distributes resume via IPv6 traceroute

#44
post #39
post #17

Earlier quoted context omitted.

Not sure how he did it, but my first guess would be just a bunch of virtual interfaces on a linux box with a->b->c->d->e->etc routing, and something like the tc command[1] to add enough latency to each one that traceroute sees them all. If he's scripted it to do all the virtual nic creation and dns ptr entries, it would be interesting to see. [1] https://bencane.com/2012/07/16/tc-adding-simulated-network-l...

Virtual interfaces aren't necessary, and would be overkill. All he needs on his server is to listen on a raw network socket, read the incoming packet's IP TTL value, then forge and send an ICMP "time exceeded" response with the source IP address set to a value that depends on the TTL. The entire thing could be done in 20-30 lines of Python. Next to that he set up a DNS server configured with PTR records that map thes…

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.

Re: Engineer distributes resume via IPv6 traceroute

#45
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

> Cloudflare.NetworkEngineer Ah, that explains a lot. Not that anyone else couldn't do such a thing, but I feel like even amongst more "hacker" types it takes a relatively specialized background to pull a trick like this (at least statistically; I'm sure there are outliers).

Feels like we’re a dying bread with everything cloud first and serverless.

Re: Engineer distributes resume via IPv6 traceroute

#46
post #18
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

Why have you traceroute ip instead of domain?

> Host mail.jobs.at.poinsignon.org not found: 3(NXDOMAIN)

(A bit of a missed opportunity; the author should really set a AAAA record there IMHO)

There's no actual requirement that your PTR records resolve back to the same IP. Historically very little software bothered to check, and most of the Unix-y diagnostic software has never been updated to do so...

Re: Engineer distributes resume via IPv6 traceroute

#48
post #18
post #7

Here's what it looks like: $ traceroute cv6.poinsignon.org traceroute to cv6.poinsignon.org (2001:bc8:3eff:c0::ff), 30 hops max, 80 byte packets 1 gateway 0.795 ms 0.789 ms [...] 8 hello (2001:bc8:3eff:c0::1) 1.431 ms 1.202 ms 9 My.name.is.Louis.Poinsignon (2001:bc8:3eff:c0::2) 1.649 ms 1.274 ms 10 I.am.a.network.and.systems.Engineer (2001:bc8:3eff:c0::3) 1.695 ms 2.090 ms 11 This.is.my.resume.over.traceroute (2001:b…

Why have you traceroute ip instead of domain?

Bad copy/paste
Post reply on HN