Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

111–120 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

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

How would you spoof arbitrary IPs? IIUC it's poked at as the next hop...? (Mhm, embarrassingly out of the loop)

I _think_ that if you know the real source and real destination of an ICMP message, you can just forge back a message with an arbitrary TTL exceeded message, from any "I'm IP address xxx" address. Those can come from a lot of rando IPs because the intent of them is just "at this hop, the TTL ran out", and the hops the original sender wouldn't know anyway. A lot of fake hops would be essentially impossible if you examined the real BGP routes and stuff, but verifying that in real time sounds hard enough that I bet nobody bothers.

I'd have to do a lot more research and testing to verify though, not something I've played with in practice, and obviously my terminology isn't even right above, so take it for what it's worth.

Re: Engineer distributes resume via IPv6 traceroute

#113

Earlier quoted context omitted.

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!

You can easily obtain a /44 and your own ASN as an individual, through various RIPE LIRs, no questions asked. If you're in the US, you'll have to procure an overseas VPS so you have a European presence.

Re: Engineer distributes resume via IPv6 traceroute

#115
post #83
post #61

"That's very nice but can you email me a copy in Microsoft Word DOCX format please?"

I’m just about to live this hell. On advice from a friend, my response will be a simple one: no, because it doesn’t exist. It was written in Markdown [0]. Here’s a PDF. I’m expecting the usual pushback, and will reciprocate. I’ll let you know how it goes. [0]: https://github.com/johnnydecimal/resume/blob/main/resume.md (Yeah I shamelessly inserted my own résumé.)

Went through this. Gave up and remade it in Word. Practical beats pure sometimes. Tough for us HN types.

Re: Engineer distributes resume via IPv6 traceroute

#116
post #92
post #44

Earlier quoted context omitted.

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…

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

Re: Engineer distributes resume via IPv6 traceroute

#117

Earlier quoted context omitted.

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

I'm curious why you would be concerned. I've seen a good number of teenagers hanging around and playing with computers.

Re: Engineer distributes resume via IPv6 traceroute

#118

Earlier quoted context omitted.

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!

2.261ms, aka a billable hour!

Re: Engineer distributes resume via IPv6 traceroute

#119

Earlier quoted context omitted.

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

I'm curious why you would be concerned. I've seen a good number of teenagers hanging around and playing with computers.

[deleted]
Post reply on HN