Live data from Hacker News

Engineer distributes resume via IPv6 traceroute

cv6.poinsignon.org

131–140 of 162 posts

Re: Engineer distributes resume via IPv6 traceroute

#131
post #126

Earlier quoted context omitted.

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 exam…

If you return fake IPs in a traceroute you won't be able to control the reverse DNS which is the point of this exercise.

I understood this current thread to be another, separate, stupid ICMP trick. I wouldn't think the two tricks can be combined.

Re: Engineer distributes resume via IPv6 traceroute

#132

Earlier quoted context omitted.

My interpretation was mail: jobs@poinsignon.org

My interpretation would be mail+jobs@example.com, given that it's become the de facto standard, and mail@example.com looks like his main one.

I'm not sure it can be a de facto standard with the number of sites that flatly refuse to recognize + as a valid character in email addresses. There's so many that I gave up and started just using . instead.

Re: Engineer distributes resume via IPv6 traceroute

#133

Earlier quoted context omitted.

Sure thing! unzip resume.docx; cd resume; dd if=/dev/random of=crap.tax bs=1M count=19;cd ..; zip resume.docx resume

You're going to be sitting there for a while waiting for blocking random to fill 19MB. You want urandom.

These days, blocking random isn't a thing anymore. /dev/random and /dev/urandom just do the same non-blocking operation.

Re: Engineer distributes resume via IPv6 traceroute

#134
post #18

Earlier quoted context omitted.

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

Unless you send email.

Re: Engineer distributes resume via IPv6 traceroute

#135
post #128

Earlier quoted context omitted.

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

Are they still using that hand-wavy "cryptographic proof that a duration of time has passed"?

Do you mean Proof of History? The concept is made concrete in Solana, but actually any blockchain that hashes a set of transactions in each of its successive slots/blocks can be used to prove that time has passed.

You can verifiably be assured of a temporal ordering between transactions that were hashed in different slots because the output of a slot/block is hashed and used as an input for the next block/slot.

Re: Engineer distributes resume via IPv6 traceroute

#136
post #116
post #92

Earlier quoted context omitted.

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.

Right, I understand you now.

Re: Engineer distributes resume via IPv6 traceroute

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

Remember when they said we'd never run out of IPV6 addresses? Good times.

Will age just like the famous quotes about 640K of memory is enough.

Re: Engineer distributes resume via IPv6 traceroute

#139

Earlier quoted context omitted.

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.

Yesterday i was watching LSD documentary (https://www.netflix.com/title/80229847). They briefly stated that LSD usage in California was very likely to have accelerated invention of computers. It helped people with problem solving.

Re: Engineer distributes resume via IPv6 traceroute

#140

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…

Fun Fact ; I'm not sure if it was RIP or BGP, but a certain Cisco Founder stated that they wouldnt have come up with the routing protocol if it weren't for Hoffman and LSD.

Would love to read more about this.
Post reply on HN