Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

51–60 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

#51
post #38
post #3

I guess the site can only be reached over IPv6? It seems I only have IPv4 :(

That could be a feature if he didn't want to work at companies that don't have a IPv6 network :)

Doesn't seem to be the case, apple.com does not have an AAAA record. :(

Also shame on Microsoft for no full IPv6 support in WSL2.

(The CV posted above is outdated, this is what the traceroute shows today)

  8    37 ms    36 ms    36 ms  hello [2001:bc8:3eff:c0::1]
  9    32 ms    32 ms    31 ms  My.name.is.Louis.Poinsignon [2001:bc8:3eff:c0::2]
 10    33 ms    32 ms    31 ms  I.am.a.network.and.systems.engineer [2001:bc8:3eff:c0::3]
 11    35 ms    36 ms    35 ms  This.is.my.resume.over.traceroute [2001:bc8:3eff:c0::4]
 12    37 ms    35 ms    36 ms  o---Experience---o [2001:bc8:3eff:c0:ee::]
 13    36 ms    35 ms    35 ms  2021.Apple.Engineer.SF.USA [2001:bc8:3eff:c0:ee::714]
 14    33 ms    34 ms    31 ms  2018.Cloudflare.Engineer.SF.USA [2001:bc8:3eff:c0:ee::cf3]
 15    32 ms    34 ms    33 ms  2017.Cloudflare.Engineer.London.UK [2001:bc8:3eff:c0:ee::cf2]
 16    38 ms    36 ms    35 ms  2016.Cloudflare.Engineer.Intern.SF.USA [2001:bc8:3eff:c0:ee::cf1]
 17    36 ms    35 ms    34 ms  o---Education---o [2001:bc8:3eff:c0:ed::]
 18    36 ms    35 ms    34 ms  2015-2016.DrexelUni.Exchange.CE.Philadelphia.USA [2001:bc8:3eff:c0:ed::1]
 19    37 ms    32 ms    32 ms  2011-2016.UTT.Master.CE.France [2001:bc8:3eff:c0:ed::2]
 20    37 ms    34 ms    35 ms  o---Skills---o [2001:bc8:3eff:c0:51::]
 21    36 ms    36 ms    34 ms  Golang.C.Python [2001:bc8:3eff:c0:51::1]
 22    36 ms    34 ms    36 ms  Networks.Linux.Automation.Kafka.Clickhouse.Kubernetes [2001:bc8:3eff:c0:51::2]
 23    33 ms    33 ms    33 ms  Statistics.Maths [2001:bc8:3eff:c0:51::3]
 24    31 ms    32 ms    31 ms  o---Various---o [2001:bc8:3eff:c0:7a::]
 25    34 ms    35 ms    35 ms  Swimming.Karate.Piano [2001:bc8:3eff:c0:7a::1]
 26    36 ms    34 ms    35 ms  o---Contact---o [2001:bc8:3eff:c0:c0::]
 27    32 ms    34 ms    31 ms  mail.jobs.at.poinsignon.org [2001:bc8:3eff:c0:c0::1]
 28    33 ms    35 ms    30 ms  cv6.poinsignon.org [2001:bc8:3eff:c0::ff]

Re: Engineer distributes resume via IPv6 traceroute

#54
Doesn't work here.

  ALARM ~ $ tracepath 2001:bc8:3eff:c0::ff
   1?: [LOCALHOST]                        0.015ms pmtu 1500
  ...
  ...
   2:  ALPHEUS-COM.edge1.Washington1.Level3.net             15.966ms 
   3:  ae5-3828.edge1.Washington1.Level3.net                 4.011ms 
   4:  2001:1900:2::3:18                                    77.693ms 
   5:  2001:1900:5:2:2::4a0a                                78.469ms asymm  4 
   6:  2001:bc8:400:1::8a                                   78.737ms asymm  7 
   7:  2001:bc8:400:1::13a                                  78.635ms asymm  6 
   8:  no reply
   9:  no reply
  10:  no reply
  11:  no reply
  12:  no reply
  13:  no reply

Re: Engineer distributes resume via IPv6 traceroute

#55
post #45

Earlier quoted context omitted.

> 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.

Dying breed? Though dying bread sounds like an interesting metaphor.

Re: Engineer distributes resume via IPv6 traceroute

#56
post #45

Earlier quoted context omitted.

> 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.

Eh, smaller slice of a bigger pie. Somebody has to make "the cloud" work so that everybody else doesn't have to worry about the underlying bits as much.

Re: Engineer distributes resume via IPv6 traceroute

#57
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…

For maximum 'performance' you can do it in-kernel with eBPF :^) https://github.com/simmsb/traceroute-spoof

Re: Engineer distributes resume via IPv6 traceroute

#58
post #42
post #21

Earlier quoted context omitted.

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

Yes really, you can see even in the other replies the interpretations are not 100% clear.

It took me a minute to realize it wasnt some form of "mail+jobs" or "mail.jobs". It wasnt until I wrote the last line of my comment that it was "mail jobs@"

Re: Engineer distributes resume via IPv6 traceroute

#59
post #21

Earlier quoted context omitted.

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

I bet if he can do this trace route thing, he can get all those emails going to his own domain regardless of who they are addressed to

I would presume a better way would be to not make people feel unsure of what it is, and just pick something thats super clear.

Re: Engineer distributes resume via IPv6 traceroute

#60
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).

This is a very old and oft-repeated trick though.

https://github.com/blechschmidt/fakeroute

https://github.com/antifork/hopfake

https://github.com/jprenken/rickroute

https://github.com/sams-gleb/ipv4-traceroute-fake

https://github.com/job/ipv6-traceroute-faker

And so on…

I remember being a 13yo kid sitting on IRC doing exactly this for fun years ago back when IP addresses were cheap and easy to come by. But spoofing military IPs in the traceroute was more fun.

Post reply on HN