CIRCLE WITH A DOT

Useful tool for scanning and CBOM generation I ran across this morning; feature set is great, capabilities are great, integrations are great, I love command line tooling and it's from a non-profit. https://github.com/csnp/cryptoscan #PQC #cryptography

@bsi Diese „hochsicherheits-Chips“, waren das nicht die, die Infineon in die Yubikey gebaut hat, aus denen man dann den private Key rausrutschende konnte?Rhetorische Frage. Ja, genau die waren das

@ghosttie @dacmot I think you need a second communication channel. And something to corroborate that multiple channels are controlled by the same person. The most surefire way is to meet in person and confirm the keys. I don't think there's a purely technical way to solve this without putting trust into some central authority. It's inherently a social problem.

Fun post pointed out by Werner Koch on the GPG "post-quantum defaults" thread:https://www.metzdowd.com/pipermail/cryptography/2026-March/039449.html"""Quantum Cryptography, while intellectually neat, does not present a practical attack that we need protection against at this time. Kleptographic Standards on the other hand are very much a practical attack that we need to protect against at this time.When a standards body tells you that you should cast aside well-studied cryptographic algorithms which have earned their trust through dozens of years of examination, testing, and motivated attackers, for the sake of protection against Quantum Crypto? The attack you should be protecting against isn’t Quantum Crypto."""#cryptography #QuantumCryptography #security

VeraCrypt to stop developing Windows application due to Microsoft revoking their driver signing certificate:https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/Sorry to hear about this turn of events, but it was pretty much to be expected given the way the world is turning, and Microsoft being Microsoft.Switch to Linux if you can, and come give Shufflecake a try #veracrypt #truecrypt #privacy #cryptography #plausibledeniability #shufflecake #microsof #windows #enshittification #surveillance #cypherpunk

VeraCrypt to stop developing Windows application due to Microsoft revoking their driver signing certificate:https://sourceforge.net/p/veracrypt/discussion/general/thread/9620d7a4b3/We are sorry to hear this turn of events and we wish VeraCrypt team all the best. For us, Windows was never an option.#veracrypt #truecrypt #privacy #cryptography #plausibledeniability #shufflecake #microsof #windows #enshittification #surveillance #cypherpunk

The A858 puzzlehttps://negativepid.blog/the-a858-puzzle/#cryptography #internetMysteries #unsolvedCases #coldCases #internetPuxxles #a858puzzle #digitalInvestigations #OSINT #socialEngineering #cyberInvestigations #intelligence #darkWeb #negativepid

@paragon @Girgias excellent, thanks!

OpenSSH 10.3/10.3p1 released! https://undeadly.org/cgi?action=article;sid=20260407084719 #openbsd #openssh #ssh #security #cryptography #networking

