Technology

59374 readers

3250 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

692

All Windows users should immediately update their computers. An exploit rated 9.8/10 (CVE-2024-38063) compromises all devices running Windows with an IPv6 address. (msrc.microsoft.com)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

207 comments fedilink hide all child comments

archive

If you have the August 13, 2024—KB5041580 update. You're good.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -2 points 3 months ago (1 children)

Old tale, I know, but just cause v4 is running out on the internet it doesn't stop anyone from using it in their homes. I manage some ASNs on the internet. I have no need yet to worry about implementing v6 on the inside.

[–] [email protected] 13 points 3 months ago (1 children)

The thing is that if IPv6 were actually adopted, it would be straight up better. For everyone. It's easier to use if it's all the networking instead of just a niche case.

[–] [email protected] 3 points 3 months ago (1 children)

Yup, I know. What a pain to migrate it all.

[–] [email protected] 4 points 3 months ago (1 children)

It's really not though. ISPs are a problem, but every hosting provider I've used has offered IPv6. It's really trivial to setup IPv6 name DNS, and host a website on both IPv4 and IPv6. I just do it by default now.

Once it becomes the default to deploy to both, if IPv4 died then the IPv6 side would just keep working.

For DNS, you can make a single glue record contain an IPv4 and IPv6 address.
DNS just needs A and AAAA records for the Name servers. NS records still point to the hostname as normal.

For Web servers, the web server just needs to bind to the IPv6 address(es). Then in DNS just have an A and AAAA record for each website hostname. The server name directives will cover both.

There really isn't much to it right now. The technology is mature now. It used to be a pain, but now it isn't.

[–] [email protected] 2 points 3 months ago

It really is for me when I've got thousands of servers and hundreds of firewall rules, hundreds of subnets and routing to worry about.