Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

91–100 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

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

i love how the low bits of the addresses in hex are cognates for both the section and the actual content of the name/line.

also, looking glasses... jeez. i haven't heard or thought of those in _years_.

Re: Engineer distributes resume via IPv6 traceroute

#92
post #44
post #39

Earlier quoted context omitted.

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.

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

#93

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

It’s because practical experience with technologies like BGP is difficult to acquire without sufficient capital to run a network. You can of course purchase a /24 and dabble (search HN for blog posts describing exactly that). And you can experiment with large deployments in simulators. But network optimization is inherently more of a practical pursuit than a theoretical one, so most broad and consistent learning oppo…

You can contribute to the Solana core tech team, with the incentive alignment of underlying token value as a partial backer!

I think they're doing some really cool stuff on the network optimization level. As an example, Solana recently implemented QUIC in its latest release: https://github.com/solana-labs/solana/projects/74

Re: Engineer distributes resume via IPv6 traceroute

#94

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

It’s because practical experience with technologies like BGP is difficult to acquire without sufficient capital to run a network. You can of course purchase a /24 and dabble (search HN for blog posts describing exactly that). And you can experiment with large deployments in simulators. But network optimization is inherently more of a practical pursuit than a theoretical one, so most broad and consistent learning oppo…

> search HN for blog posts describing exactly that

Know any offhand? Search is a bit tough for a common number like 24. The concept sounds interesting

Re: Engineer distributes resume via IPv6 traceroute

#95
post #6
post #3

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

No A record, so I guess so. If your ISP doesn't block ICMP, you can get IPv6 capabilities using tunnels like https://tunnelbroker.net/ . Especially useful if you have a router you can configure this stuff on so all of your devices get IPv6 for free. Completely free of charge and with minimal latency if you live somewhere near a data centre.

Netflix and friends won’t work over them. But with some clever routing, you can get it to work… I just got native ipv6 last winter and had to use tunnels like this for years.

Re: Engineer distributes resume via IPv6 traceroute

#96
post #60

Earlier quoted context omitted.

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…

Believe it or not, you might have very specific interests :)

If a 13 year old was using irc regularly in 2022 I would be concerned for them. Not thata 13 year old shouldn't use irc but I would wonder how they found that destination, especially given the countless other sinks for internet denizens

Re: Engineer distributes resume via IPv6 traceroute

#97

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

It’s because practical experience with technologies like BGP is difficult to acquire without sufficient capital to run a network. You can of course purchase a /24 and dabble (search HN for blog posts describing exactly that). And you can experiment with large deployments in simulators. But network optimization is inherently more of a practical pursuit than a theoretical one, so most broad and consistent learning oppo…

it's ipv6 so a /120 would do!

Re: Engineer distributes resume via IPv6 traceroute

#98
post #49

Great, but not Bad Horse great. https://www.a2wd.com/traceroute-bad-horse/

No wonder we're running out of IPv4 addresses.

It's only a /27, they were quite affordable a year or ten ago. A full /24 went for about $2500 back in 2015 when this was made and you can subdivide that to 8 customers who all get 30 usable addresses. Bit expensive for a joke, but not unmaintainably so.

It's silly that ISPs have messed up their IPv6 deployment so badly that there's a "shortage" of IPv4 addresses now. Of course, IPv4 was never going to be enough; there are too many people on earth.

Re: Engineer distributes resume via IPv6 traceroute

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

He must have added Apple at some point. Here's what I got (using mtr):

    19. hello                                                   0.0%    14  141.6 140.5 139.1 141.6   0.7
    20. my.name.is.louis.poinsignon                             0.0%    14  141.9 142.1 141.2 143.3   0.5
    21. i.am.a.network.and.systems.engineer                     0.0%    14  140.5 140.4 139.7 141.6   0.5
    22. this.is.my.resume.over.traceroute                       0.0%    14  140.5 140.4 140.0 141.5   0.5
    23. o---experience---o                                      0.0%    14  139.9 140.4 139.4 141.4   0.5
    24. 2021.apple.engineer.sf.usa                              0.0%    14  140.7 140.5 139.8 141.2   0.4
    25. 2018.cloudflare.engineer.sf.usa                         0.0%    14  140.8 140.4 139.4 142.8   0.9
    26. 2017.cloudflare.engineer.london.uk                      0.0%    13  142.2 142.6 141.4 147.5   1.5
    27. 2016.cloudflare.engineer.intern.sf.usa                  0.0%    13  149.7 141.2 139.1 149.7   2.7
    28. o---education---o                                       0.0%    13  142.1 142.1 141.3 144.1   0.7
    29. 2015-2016.drexeluni.exchange.ce.philadelphia.usa        0.0%    13  140.9 140.3 139.5 141.3   0.5
    30. 2011-2016.utt.master.ce.france                          0.0%    13  143.1 142.3 140.8 143.3   0.7
    31. o---skills---o                                          0.0%    13  140.3 140.9 139.7 146.0   1.6
    32. golang.c.python                                         0.0%    13  142.2 142.4 141.1 146.0   1.2
    33. networks.linux.automation.kafka.clickhouse.kubernetes   0.0%    13  139.6 140.5 139.3 142.2   0.8
    34. statistics.maths                                        0.0%    13  141.6 142.1 141.2 142.8   0.5
    35. o---various---o                                         0.0%    13  141.8 142.4 141.8 144.8   0.8
    36. swimming.karate.piano                                   0.0%    13  139.8 141.4 138.7 155.2   4.2
    37. o---contact---o                                         0.0%    13  140.1 140.3 138.6 141.7   0.8
    38. mail.jobs.at.poinsignon.org                             0.0%    13  141.1 142.5 141.1 145.4   1.1
    39. cv6.poinsignon.org                                      0.0%    13  139.4 140.3 139.4 141.2   0.5

Re: Engineer distributes resume via IPv6 traceroute

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

I think that many HRs would be suspicious about somebody who worked at each job for 2.261 ms.

It's contracting work, so the short duration makes sense!
Post reply on HN