You can relicense code. Though that doesn’t mean that you can take anything away. You just open another avenue for people to use what you wrote and developed, and any old license still exists and retains validity; the way you can curtail rights is by not granting liberal terms on newly created code.
This is how macOS switched to zsh, and left all GNU code in it to rot.
Pregnancy is a gatcha
Bold of you to assume that my offspring would be useful in some way.
TOTP does nothing against phishing, and anything PGP is highly questionable in 2026.
But, I agree about the FIDO U2F keys.
You’re saying one VM was cloned from the other. I could imagine a DHCP client saving leases to disk (they can have pretty long validity periods), and if the box was assigned the .106 address at any point and then cloned, the cloned machine would probably try to take that address, in other words ARP the address to determine if it’s taken, and if so, fall back to some other thing. I would have expected an APIPA address but 172.x.y.z is not out of the question depending on config.
Also, if your bridge has an interface connected to e.g. another ISP-provided router then it would expose any DHCP server running behind that interface to your VMs, creating a race.
Autists will also die if a wooden stake is driven through the heart.
As they are also vulnerable to silver bullets, maybe autists are werewolves, too?
Thanks to the wonders of capitalism, a bunch of businesses that would have to yield to tyrannical open source devs and their goody-two-shoes mentality can pool their bargaining power and each pay a little to a benevolent clean room reimplementer of security fixes.
Or, they can vendor the library and ask Claude to fix it in-tree 🤷