339
Chrome, Firefox and other browsers affected by critical WebP vulnerability
(siliconangle.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Sep 2023
339 points (98.8% liked)
Technology
60035 readers
2871 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 2 years ago
MODERATORS
Welp, time to update my browser after months.
Not updating a browser strategically is like ... one of the worst ideas possible. The most vulnerable part of your system, interfacing directly with the biggest if not only source of malware and other threats, being outdated and not updated while critical patches you didn't hear about or are so dangerous that they weren't mentioned yet and silently patched can attack you at every click you do is the single most dangerous thing to do.
I know, but I only have slow mobile data. To be honest I thought the update would be larger than 60MB. I probably confused Firefox with some other, larger package I wanted to avoid downloading besides supertuxkart and libreoffice-still.
The whole package is just 63 MB in Arch's repos, not calculating the dependencies. I'd imagine there to be a solution to filtering those packages from updating with the normal update command, whatever package manager you may be using.