Engineer distributes resume via IPv6 traceroute
61–70 of 162 posts
Re: Engineer distributes resume via IPv6 traceroute
#62That's how it's done probably https://github.com/blechschmidt/fakeroute
Re: Engineer distributes resume via IPv6 traceroute
#63That's how it's done probably https://github.com/blechschmidt/fakeroute
Except this doesn't have custom text. All the IP addresses correspond to real domain names
Re: Engineer distributes resume via IPv6 traceroute
#64I recall seeing something similar a while back, you'd traceroute to some IP address and the output was the opening text of a star wars movie https://www.theregister.com/2013/02/15/star_wars_traceroute/
telnet towel.blinkenlights.nlRe: Engineer distributes resume via IPv6 traceroute
#65Doesn'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…
[edit]
Note that "tracepath -m60 bad.horse" works just fine.
Re: Engineer distributes resume via IPv6 traceroute
#66Here'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 really unfortunate, and I mostly blame Cisco and Juniper. They suffocated an entire academic discipline with obfuscated terminology driven more by their business models than anything resembling the OSI model or open standards. That’s why WireGuard feels like such a breath of fresh air after 20 years of L2TP/IPSec.
I applaud companies like Cloudflare and Fly.io for their openness in sharing techniques and open sourcing so much of their code. It goes a long way toward lowering the barriers to self-teaching and experimenting with the latest networking software. And I’m sure HR is happy about the increasingly large applicant pool of qualified networking engineers – even if some hires do eventually leave by advertising their resume to anyone who sends them an IPv6 trace-route :)
Re: Engineer distributes resume via IPv6 traceroute
#67See also: traceroute -m 60 bad.horse
Re: Engineer distributes resume via IPv6 traceroute
#68Earlier quoted context omitted.
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
#69Re: Engineer distributes resume via IPv6 traceroute
#70Here'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
Doxxing usually implies ill intent but having your personal information broadcast to HN is likely only to result in a few of the hiring managers that haunt here sending a cold offer.