# Cryptography Published articles for Cryptography. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## FIPS 140-3 support in OpenSearch DevFeed: [FIPS 140-3 support in OpenSearch]() Original publisher: [Read original article]() Author: Karsten Schnitter Published: 2026-09-16T19:12:14Z Content type: article Language: en Sources: [OpenSearch]() Topics: [fips 140-3](), [opensearch](), [Cryptography](), [Encryption](), [Security]() Tags: [aws](), [blog](), [compliance](), [cryptography](), [encryption](), [fips](), [fips-140-3](), [opensearch](), [security](), [technical]() ### AI overview This post explains OpenSearch support for a FIPS 140-3-compliant mode starting with version 3.6. It describes the validated cryptographic modules used for security-relevant operations, the collaboration involving SAP, SAS, and AWS, and how native FIPS mode differs from using a FIPS-validated TLS-terminating proxy. ### Source excerpt OpenSearch now supports running in a mode compliant with FIPS 140-3, contributed through a multi-year collaboration between SAP, SAS, and AWS. The post FIPS 140-3 support in OpenSearch appeared first on OpenSearch. ## Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27 DevFeed: [Java 27 Delivers Post-Quantum Cryptography, Future Language Innovation, Helidon 27, JavaFX 27]() Original publisher: [Read original article]() Author: Michael Redlich Published: 2026-09-16T10:00:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Java](), [java-27](), [Post-quantum cryptography](), [Cryptography](), [Security](), [Programming](), [releases]() Tags: [application-security](), [architecture-design](), [cryptography](), [development](), [digital-signature](), [helidon](), [java](), [java-27](), [java27-released](), [javafx](), [jdk-27](), [jdk-28](), [lattice](), [module](), [news](), [oracle](), [portfolio](), [post-quantum-cryptography](), [preview](), [project-valhalla](), [quantum-computing](), [release](), [security](), [structured-concurrency](), [vector]() ### AI overview Oracle released Java 27, the second non-LTS release since JDK 25. Its final feature set contains nine JEPs, including post-quantum hybrid key exchange for TLS 1.3, structured concurrency, compact object headers, JFR data redaction, the Vector API, and PEM encodings for cryptographic objects. Five features remain in preview or incubator stages. ### Source excerpt Oracle has released version 27 of the Java programming language and virtual machine. As the second non-LTS release since JDK 25, the final feature set includes nine JEPs, five of which are still progressing through the preview and incubator stages. This release focuses on strengthening security, future language innovation, and projects under the auspices of the Java Verified Portfolio. By Michael Redlich ## JDK 27 Is Generally Available with Nine JEP-Backed Enhancements DevFeed: [JDK 27 Is Generally Available with Nine JEP-Backed Enhancements]() Original publisher: [Read original article]() Author: On September Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Inside Java]() Topics: [JDK 27](), [Java](), [Security](), [Cryptography](), [Quantum Computing]() Tags: [announce](), [cryptography](), [improvements](), [java](), [jdk](), [jdk-27](), [oracle](), [quantum](), [security]() ### AI overview Oracle announces the general availability of JDK 27, which includes nine enhancements covered by JDK Enhancement Proposals, including preview and incubator features across the Java language, security, performance, runtime, and libraries. ### Source excerpt JDK 27 is now available! Oracle is proud to announce the general availability of JDK 27 for developers, enterprises, and end-users. ## 1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it DevFeed: [1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it]() Original publisher: [Read original article]() Author: Bas Westerbaan Published: 2026-09-10T13:00:00Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Cryptography]() Tags: [1-1-1-1](), [algorithms](), [cryptography](), [dns](), [dnssec](), [post-quantum](), [research](), [security](), [testing](), [tls](), [validation]() ### AI overview Cloudflare's 1.1.1.1 now validates DNSSEC signatures using the post-quantum ML-DSA-44 algorithm. The article discusses testing oversized DNS responses and preventing downgrade to conventional signatures while retaining compatibility with older resolvers. ### Source excerpt 1.1.1.1 now validates DNSSEC signatures using NIST's post-quantum ML-DSA-44 algorithm. Here is how we manage 2,420-byte signatures and downgrade risks at scale. ## A decade of Rustls DevFeed: [A decade of Rustls]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-09T18:11:54Z Content type: news Language: en Sources: [LWN.net]() Topics: [releases](), [Cryptography](), [Security, Privacy and Abuse Prevention]() Tags: [api](), [blog](), [compression](), [cryptography](), [performance](), [post-quantum](), [releases](), [tls]() ### AI overview A retrospective on ten years of the Rustls TLS-library project, covering its release history, the forthcoming 0.24 and eventual 1.0 releases, and features added in the stable 0.23 line. ### Source excerpt Joe Birr-Pixton has written a blog post reflecting on a decade of the Rustls TLS-library project and looking ahead to the upcoming 0.24 release and an eventual 1.0 release. Rustls began with a first commit on May 2, 2016. Progress was quick: a month later, on June 5, it could interoperate with most sites on the web. The first release, 0.1.0, followed on August 27, 2016 - less than four months after the first commit. [...] From the 0.1.0 release, the project moved through a long series of releases over the following eight years, building out functionality, hardening and refining the API. That sequence of release lines culminated in 0.23, released on February 29, 2024. The 0.23 release line has been a stable one: in the time since, it has seen 43 non-breaking releases. That stability didn't come with stagnation. The 0.23 line delivered a wide range of important features, including a FIPS-certified cryptography option, certificate compression, Encrypted ClientHello, post-quantum cryptography, and performance improvements. ## FIPS 140-2 vs FIPS 140-3, Explained DevFeed: [FIPS 140-2 vs FIPS 140-3, Explained]() Original publisher: [Read original article]() Author: info@goteleport.com (Mayur Pipaliya) Published: 2026-09-09T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [fips 140-3](), [FIPS validation](), [Cryptography](), [Encryption](), [certificates](), [Security](), [Cloud]() Tags: [certificates](), [cloud](), [cmvp](), [cryptography](), [encryption](), [fedramp](), [fips](), [fips-140-3](), [fips-validation](), [security](), [sensitive-data]() ### AI overview This article explains the differences between FIPS 140-2 and FIPS 140-3, including the standards' origins, CMVP validation certificates, applicable requirements for protecting sensitive data, and the transition timeline through September 2026. ### Source excerpt Understand key changes from FIPS 140-2 to FIPS 140-3. ## Java Weekly, Issue 662 DevFeed: [Java Weekly, Issue 662]() Original publisher: [Read original article]() Author: baeldung Published: 2026-09-06T09:25:19Z Content type: article Language: en Sources: [Baeldung]() Topics: [IntelliJ IDEA](), [Concurrency](), [Tooling](), [Cryptography](), [elasticsearch]() Tags: [concurrency](), [cryptography](), [elasticsearch](), [intellij-idea](), [java](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [tooling](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview A Java ecosystem roundup led by a hands-on look at Project Loom in IntelliJ IDEA, covering virtual threads, scoped values, structured concurrency, and related tooling. It also links to Java and Spring articles, podcasts, release announcements, code-review commentary, and IntelliJ IDEA Conf 2026. ### Source excerpt The three Loom pillars and, more importantly, the tooling. Plus IntelliJ IDEA Conf 2026 getting close. The post Java Weekly, Issue 662 first appeared on Baeldung. ## Updates on HEIR, the homomorphic encryption compiler project DevFeed: [Updates on HEIR, the homomorphic encryption compiler project]() Original publisher: [Read original article]() Published: 2026-09-04T18:53:40Z Content type: article Language: en Sources: [Jeremy Kun]() Topics: [homomorphic encryption](), [Compiler](), [Encryption](), [Cryptography](), [Machine learning](), [Inference](), [GitHub](), [bazel](), [Kaggle]() Tags: [bazel](), [ckks](), [compiler](), [cryptography](), [encryption](), [github](), [homomorphic-encryption](), [inference](), [kaggle](), [mathematics](), [ml](), [programming]() ### AI overview This companion article explains HEIR, a homomorphic encryption compiler that converts programs to operate directly on encrypted data. It discusses compiling pre-trained machine-learning models for private inference, describes the repository and setup, and reports an example involving encrypted credit-card fraud detection. ### Source excerpt On 2026-08-14 I published an article on the Google Security blog with an update on HEIR, our homomorphic encryption (HE) compiler. This is a companion article, in which I have no limits on word count or jargon, and I can feel free to be honest. So strap in. Assuming you won't read the linked corporate blog post, HEIR is a compiler that converts an input program to a program that operates directly on encrypted data. ## OSPAR 2026 report now available with 167 services in scope DevFeed: [OSPAR 2026 report now available with 167 services in scope]() Original publisher: [Read original article]() Author: James Chang Published: 2026-09-04T18:13:04Z Content type: news Language: en Sources: [AWS Security Blog]() Topics: [Security, Privacy and Abuse Prevention](), [Cryptography]() Tags: [amazon-web-services-aws](), [announcements](), [compliance](), [cryptography](), [financial-services](), [foundational-100](), [security](), [security-blog](), [security-identity-compliance]() ### AI overview AWS completed its annual OSPAR assessment under the OSPAR 2.0 framework. The certification covers 167 AWS services in the Asia Pacific (Singapore) Region and is intended to support customer compliance due diligence. ### Source excerpt We're pleased to confirm the successful completion of our annual Amazon Web Services (AWS) Outsourced Service Provider's Audit Report (OSPAR) assessment on July 29, 2026, in line with the OSPAR version 2.0 framework. The Association of Banks in Singapore (ABS) established the Guidelines on Control Objectives and Procedures for Outsourced Service Providers (ABS Guidelines) to [...] ## Crypto Agility: Why PQC Is Not a One-Time Upgrade DevFeed: [Crypto Agility: Why PQC Is Not a One-Time Upgrade]() Original publisher: [Read original article]() Author: Hugo Vliegen Published: 2026-09-03T15:00:56Z Content type: article Language: en Sources: [Security @ Cisco Blogs]() Topics: [Cryptography](), [networking](), [Network design](), [Vulnerabilities]() Tags: [cisco-sd-wan](), [cryptographic](), [cryptography](), [infrastructure](), [network-security](), [networks](), [post-quantum](), [quantum-computing](), [sd-wan-security](), [security](), [security-for-ai]() ### AI overview The article explains why crypto agility is essential for long-lived network infrastructure adopting post-quantum cryptography. It argues that organizations should design systems to update cryptography continuously as standards, threats, and implementations evolve. ### Source excerpt Learn why crypto agility is essential for PQC-ready networks--and how adaptable infrastructure helps organizations keep pace with evolving threats. ## Sites using PQC (September 2026) DevFeed: [Sites using PQC (September 2026)]() Original publisher: [Read original article]() Published: 2026-09-01T14:49:46Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [Post-quantum cryptography](), [Post-Quantum](), [TLS (Transport Layer Security)](), [Cryptography]() Tags: [2026](), [cryptography](), [post](), [post-quantum](), [post-quantum-cryptography](), [quantum](), [september-2026](), [sites](), [tls](), [top](), [using]() ### AI overview A periodic check examines which of the top 1 million domains support post-quantum cryptography in their TLS key exchange. ### Source excerpt One more periodic check of which of the top 1M domains support post-quantum cryptography in their TLS key exchange. ## Announcing Chainguard container images for Go 1.27 DevFeed: [Announcing Chainguard container images for Go 1.27]() Original publisher: [Read original article]() Published: 2026-08-31T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [container images](), [Go Language](), [Cryptography](), [Deployment](), [Security, Privacy and Abuse Prevention](), [Post-Quantum]() Tags: [chainguard](), [container](), [container-images](), [cryptography](), [deployment](), [fedramp](), [fedramp-ato](), [fips](), [go](), [hardening](), [images](), [post-quantum](), [release]() ### AI overview Chainguard announces three Go 1.27 container images: go, go-fips, and go-openssl-fips. The options differ in their FIPS-validated cryptography, including whether cryptography is built in or selected at deployment time. ### Source excerpt Chainguard simplifies Go 1.27 with three images and a new option to choose FIPS-validated cryptography at deployment without recompiling. ## Why a cryptographic inventory is key for addressing the quantum computing threat DevFeed: [Why a cryptographic inventory is key for addressing the quantum computing threat]() Original publisher: [Read original article]() Author: Christopher Day Published: 2026-08-28T14:01:00Z Content type: article Language: en Sources: [Tenable Blog]() Topics: [Cryptography](), [Security, Privacy and Abuse Prevention](), [migration](), [Security Attacks]() Tags: [algorithms](), [attacks](), [cryptographic](), [cryptography](), [encryption](), [migration](), [post-quantum](), [quantum](), [quantum-computing](), [security]() ### AI overview The article explains how a cryptographic inventory and phased migration to quantum-resistant cryptography can address the risk that future quantum computers pose to public-key algorithms. It highlights harvest-now, decrypt-later attacks, the vulnerability of RSA, ECC, and Diffie-Hellman to Shor's Algorithm, and the expected resilience of AES-256. ### Source excerpt When quantum computers become generally available, they'll be able to crack current public-key cryptographic algorithms, putting digitally stored and transmitted data at risk. But the threat already exists, as attackers use the "harvest now, decrypt later" tactic. Discover why building a comprehensive cryptographic inventory and executing a phased operational strategy are critical for protecting your data against quantum computing attacks. Key takeaways Quantum computing risks are an operational threat today due to "harvest now, decrypt later" (HNDL) tactics, in which adversaries actively harvest and store encrypted data to decrypt it retroactively once quantum capabilities mature. When run on a quantum computer that's powerful enough, Shor's Algorithm will break foundational asymmetric infrastructure like the RSA, ECC, and Diffie-Hellman algorithms, although symmetric encryption standards like AES-256 are expected to remain secure against quantum attacks. Globally, more regulatory bodies are starting to mandate a comprehensive cryptographic inventory, making absolute visibility across the digital environment a prerequisite for an orderly post-quantum migration. Transitioning to quantum-resistant cryptography requires a phased operational strategy spanning discovery, prioritization, remediation, and verification. The quantum threat to modern security architecture Future quantum computers will represent a threat to the foundational security architecture that protects digital data. For decades, the global economy, national security apparatus, and critical infrastructure have relied on asymmetric cryptography, specifically RSA and elliptic curve cryptography (ECC), to secure data in transit, authenticate identities, and protect digital signatures. The mathematical difficulty of factoring large integers or solving discrete logarithm problems has long provided a robust shield against cyber attacks launched using conventional computing capabilities. However, the rapid mat ## How WhatsApp Implemented Passkey Authentication for Faster, Phishing-Resistant Sign-In DevFeed: [How WhatsApp Implemented Passkey Authentication for Faster, Phishing-Resistant Sign-In]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-27T17:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [Passkeys](), [Authentication](), [Security, Privacy and Abuse Prevention](), [Cryptography](), [Android]() Tags: [api](), [authentication](), [credential-theft](), [cryptography](), [developer](), [google](), [meta](), [sign-in](), [whatsapp]() ### AI overview The article describes how WhatsApp implemented passkey-based authentication to provide faster sign-ins and reduce phishing and credential-theft risks. It explains the use of public-private key cryptography, biometric or screen-lock authentication, and Android's Credential Manager API. ### Source excerpt Posted by Niharika Arora, Senior Developer Relations Engineer, Tracy Agyemang, Product Marketing Manager, Google and Mayank Manuja, Android Engineer, Meta WhatsApp is the world's largest messaging platform, serving billions of users globally. It is the default communication tool for people across diverse regions, connecting users through private, reliable, and secure messaging. "What excites me most is the sheer scale of WhatsApp's impact. Even a small improvement to WhatsApp touches billions of users worldwide," says Mayank Manuja, an Android Engineer on the WhatsApp Registration and Access team who led the design and implementation of passkey-based authentication for WhatsApp. Building for an audience of this magnitude requires navigating a vast range of network conditions, device capabilities, and levels of digital literacy. Recognizing the potential early, WhatsApp committed to adopting passkeys in 2023, becoming one of the first major consumer apps to integrate the technology. By implementing passkeys, WhatsApp aimed to provide a fast, phishing-resistant option that significantly reduces user friction while providing robust protection against account takeovers and credential theft. A user creating a passkey on WhatsApp for faster, more secure sign-ins. The Decision to Adopt Passkeys For WhatsApp, offering multiple access methods is key to making it easier for users to stay connected and regain access when needed. Passkeys offer users a streamlined, one-tap login experience that eliminates phishing risks and functions reliably even in regions where OTP message delivery can be inconsistent. Underneath, passkeys leverage public-private key cryptography to replace manual entry with biometric or screen lock authentication. This workflow drastically improves sign-in speeds by reducing the process to a single tap via a unified, bottom-sheet interface that keeps users engaged within the app's context. The benefits are twofold: passkeys offer users a streamlined login e ## How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys DevFeed: [How WhatsApp Upgraded to Secure, Seamless Sign-In for 1 Billion Users with Passkeys]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-27T17:00:00Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Passkeys](), [Authentication](), [Security, Privacy and Abuse Prevention](), [Cryptography](), [Android](), [App](), [API]() Tags: [android](), [api](), [app](), [authentication](), [credential-theft](), [cryptography](), [phishing](), [scale](), [whatsapp]() ### AI overview WhatsApp's adoption of passkeys provides a fast, phishing-resistant sign-in method for its large global user base. The article explains how passkeys use public-private key cryptography with biometric or screen-lock authentication, reduce reliance on inconsistent SMS OTP delivery, and simplify implementation through Android's Credential Manager API. ### Source excerpt Posted by Niharika Arora, Senior Developer Relations Engineer, Tracy Agyemang, Product Marketing Manager, Google and Mayank Manuja, Android Engineer, Meta WhatsApp is the world's largest messaging platform, serving billions of users globally. It is the default communication tool for people across diverse regions, connecting users through private, reliable, and secure messaging. "What excites me most is the sheer scale of WhatsApp's impact. Even a small improvement to WhatsApp touches billions of users worldwide," says Mayank Manuja, an Android Engineer on the WhatsApp Registration and Access team who led the design and implementation of passkey-based authentication for WhatsApp. Building for an audience of this magnitude requires navigating a vast range of network conditions, device capabilities, and levels of digital literacy. Recognizing the potential early, WhatsApp committed to adopting passkeys in 2023, becoming one of the first major consumer apps to integrate the technology. By implementing passkeys, WhatsApp aimed to provide a fast, phishing-resistant option that significantly reduces user friction while providing robust protection against account takeovers and credential theft. A user creating a passkey on WhatsApp for faster, more secure sign-ins. The Decision to Adopt Passkeys For WhatsApp, offering multiple access methods is key to making it easier for users to stay connected and regain access when needed. Passkeys offer users a streamlined, one-tap login experience that eliminates phishing risks and functions reliably even in regions where OTP message delivery can be inconsistent. Underneath, passkeys leverage public-private key cryptography to replace manual entry with biometric or screen lock authentication. This workflow drastically improves sign-in speeds by reducing the process to a single tap via a unified, bottom-sheet interface that keeps users engaged within the app's context. The benefits are twofold: passkeys offer users a streamlined login e ## Java Weekly, Issue 661 DevFeed: [Java Weekly, Issue 661]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-26T17:15:42Z Content type: article Language: en Sources: [Baeldung]() Topics: [IntelliJ IDEA](), [Spring Boot 4](), [Orchestration](), [Quarkus](), [elasticsearch](), [JSON](), [Compiler](), [Scripting](), [GUI](), [Cryptography](), [Security]() Tags: [boot](), [cryptography](), [gui](), [intellij](), [intellij-idea](), [java](), [json](), [metrics](), [netflix](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [orchestration](), [post](), [release](), [scripting](), [security](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 661 is a roundup covering IntelliJ IDEA Conf, the JDK 27 release candidate, early JDK 28 developments, Spring and Java updates, technical articles, webinars, and recent framework and library releases. It also highlights Netflix Conductor's evolution as a workflow orchestration engine. ### Source excerpt IntelliJ IDEA Conf is back, JDK 27 got its first RC and JDK 28 is already looking solid The post Java Weekly, Issue 661 first appeared on Baeldung. ## Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java DevFeed: [Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java]() Original publisher: [Read original article]() Author: Poonam Parhar Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [Inside Java]() Topics: [Cryptography](), [fips 140-3](), [openssl](), [Java](), [Encryption](), [Security, Privacy and Abuse Prevention]() Tags: [cryptographic](), [cryptography](), [fips](), [fips-140-3](), [java](), [openssl](), [oracle](), [security](), [standard]() ### AI overview Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module and exposes cryptographic services through Java Cryptography Architecture (JCA). ### Source excerpt Oracle Jipher 10 packages a FIPS 140-3 validated OpenSSL cryptographic module, making cryptographic services available through the standard Java Cryptography Architecture (JCA) framework. ## How Trail of Bits helps verify the integrity of your Signal chats DevFeed: [How Trail of Bits helps verify the integrity of your Signal chats]() Original publisher: [Read original article]() Author: "Tjaden Hess" Published: 2026-08-11T17:30:00Z Content type: article Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [client](), [servers](), [Cloudflare](), [App]() Tags: [audits](), [cloudflare](), [cryptography](), [devices](), [external](), [open-source](), [safety](), [server](), [signing](), [verification]() ### AI overview The article explains how Trail of Bits helps verify the integrity of Signal chats through Automatic Key Verification. The system uses external auditors, globally consistent public-key maps, Merkle trees, and signed tree heads to make mismatches harder to conceal. Signal clients currently require signatures from auditors operated by Signal, Cloudflare, and Trail of Bits. ### Source excerpt Every Signal chat starts the same way: the client asks the Signal server for the public key associated with your contact's phone number. But how do you know the server gave you the right key? A compromised server could provide a false public key, allowing the client to encrypt messages to an attacker rather than the intended recipient. Until now, the only way to detect such malfeasance was to verify safety numbers with your contact in person or over a trusted channel. Signal recently launched an alternative: Automatic Key Verification, a feature that helps validate that your chats are secure without requiring direct safety number comparison. Trail of Bits built and operates one of the three auditors that make this system trustworthy. Our auditor, which is an independent implementation written from scratch, continuously checks that the Automatic Key Verification system behaves honestly. How key verification works Automatic Key Verification is a form of "key transparency" that makes mismatch attacks harder to hide by creating a globally consistent view of the set of public keys associated with each phone number. The Signal app now performs a periodic self-check to ensure that all keys stored in the global map for your account belong to your devices. If the app is unable to verify the log, or finds that not all keys are expected, the user is presented with a warning that "Automatic Key Verification is currently unavailable for your device." Automatic Key Verification may also be unavailable for other reasons, as outlined in Signal's documentation. What our auditor does Automatic Key Verification depends on external auditors. Trail of Bits helps this system function by providing external verification that the user ↔ public key map is globally consistent and well formed, and does not hide any entries. Each time a new entry is added, we update our local copy of the map, stored as a Merkle tree. Periodically, we sign the head of the tree using a signing key that only we kn ## Introducing Automatic Key Verification DevFeed: [Introducing Automatic Key Verification]() Original publisher: [Read original article]() Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Signal Blog]() Topics: [Cryptography]() Tags: [communication](), [cryptography](), [encryption](), [feature](), [safety]() ### AI overview Signal introduces automatic key verification, a key-transparency-based feature that independently verifies the consistency of a contact's public encryption key alongside existing safety numbers. ### Source excerpt Signal now offers a feature called "automatic key verification" which complements the existing safety number system. Signal is always end-to-end encrypted, and automatic key verification provides an additional, streamlined way to confirm that there's no unexpected party between you and the other "end" of an end-to-end encrypted session. Read more... ## How Two Small Bugs Led to a Critical Vulnerability and a Cryptography Audit of Go's SSH Library DevFeed: [How Two Small Bugs Led to a Critical Vulnerability and a Cryptography Audit of Go's SSH Library]() Original publisher: [Read original article]() Author: info@goteleport.com (Rob Picard) Published: 2026-08-10T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [cryptographic audit](), [Go Language](), [ssh](), [Security](), [vulnerability]() Tags: [analysis](), [audit](), [bugs](), [cryptographic-audit](), [cryptography](), [go](), [security](), [security-engineering](), [ssh](), [vulnerability]() ### AI overview Teleport describes a critical vulnerability caused by two interacting bugs in its SSH certificate validation logic and reports that NCC Group conducted a cryptographic audit of Go's SSH package. The audit resulted in nine CVEs and identified subtle issues requiring expert review. ### Source excerpt Learn about NCC Group's cryptographic audit of Go's SSH package. ## Why We Wrote a New JWT Library for Kotlin Multiplatform DevFeed: [Why We Wrote a New JWT Library for Kotlin Multiplatform]() Original publisher: [Read original article]() Published: 2026-08-07T00:00:00Z Content type: article Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [JSON Web Tokens](), [Kotlin Multiplatform](), [Cryptography](), [Authentication](), [Authorization](), [Open Source](), [Library]() Tags: [authentication](), [authorization](), [community](), [cryptography](), [jwt](), [kmp](), [kotlin](), [kotlin-multiplatform](), [libraries](), [library](), [open-source]() ### AI overview The author explains how a security-focused Kotlin Multiplatform banking project led to research into cryptography and JWTs. After finding that JJWT was limited for cross-platform projects, they began developing a new JWT library as a personal open-source learning project. ### Source excerpt Earlier this year, we silently started working on and published a new KMP library. The reason it exists serves as a good lesson on how to start contributing to the open-source community. ## A few notes on AWS Nitro Enclaves: KMS integration DevFeed: [A few notes on AWS Nitro Enclaves: KMS integration]() Original publisher: [Read original article]() Author: "Paweł Płatek" Published: 2026-08-05T11:00:00Z Content type: article Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [Cryptography](), [AWS IAM]() Tags: [application-security](), [aws](), [cryptographic](), [cryptography](), [encryption](), [iam](), [integration](), [policy](), [trusted-execution-environment]() ### AI overview The article examines security and operational risks in integrating AWS Nitro Enclaves with KMS, including attestation, key policies, and encrypted key handling. ### Source excerpt Nitro Enclaves and Key Management Service (KMS) feel like a natural fit: since the KMS can verify attestation documents generated by the enclaves, developers can offload key management tasks from their applications to the AWS-managed service. But integrating an external service with your trusted enclaves comes with new threats, even if that service comes from the same provider. In this blog post--the third in our series on Nitro Enclaves, following our posts on attack surface and images and attestation--we catalog passive and active attack classes against the enclave-KMS communication channel, and cover the operational risks that persist even when the cryptography is correct. Intro to KMS The KMS is an AWS service that provides a unified public API for creating and managing keys backed by HSMs to the broader AWS ecosystem. There are three main key types supported by KMS that devs need to care about: Customer-managed keys (CMK) Data keys (DK, symmetric) Data key pairs (asymmetric) CMKs never leave KMS. You request KMS to perform cryptographic operations (like encryption or signing) for you. Data keys and key pairs are generated in KMS, are not stored in KMS, and are intended for programmatic uses. For symmetric keys, the KMS gives you a plaintext key and the same key encrypted to CMK. Your application performs encryptions, removes the plaintext key, and stores the key encrypted to a CMK along the ciphertexts; this pattern is called envelope encryption. For asymmetric keys, the KMS gives you a plaintext key pair and the private key encrypted to CMK. Your application creates signatures or encrypts data, deletes the private key, and keeps the public key and encrypted private key (along with signatures/ciphertexts). Both types of data keys can be used with Decrypt operation to get plaintext keys again. S t o r a g e s t { o E r _ e d ( k E , _ C d } k , C ) E n c l a v G e e { n d e k C D p r , = e l a E e c a t _ n r i e d c y n D k ( p t a = d t e t e k ( { x a n , c d t ## Ten advances in mathematics and theoretical computer science DevFeed: [Ten advances in mathematics and theoretical computer science]() Original publisher: [Read original article]() Published: 2026-08-01T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [AI Chat](), [Cryptography]() Tags: [ai](), [chatgpt](), [complexity](), [cost](), [cryptography](), [model](), [openai](), [publication](), [quantum](), [research](), [science]() ### AI overview OpenAI presents ten AI-assisted results on long-standing problems in mathematics and theoretical computer science. An internal Astra model produced solutions that humans prepared into manuscripts and that were formalized in Lean certificates. ### Source excerpt OpenAI shares new results on long-standing open problems in mathematics and theoretical computer science, including advances in geometry, cryptography, and complexity. ## Qodana 2026.2: More Security, Better Coverage, Less Configuration DevFeed: [Qodana 2026.2: More Security, Better Coverage, Less Configuration]() Original publisher: [Read original article]() Author: Kerry Beetge Published: 2026-07-29T13:47:03Z Content type: release Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [Security, Privacy and Abuse Prevention](), [Pull Request](), [configuration](), [Cryptography](), [PHP](), [.NET](), [Go Language]() Tags: [2026-2](), [code-quality](), [compliance](), [cryptography](), [ide](), [laravel](), [pull-request](), [release](), [security]() ### AI overview Qodana 2026.2 adds pull-request coverage insights, automatic coverage-report detection, and expanded security and compliance checks. ### Source excerpt Qodana 2026.2 makes it easier for development teams to act on code quality, security, and compliance findings throughout the development workflow. This release introduces clearer code coverage insights for pull requests, highlights uncovered new lines directly in the IDE, and automatically detects coverage reports in common project locations - reducing the configuration required to get [...] [Next page]()