this post was submitted on 13 Jun 2026
324 points (99.4% liked)

Technology

85357 readers
3813 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 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
324
AMD changes rules, denies researcher $10,000 bounty after taking 124 days to patch security flaw (www.techspot.com)
submitted 9 hours ago by sanitation@lemmy.today to c/technology@lemmy.world
28 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] themachinestops@lemmy.dbzer0.com 1 points 2 hours ago* (last edited 1 hour ago) (1 children)

They use https now, but use CRC for signature verification:

AMD told MrBruh that all update communications now use HTTPS and that updates undergo signature verification. The researcher says he verified the HTTPS claim, but found only a CRC32 check on the downloaded executable, which is not considered a cryptographic signature.

I could be wrong here, but I believe they should use a combination of SHA256 and PGP for signature verification.

[โ€“] ren@reddthat.com 1 points 19 minutes ago* (last edited 17 minutes ago)

Oh, okay, so maybe I misread the sentence. I thought the implication was they used crc32 as opposed to HTTPS. Not sure why you need an additional layer in addition to https- as long as the certificate chain is setup properly. And again, you're not gaining additional security if you submit the hash (or a gpg key) through the same channel. So if they already use https and just want to check for broken downloads, crc32 is perfectly fine. It's just security theater at that point.