512

AMD won't patch all chips affected by severe data theft vulnerability — Ryzen 3000, 2000, and 1000 will not get patched for 'Sinkclose' (www.tomshardware.com)

submitted 3 months ago by TheHolm@aussie.zone to c/selfhosted@lemmy.world

183 comments fedilink hide all child comments

Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.

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

[-] ipkpjersi@lemmy.ml 22 points 3 months ago* (last edited 3 months ago)

Yay, another BIOS update!

I am getting so sick of all these BIOS updates because of all these security vulnerabilities all the time. It is so tiring having to set up my settings all over again all of the time. Earlier this year, or maybe it was last year, it felt like every month or two there was a new BIOS update for a new security vulnerability.

[-] semperverus@lemmy.world 5 points 3 months ago

Back your settings up and restore them then.

[-] ipkpjersi@lemmy.ml 10 points 3 months ago* (last edited 3 months ago)

Depending on your BIOS and/or motherboard, you can't restore them between versions. The point of clearing the BIOS settings after flashing a new version is to ensure that you only have values that are expected, which is why restoring backups can often be blocked between versions.

[-] EddoWagt@feddit.nl 2 points 3 months ago

I learned this the hard way when I lost all my fan profiles

[-] ipkpjersi@lemmy.ml 1 points 3 months ago

Thankfully that's one thing that can be restored between BIOS versions for my motherboard lol

[-] EddoWagt@feddit.nl 2 points 3 months ago

Not on mine :(

this post was submitted on 12 Aug 2024

512 points (95.7% liked)

Selfhosted

40383 readers

649 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz