this post was submitted on 01 May 2024
225 points (100.0% liked)

Technology

68567 readers
4416 users here now

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


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
all 48 comments
sorted by: hot top controversial new old
[–] mindlight@lemm.ee 153 points 11 months ago (2 children)

PCWorld:

Microsoft’s latest Windows update breaks VPNs, and there’s no fix

What Microsoft actually said:

Windows devices might face VPN connection failures after installing the April 2024 security update, or KB5036893. We are working on a resolution and will provide an update in an upcoming release

I'm so fed up with everyone trying to make a quick buck on our constant struggle to stay safe.

[–] w2tpmf@lemmy.world 36 points 11 months ago* (last edited 11 months ago)

The reality is that it broke "something* in certain lpt2/ipsec connections using certain authentication protocols, although they haven't yet specified which particular connection technologies are affected.

However this does not mean that a blanket affect of ALL VPN connection not working is an issue.

So far we are unaffected on clients using ipsec and PAP protocol authentication, nor connections using Anyconnect (aka Cisco Secure Connect).

I have also not seen any affect on private VPN clients such as PIA or Nord on machines that have this update.

I suspect what broke was clients using MSChap, Microsoft's own protocol for authentication for VPN clients.

Source: an admin with 200+ client machines with VPN connections that are not impacted after installing this update.

[–] nublug@lemmy.blahaj.zone 12 points 11 months ago

absolutely bonkers take

[–] Imgonnatrythis@sh.itjust.works 74 points 11 months ago (4 children)

I dunno man. I'm convinced that pretty much any mention of VPN these days is just an ad for vpns. That's with this article looks like.

[–] zaemz@lemmy.world 42 points 11 months ago (1 children)

Yeah, you're not wrong that the article kinda sets itself up for the "lookit our recommended VPNs" pitch.

There's no way Microsoft would purposefully disable VPNs from working. I can guarantee that they require VPNs for thousands of roles in the company, let alone breaking it for government agencies that require VPNs, etc.

It is good to know that a specific update can break something ahead of time, though. Then at least you can avoid it.

[–] Kiernian@lemmy.world 16 points 11 months ago

There's no way Microsoft would purposefully disable VPNs from working

No, but they've done it accidentally before.

One time a few years ago it broke all LT2P VPN's unless you removed a specific KB########.

IIRC, six months later there was still no fix.

I think it's been fixed now, though.

[–] db2@lemmy.world 27 points 11 months ago (1 children)

And now a word from our sponsor, Nor-

[–] Kethal@lemmy.world 8 points 11 months ago* (last edited 11 months ago) (2 children)

My workplace requires VPN for Web sites that are authenticated, require 2FA and are encrypted. It's infuriatingly stupid. I feel like someone higher up got sold a useless contract by a good VPN salesperson.

[–] BearOfaTime@lemm.ee 15 points 11 months ago (1 children)

I applaud your IT leadership/CIO for being willing to do this.

Most companies are far too passive and think "aIt won't happen to us".

I've seen companies scammed of $1mil in a single transaction because they sent credentials in email, to a scammer.

Had they used a credential management system this wouldn't have happened.

Every layer of security helps.

[–] Kethal@lemmy.world 1 points 11 months ago

Yeah, maybe they should encrypt it a third time. You never know.

[–] NGC2346@sh.itjust.works 1 points 11 months ago

Its actually real news

[–] cy_narrator@discuss.tchncs.de 27 points 11 months ago

It may be unintentional bug. People in the enterprise world need VPN for corporate purposes, they will fix it dont worry

[–] sgibson5150@slrpnk.net 23 points 11 months ago (1 children)

Doesn't seem to have impacted Wireguard.

[–] MakePorkGreatAgain@lemmy.basedcount.com 23 points 11 months ago* (last edited 11 months ago) (1 children)

thats going to be an issue - at my work roughly 60% of the userbase is connected via VPN at any given point - so, ~40,000 people or so

[–] Qwaffle_waffle@sh.itjust.works 1 points 11 months ago

That's a paddlin.

[–] BaroqueInMind@kbin.run 13 points 11 months ago* (last edited 11 months ago)

Looks like their policy to prefer cheap labor they hire from Asia rather than paying local U.S. developers a living wage is starting to bite them in the ass.

[–] tsonfeir@lemm.ee 11 points 11 months ago

Obligatory Linux plug.

[–] Holzkohlen@feddit.de 5 points 11 months ago

You are gonna test the software for a multi-billion dollar cooperation and you are gonna like it!

[–] Melatonin@lemmy.dbzer0.com 4 points 11 months ago (1 children)

Is it too late to turn off security updates and avoid this issue?

[–] BearOfaTime@lemm.ee 3 points 11 months ago (1 children)

And this is exactly why I don't do auto updates (and people around here berate me for it, saying my systems are unsafe).

Hell, Windows LTSC only gets updates twice a year (which is what I run).

LTSC is great.
Much less bloat and bs too.