I see the generative AI fad with its "hallucinations" & other mishaps as a giant, annoying, slow-rolling bubble (that we might never see completely burst in our lifetimes since companies continue to invest so much in the #tech).Whereas - quantum computing is potentially a serious long-term #cybersecurity threat that could break the internet and is therefore a much bigger deal.#QuantumComputing #cryptography #business #finance #MyThoughts--https://www.forbes.com/sites/digital-assets/2026/03/31/google-finds-quantum-computers-could-break-bitcoin-sooner-than-expected/--https://ig.ft.com/quantum-computing/

New breakthrough results for quantum attack resource estimates against 256-bit elliptic curves: most ECC-based applications including ECDSA and Bitcoin could be at risk way sooner than expected:https://research.google/blog/safeguarding-cryptocurrency-by-disclosing-quantum-vulnerabilities-responsibly/"We estimate that these circuits can be executed on a superconducting qubit CRQC with fewer than 500,000 physical qubits in a few minutes [...] This is an approximately 20-fold reduction in the number of physical qubits required to solve ECDLP-256"I have been saying this since the 2010s: quantum cryptanalysis is one of those non-linear technology progresses that will take everyone by surprise when it arrives. Qubits quality and numbers go up, error-correction and attacks improve, investments scale up accordingly. It's a perfect storm of compound factors. Folks didn't listen, now time is ticking.#quantum #quantumcomputing #cryptography #security #cybersecurity #infosec #google #bitcoin #blockchain #ethereum

Quantum computers threaten to break most modern cryptography within minutes — perhaps seconds. The theoretical threat is becoming practical reality.What stands to be compromised:Financial systems and transactionsGovernment communications and classified informationMedical records and health dataCorporate trade secrets and intellectual propertyPersonal communications and private messagesThe "harvest now, decrypt later" strategy is already in use. State actors are collecting encrypted data today, anticipating future quantum decryption capabilities.NIST's post-quantum cryptography competition has identified promising algorithms across several approaches: lattice-based, code-based, multivariate, and hash-based cryptography. Each presents trade-offs in performance, key size, and implementation complexity.The transition will cost billions globally. The geopolitical stakes are immense: the nation that achieves practical quantum computing first gains unprecedented strategic advantage — the ability to decrypt adversaries' communications, access protected state secrets, and undermine financial systems.This is a quantum arms race. The winner may effectively read the digital world's thoughts.https://newsgroup.site/quantum-computing-cryptography-threat-encryption-2026/#QuantumComputing #Cryptography #PostQuantum #NIST #CyberSecurity #DataPrivacy

Transitioning to Quantum-Safe Cryptography on IBM Z "AbstractAs cyberattacks continue to increase, the cost and reputation impacts of data breaches remain a top concern across all enterprises. Even if sensitive data is encrypted and is of no use now, cybercriminals are harvesting that data because they might gain access to a quantum computer that can break classical cryptographic algorithms sometime in the future. Therefore, organizations must start protecting their sensitive data today by using quantum-safe cryptography.This IBM Redbooks publication reviews some potential threats to classical cryptography by way of quantum computers and how to make best use of today’s quantum-safe capabilities on the IBM Z platform. This book also provides guidance about how to get started on a quantum-safe journey and step-by-step examples for deploying IBM Z quantum-safe capabilities.This publication is intended for IT managers, IT architects, system programmers, security administrators, and anyone who needs to plan for, deploy, and manage quantum-safe cryptography on the IBM Z platform. The reader is expected to have a basic understanding of IBM Z security concepts."#draft #ibm #book #quantum #cryptography #ebook #redbooks #ittech #it #securityhttps://www.redbooks.ibm.com/redpieces/pdfs/sg248525.pdf

Generating cryptographically secure random values in C and C++ – what are your options?After writing about how secure random links work, a few people asked about the underlying libraries. So here is a quick overview. libsodium is the easiest and most recommended choice. One function call, cross-platform, and built specifically for cryptography:randombytes_buf(buffer, size);That is really all there is to it. libsodium picks the best available entropy source on the OS automatically. OpenSSL / LibreSSL is the classic option. RAND_bytes() does the job and is available almost everywhere. Worth using if you already have OpenSSL as a dependency – otherwise libsodium is cleaner.️ If you want no external dependency at all, go directly to the OS:Linux: getrandom() – available since kernel 3.17macOS / BSD: arc4random_buf() – even simpler, no error handling neededBoth are solid choices for system-level code.️ What about std::random_device in C++? It looks convenient but the standard does not guarantee cryptographic security. On some platforms it falls back to a predictable seed. Fine for games or simulations – not for security-critical code.So for anything security-related: libsodium or the OS primitives directly. std::random_device is a trap if you care about real randomness.What do you use in your projects for secure randomness? Still rolling your own or already on libsodium? #CPlusPlus #C #Security #Cryptography #libsodium #Infosec #SystemsProgramming

@newsgroup Thanks — the prototype is already taking shape. The core architectural decision was to treat the Shadowsocks node as a blind relay inside which RINA flows run via Ouroboros user-space IPC, with Ockam handling E2E channel authentication above it. No root, no TUN/TAP, no kernel interfaces.The interesting property that emerges: no single node in the path ever knows simultaneously who is talking, to whom, and what they're saying. That's not achievable with any IP-based stack regardless of encryption.Code going on Gitea this week. Happy to continue the conversation in a less public channel if you want to dig into the specifics — the practical hurdles around OuroboRs FFI bridging are worth a longer discussion.