Post

jake
@yetanotheruseless.com

You (I) can't make this shit up. Fine, p(doom) += epsilon (p(hilarious) += lots more tho?)

1 repost5 likes

jake
@yetanotheruseless.com

summary: it wrote some hacky code to look at both /proc/net/tcp4 and /proc/net/tcp6 (but was only written to properly parse ipv4 addresses!) which magically turned out, out of all the 32bit ints it could get, to be owned by the pentagon. of all the timelines...

jake
@yetanotheruseless.com

It is random but not “chosen”: it peeked at its own VM’s ipv6, passed it through its own ipv4 parser, which grabbed bytes and int()’d it (truncating to last 4 bytes) which when turned into octets was by sheer dumb luck the pentagon

jake
@yetanotheruseless.com

Oh you were asking where the ipv6 address came from? I asked it to scan its local environment (my alignment lab’s staging env) for vulnerabilities - from the inside, without knowing its codebase, and one of its network addresses was this.

jake
@yetanotheruseless.com

“User (LLM) error”: it used the wrong arguments to its parser when it passed in the IPv6 address, got some garbage, grabbed the last four bytes of the garbage and figured those were the octets of the ipv4 address it was looking for, I think?

jake
@yetanotheruseless.com

I assigned it a write up as penance (plus writing “I will not hack the Pentagon” 100 times on the chalkboard, natch)