Security researcher highlights years of unheeded warnings
2 Oct 30 · 12d ago · 4 posts · 1 source · development 2 of 2
Infosec researcher notes that VS Code's unsafe plugin model has been criticized for years, with Microsoft consistently refusing to implement safety controls and deferring responsibility to users.
“we, people who like things to have some reasonable baseline amount of safety in our everyday tools, have been complaining for years that VS Code's plugin model is absurdly unsafe and an absolute open sewer; Microsoft shrugs and says it's the user's responsibility”
0xabad1deaMicrosoft VS Code maintainer0xabad1dea Security researcher
The whole story posts the bright band is this development · numbered dots are the others · click one to jump
What people said 4 voices · verbatim
-
RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 With every passing day I become increasingly emboldened that it is not only “not radical” but in fact “the only right choice” to only ever run software you yourself write, and to never connect such software to a network. (No, I haven’t written my own kernel yet despite thinking I maybe…
-
A
RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 I would politely suggest that any theft of crypto 'currency' is just fastracking what will eventually happen to all crypto 'currency'. The Microsoft scandal is small beans compared to the crypto-ponzi scandal.
-
G
RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 I’m pretty sure she knows this, but the audience should be warned: DO NOT HOLD YOUR BREATH WAITING FOR MICROSOFT TO ADDRESS THIS
-
J
RE: https:// infosec.exchange/@0xabad1dea/1 17529823729259748 Anybody got a connection who can hook me up with an invitation to the medals ceremony in Pyongyang? Gonna be a hella party yo
All 2 developments of Major VS Code plugin compromised, pushes SSH backdoors →
Mastodon