lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

53
active users

#postquantum

0 posts0 participants0 posts today

⚛️ Q-Day isn’t sci-fi—it’s the day a quantum computer can break the cryptography that underpins all email, banking, military comms, and cryptocurrencies. Experts put the odds at 1-in-3 before 2035, with a nonzero chance it’s already happened in secret. The threat is twofold: “harvest now, decrypt later” espionage, and real-time authentication attacks that could shut down grids or hijack markets. Post-quantum encryption standards exist, but upgrading the world’s infrastructure—from hospitals to satellites—is a decades-long process. Like Y2K, the best-case outcome is a collective scramble that makes Q-Day anticlimactic. The worst case? The end of digital trust as we know it. 😱

TL;DR
🕒 1-in-3 chance by 2035
🔓 Risk to all modern encryption
💰 Bitcoin could go to zero
⚠️ Global infrastructure at risk

wired.com/story/q-day-apocalyp
#QuantumComputing #Cybersecurity #Encryption #PostQuantum #security #privacy #cloud #infosec

WIRED · The Quantum Apocalypse Is Coming. Be Very AfraidBy Amit Katwala

Monday news from ITSPmagazine 🙂 #happymonday!

Join Marc Manzano, Sean Martin, CISSP and me on this week SandboxAQ Webinar!

After an incredible conversation with Marc on the #RSAC floor in San Francisco — where Sean and I used every second of our time and still had more to explore — I knew the #Sandbox Story couldn’t stop there.

If you missed that on-location episode from #RSAC2025, catch it here:

👉 Security at the Edge of Change – A Brand Story with Marc Manzano from SandboxAQ

itspmagazine.com/their-stories

Now, we’re keeping the momentum going with a live ITSPmagazine webinar you don’t want to miss — and I won’t either. 🤘😬

🔐 How To Detect And Mitigate Non-Human Identity And Cryptographic Vulnerabilities | An ITSPmagazine Webinar with SandboxAQ

Join Marc, Sean, and me as we dig deeper into how SandboxAQ is tackling one of today’s most urgent security challenges.

Unmanaged cryptographic assets and non-human identities have left security teams blind to critical risks. These gaps have fueled vulnerabilities, breaches, compliance challenges, and operational drag across enterprise environments.

By attending, you’ll:

🔸 Gain visibility into cryptographic assets and non-human identities like API keys, certificates, and service accounts

🔸 See how #AQtiveGuard enables automated discovery, threat detection, and root cause analysis without disrupting workflows

🔸 Learn how to future-proof your security with Post-Quantum Cryptography readiness and AI-powered #SecOps

📌 Learn more:

👉 itspmagazine.com/itspmagazine-

📅 REGISTER NOW:

Can’t attend the live webinar? All registrants get exclusive access with a link to rewatch the recording.

👉 crowdcast.io/c/how-to-detect-a

Share the news and join us!

See you live on Thursday!

#infosec

#cybersecurity

#technology

#tech

#infosecurity

#AIsecurity

#postquantum

#cryptography

#identitymanagement

Daniel J. Bernstein (#djb, to those who know and love him [1]) has a new blog entry about the NIST post-quantum #cryptography standardization process that's been ongoing for some years. Also, follow him @djb .

If you're not aware of some of the controversy about how NIST is running this process, it's a must-read.

blog.cr.yp.to/20250423-mceliec

My $0.02: it sure looks like NIST is backstopping an attempt by the NSA to get everyone to standardize on cryptography #standards that the #NSA knows how to break.

Again.

Yes, they did it before. If you read up on the Dual_EC calamity and its fallout, and how this time it was supposed to be different - open, transparent, secure - then prepare to be disappointed. NIST is playing #Calvinball with their rules for this contest, yanking the rug out from under contenders that appear to be more #secure and better understood, while pushing alternatives that are objectively worse (#weaker encryption, less studied, poorer #performance).

Frankly, I think organizations outside of the #USA would be foolish to trust anything that comes out of #NIST's current work. Well, those inside the USA too, but some of those may be forced by law to use whatever NIST certifies.

[1] Some people think djb is "prickly", not lovable. Oddly, it seems that the only people who say this are those who are wildly incorrect about code/algorithms and are being gently but publicly corrected about by djb at the time

blog.cr.yp.tocr.yp.to: 2025.04.23: McEliece standardization

Post-quantum cryptography posts.

13.08.2024: NIST releases first three finalized PQC encryption standards.
Source: nist.gov/news-events/news/2024

12.09.2024: GnuPG announces release of 2.5.1 for public testing, finalized PQC algorithms are supported.
Source: lists.gnupg.org/pipermail/gnup

PQC: en.wikipedia.org/wiki/Post-qua
GnuPG: mastodon.online/@blueghost/111
Harvest now, decrypt later: mastodon.online/@blueghost/111

Those of you with long memories may recall the hassle of adopting TLS 1.0 when it dropped, and then TLS 1.1, and then TLS 1.2 (and the mad scramble to update cipher suites post-Heartbleed, etc.).

We’re going to see that process all over again with adoption of FIPS 203, 204, and 205 over the next few years (the new NIST quantum crypto standards). I have to wonder if we collectively learned anything from the multiple previous rounds of crypto updates in infrastructures, or if our process is as broken as it ever was. (Rhetorical question here.)

Don’t just think about how to navigate the current moment; think about how to improve your process so that it’s less painful, and less expensive, to do the right thing the next time this comes along. It’s kind of like what Colin Chapman (founder of Lotus) used to say: “Adding speed makes you faster in the straights; adding lightness makes you faster everywhere.” Fixing your process will make it better now and in the future - don’t just address the current need with a quick and dirty tactical fix or a big manual effort; spend a little more time now and reap the benefits forever after.

This will not be the last time we need to do this. #PQC #postquantum

So Amazon has rolled out support for post-quantum ciphers across services over a period of several years now (notably KMS, then ACM and Secrets Manager #TLS endpoints) ... but I can't find *anything* about when post-quantum cipher support will roll out for #CloudFront. ApostquantumT makes its formal announcement of standards in this space next month, that's suddenly going to be part of the requirements section of many customers' RFPs and service provider checklists. Cloudflare has had support enabled for quite a while now, and I know #AWS can do this because it's been on for KMS public endpoints for years ... so what's the delay with CloudFront? #postquantum

lots of #postquantum stuff in my world today - discovered the Open Quantum Safe project on Github (produces liboqs, which you can enable on the latest Chrome and Edge - although Edge has issues currently? - and soon on Firefox as well) github.com/open-quantum-safe

Quite a bit more from this great round-up post from @jschauma a couple months ago (sorry I missed it!) netmeister.org/blog/pqc-2024-0

Also! Great new tool from a friend of mine at work, which you can use to test the current post-quantum crypto supportof your browser, an arbitrary app, or a site on the Web: isitquantumsafe.info/ - feedback welcome

GitHubOpen Quantum SafeSoftware for prototyping quantum-resistant cryptography - Open Quantum Safe