News for hackers. Stuff that matters.
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by FL410 on Thursday January 06, 2022 @10:36AM (#29824840)
And to me, this is part of the problem with IPV6. This HUGE amount of space that results in "why not" numbering, also means long hexadecimal IP addresses that no one can ever remember. The ship has sailed, but adding an octet to IPV4 and not planning to assign 28912479812 IP addresses to a toaster would have been so much easier.
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by reincarnate0x14 on Thursday January 06, 2022 @12:06PM (#29826217)
You're not supposed to be remembering addresses, that's what DNS and LLNMR et al are for. IPv4 let people depend on bad habits and hard-coded fixups, V6 makes that slightly less practical.

Although frankly the functional part of most V6 addresses isn't that much more. Using ULA, of which there are enough of that organizations need not fear constant overlap like 10/8, the network side of our private internet space is only 6 characters and fixed host addresses are often 2. eg, fde3af::1.

We get cute with 6to4 mappings and some routing games and so they may look more like fde3:af00:12:34::1 but the local subnet is handed out via prefix delegation so end users rarely, if ever, need to care.

Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by nybble41 on Thursday January 06, 2022 @03:23PM (#29829511)
> Using ULA … the network side of our private internet space is only 6 characters

How do you fit the fixed 8-bit ULA prefix (fd00::/8) plus the 40 random bits you're supposed to use for the Global ID (per RFC 4193) into six hex characters? It should be at least 12, e.g. fdXX:XXXX:XXXX::/48.

As for remembering addresses, yes, just use (m)DNS. You can even set up an mDNS Discovery Proxy[0][1] so that devices which don't support mDNS themselves can resolve the names via regular unicast DNS.

[0] https://www.rfc-editor.org/rfc/rfc8766.html

[1] https://github.com/mkuron/mdns-discovery-proxy

Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by reincarnate0x14 on Thursday January 06, 2022 @03:36PM (#29829696)
What few private organizations I've seen working with ULA ... are not using really random global IDs. I'm sure larger scale organizations are following RFC4193 more honestly, but getting V6 going at all versus ever more horrifying NAT contraptions in industrial networks is usually enough of a victory for me.
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by bigiain on Thursday January 06, 2022 @11:30AM (#29825668)
Remembering ip addresses is like remembering passwords.

Why would you do that, when there are so many good tools you can use to do it for you way better than your feeble grey meat sack can?

I mean sure, I remember 127.0.0.1 and 8.8.8.8 and 9.9.9.9, but decent passwords these days are no more memorable than ipv6 addresses.