• 0 Posts
  • 33 Comments
Joined 10 months ago
cake
Cake day: June 11th, 2025

help-circle


  • Continuing from OP’s snippet:

    Leonie Mueck, formerly the chief product officer of Riverlane, a Cambridge-based quantum startup, said Google’s statement did not necessarily suggest there would definitely be a working quantum computer capable of breaking encryption by 2029.

    In fact, most timelines for a cryptographically relevant quantum computer – that is, one powerful enough to break encryption – range from the 2030s to the 2050s. But Mueck said the prospect was close enough that governments were already preparing for the eventuality that data stored to today’s encryption standards would be exposed when the technology sufficiently advances.

    “We’re basically seeing in the intelligence community already that for probably more than a decade they’ve been thinking about this threat,” Mueck said.

    Last year the UK’s cybersecurity agency, the National Cyber Security Centre, urged organisations to guard their systems against quantum hackers by 2035.

    Google’s timeline suggests engineering teams across the technology industry should consider measures to protect sensitive data by migrating to more advanced encryption systems now. Certain kinds of attacks predicated on the future availability of quantum decryption – “store now, decrypt later” – may currently be being deployed across the field.






  • I did say most, not all. Some of the info on that page may be outdated, but obviously it would just be limited to those that require regular comprehensive inspections in the first place.

    I was able to easily look up the inspection guidelines from my states DMV page and confirm for myself that TPMS light is not a fail here so YMMV, but my point was essentially that it’s more likely than not that bad sensors won’t fail someone, not that nobody will get failed.




  • Grostleton@lemmy.dbzer0.comtoTechnology@lemmy.worldmonitor update
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    4 months ago

    Just make sure you have the firmware for your specific monitor’s region. I had a different Samsung monitor with a few regional variants that were only indicated by an extra letter on the model # on the back label. I didn’t think it would matter until I flashed firmware from a different region and bricked my panel…

    Granted, I had to rename the firmware file to have a matching region letter to get the monitor to identify it, and the warranty covered my mistake without having to make a fuss, but it was a long couple weeks basking in my own stupidity.

    Just don’t do what I did and you’ll be fine, I’ve flashed monitor firmware properly many times before without issue. Just don’t futz with the file or power off the device mid-flash and you’re golden 😉