# digital signature Published articles for digital signature. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## Enable Your SAML Requesting App for Cross App Access DevFeed: [Enable Your SAML Requesting App for Cross App Access]() Original publisher: [Read original article]() Author: Alisa Duncan Published: 2026-07-17T05:00:00Z Content type: tutorial Language: en Sources: [Okta Developer]() Topics: [OAuth 2.0](), [Authorization](), [JSON Web Tokens](), [OpenID connect (OIDC)](), [API](), [AI Agent]() Tags: [api](), [authorization](), [claude](), [cross-app-access](), [digital-signature](), [identity](), [idp](), [implementation](), [jwt](), [oauth](), [oauth-2-0](), [oidc](), [openid-connect](), [payload](), [saml](), [signing](), [sso](), [xaa]() ### AI overview This guide explains how SAML-federated applications can use Cross App Access (XAA) to connect to third-party applications without migrating to OpenID Connect. It covers exchanging a SAML assertion for an OAuth refresh token, an ID-JAG, and an access token, along with token validation and Okta configuration. ### Source excerpt If you currently federate enterprise customers using Security Assertion Markup Language (SAML) and want to connect with third-party applications without migrating to OpenID Connect (OIDC), this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was originally designed with OIDC in mind. To use it in SAML applications, you must accommodate specific security and uniqueness requirements. This guide details what you need to support and how to make resource requests to a third-party app using XAA. Table of Contents How XAA in SAML works XAA implementation checklist for SAML-federated applications Request the refresh token Request the ID-JAG token Request the access token Handle token expiration Making cross-application requests from your SAML app securely Configure your XAA SAML Requesting App in Okta Register and configure the AI Agent in Okta Test the SAML 2.0 app Validate the XAA connection end-to-end Learn more about Cross App Access, SAML, and OAuth 2.0 How XAA in SAML works When an agent (like one running in Claude) needs API access, it presents an Identity Assertion Authorization Grant (ID-JAG). The ID-JAG is a short-lived JSON Web Token (JWT) issued by the Identity Provider (IdP) for your app's user. You exchange the ID-JAG token for an access token to the resource application you're connecting with. The sequence diagram shown below describes the SAML XAA flow and how your application fits in. You'll handle the flow in two parts: where your application requests the ID-JAG from the IdP using a refresh token, and where your app requests the access token from the ID-JAG from the third-party resource app's authorization server. XAA implementation checklist for SAML-federated applications Follow the guide in this section to support XAA in your SAML application when your app connects to a third-party resource application. The XAA flow places the burden of token validation onto the IdP and the resource ap ## How Pixel and Android are bringing a new level of trust to your images with C2PA Content Credentials DevFeed: [How Pixel and Android are bringing a new level of trust to your images with C2PA Content Credentials]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2025-09-10T15:59:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Google](), [Android Security](), [Security](), [Mobile](), [Hardware](), [Generative AI]() Tags: [android](), [android-security](), [digital-signature](), [generative-ai](), [google](), [hardware](), [pixel](), [security]() ### AI overview Google describes how Pixel 10, Pixel Camera, and Google Photos will support C2PA Content Credentials to improve the provenance and verification of digital media. The article outlines Android-specific security capabilities, including Assurance Level 2, private certificate management, trusted timestamps, offline support, and hardware-backed protection, and says developers can apply the model to Android apps. ### Source excerpt Posted by Eric Lynch, Senior Product Manager, Android Security, and Sherif Hanna, Group Product Manager, Google C2PA Core At Made by Google 2025, we announced that the new Google Pixel 10 phones will support C2PA Content Credentials in Pixel Camera and Google Photos. This announcement represents a series of steps towards greater digital media transparency: The Pixel 10 lineup is the first to have Content Credentials built in across every photo created by Pixel Camera. The Pixel Camera app achieved Assurance Level 2, the highest security rating currently defined by the C2PA Conformance Program. Assurance Level 2 for a mobile app is currently only possible on the Android platform. A private-by-design approach to C2PA certificate management, where no image or group of images can be related to one another or the person who created them. Pixel 10 phones support on-device trusted time-stamps, which ensures images captured with your native camera app can be trusted after the certificate expires, even if they were captured when your device was offline. These capabilities are powered by Google Tensor G5, Titan M2 security chip, the advanced hardware-backed security features of the Android platform, and Pixel engineering expertise. In this post, we'll break down our architectural blueprint for bringing a new level of trust to digital media, and how developers can apply this model to their own apps on Android. A New Approach to Content Credentials Generative AI can help us all to be more creative, productive, and innovative. But it can be hard to tell the difference between content that's been AI-generated, and content created without AI. The ability to verify the source and history--or provenance--of digital content is more important than ever. Content Credentials convey a rich set of information about how media such as images, videos, or audio files were made, protected by the same digital signature technology that has secured online transactions and mobile apps for decades. I ## Ed25519 Support Arrives in Chrome DevFeed: [Ed25519 Support Arrives in Chrome]() Original publisher: [Read original article]() Author: Bumblefudge Published: 2025-08-13T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [ed25519](), [Chrome](), [browsers](), [Cryptography](), [digital signature](), [API](), [Security](), [Web Development]() Tags: [api](), [browsers](), [chrome](), [cryptography](), [digital-signature](), [ed25519](), [object-object](), [security]() ### AI overview Chrome 137 adds Ed25519 support to the WebCrypto API, completing support across the major browser engines described in the article. ### Source excerpt Ed25519 is now supported in Chrome, finally joining the other browsers after much effort. ## Forging Ahead in Federal Compliance: Chainguard's FIPS 140-3 and 186-5 Milestones DevFeed: [Forging Ahead in Federal Compliance: Chainguard's FIPS 140-3 and 186-5 Milestones]() Original publisher: [Read original article]() Published: 2025-06-06T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [container images](), [Security](), [Testing](), [interoperability]() Tags: [chainguard](), [chainguard-containers](), [chainguard-fips](), [compliance](), [container-images](), [cryptographic](), [digital-signature](), [ed25519](), [federal-compliance](), [federal-information-processing-standards](), [fedramp](), [fips](), [fips-140-3](), [fips-validation](), [nist](), [openssl](), [security](), [signing](), [standards](), [validation]() ### AI overview Chainguard FIPS container images are being upgraded to support current FIPS 140-3 and FIPS 186-5 standards, including OpenSSL with FIPS 140-3 validation and Ed25519 signing support. ### Source excerpt Chainguard FIPS images have been upgraded to start using the OpenSSL project 3.1.2 module with FIPS 140-3 validation. Learn more about what this means. ## Trying out ESP32-C3's security features using QEMU DevFeed: [Trying out ESP32-C3's security features using QEMU]() Original publisher: [Read original article]() Author: John Lee Published: 2024-04-04T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-C3](), [ESP32](), [qemu](), [Security](), [Emulator](), [Encryption](), [boot](), [configuration](), [virtualization](), [RISC-V]() Tags: [blog](), [boot](), [configuration](), [digital-signature](), [emulator](), [esp-idf](), [esp32](), [esp32-c3](), [espressif](), [flash-encryption](), [iot](), [latest-release](), [qemu](), [releases-section](), [risc-v](), [security]() ### AI overview This article explains how to exercise ESP32-C3 security features under QEMU before deploying them to real hardware. It describes the risks of irreversible eFuse programming, QEMU's ESP32-C3 system emulation and firmware compatibility, and workflows for testing security configurations. ### Source excerpt Overview# ESP32 series of SoCs supports multiple security features like trusted boot, flash encryption, secure storage etc. There are also dedicated peripherals to support use-cases like HMAC and digital signature. For most of these features the eFuse storage in the ESP32-C3 is responsible for storing the private keys and also the configuration bits. eFuse memory is one time programmable and hence care must be taken whilst enabling the security features. ## Ultimate Go: Advanced Engineering Episode 15 DevFeed: [Ultimate Go: Advanced Engineering Episode 15]() Original publisher: [Read original article]() Published: 2023-01-12T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [digital-signature](), [ecdsa](), [ethereum](), [generate](), [go-blockchain](), [library](), [private-key](), [public-address](), [public-key](), [transactions]() ### AI overview This video tutorial explains how to derive a blockchain user's unique address from a public key recovered from a transaction signature. It covers reading the public key, validating the transaction's origin, and generating the user's address using Go Ethereum library functions. ### Source excerpt Introduction In episode 14, Bill architected a solution to digitally sign the transactions on his blockchain. His solution retrieved the private key by : loading private key data from disk, parsing the key data and returning the ECDSA private key. The private key is then used to generate the signature of a transaction. While writing the code to perform this functionality, Bill highlighted how a blockchain node can use a transaction's signature to extrapolate the public key. ## Creating Ethereum Digital Signatures with Go DevFeed: [Creating Ethereum Digital Signatures with Go]() Original publisher: [Read original article]() Published: 2023-01-11T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Blockchain](), [Ethereum](), [Transactions](), [Library]() Tags: [bitcoin](), [blockchain](), [code](), [digital-signature](), [ecdsa](), [ethereum](), [go](), [go-blockchain](), [library](), [private-key](), [public-key](), [signed-data](), [transactions]() ### AI overview A video tutorial demonstrating how to create Ethereum digital signatures with Go. It covers private ECDSA keys, signing objects, loading private keys from disk, decoding Ethereum signatures, and deriving public keys using the Go Ethereum library. ### Source excerpt Introduction In episode 13, Bill discussed the idea of adding salt to a hash and how modern crypto-currency blockchains use it to better interpret requests sent to nodes. He continued by defining a function called stamp that embeds a salt within a hash. While writing the function, Bill stated that he would use keccak256 as it's the same algorithm used by Ethereum to generate hash values. Bill will use the APIs provided with Go Ethereum to generate a keccak256 hash. He plans on reusing the stamp function in the future to digitally sign transactions performed on his blockchain. ## Ultimate Go: Advanced Engineering Episode 13 DevFeed: [Ultimate Go: Advanced Engineering Episode 13]() Original publisher: [Read original article]() Published: 2023-01-11T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Go Language](), [Algorithm](), [Security](), [Ethereum](), [API](), [Transactions]() Tags: [algorithm](), [bitcoin](), [blockchain](), [data-stamping](), [digital-signature](), [digital-signatures](), [ethereum](), [go](), [go-blockchain](), [hash](), [hexademical](), [how-to](), [keccak256](), [salt](), [security](), [video]() ### AI overview This video tutorial explains how to add a salt value to transaction hashes, implement the keccak256 algorithm in Go, and use transaction stamping in a blockchain. It also discusses digital signatures and related security issues. ### Source excerpt Introduction In episode 12, Bill laid out his strategy to handle data hashing on his blockchain. The first step he took was to create a package to handle the cryptographical aspects of his blockchain. After that, he wrote a hash function that met the requirements outlined in his strategy. This function took transaction data as a parameter and returned a hexadecimal representation of the hash. To implement this function, Bill imported packages from the Go standard library and Ethereum API. ## Ethereum Identity Verification with ECDSA for a Decentralized Blockchain DevFeed: [Ethereum Identity Verification with ECDSA for a Decentralized Blockchain]() Original publisher: [Read original article]() Published: 2023-01-03T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Ethereum](), [Go Language]() Tags: [bitcoin](), [blockchain](), [blockchain-asset](), [digital-signature](), [distributed](), [ecdsa](), [ecdsa-encryption](), [encryption](), [ethereum](), [ethereum-authentication](), [genesis-record](), [go-blockchain](), [identity](), [identity-management](), [verification]() ### AI overview This video tutorial explores how Ethereum confirms user identity and explains how ECDSA can verify transaction authenticity without relying on a central key store. ### Source excerpt Introduction In episode 10, Bill dove into the technical implementation of his genesis record and defined a custom Go type representing the record. While doing so, he provided an in-depth look at the reasoning behind the fields he included.. After declaring this type, Bill wrote a function that loads the genesis record from disk and onto memory. His function will use the standard library encoding/json package to load JSON data from a hard-coded file path. ## Espressif Announces AWS IoT ExpressLink Modules Based on ESP32-C3 DevFeed: [Espressif Announces AWS IoT ExpressLink Modules Based on ESP32-C3]() Original publisher: [Read original article]() Author: John Lee Published: 2021-11-30T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-C3](), [Amazon Web Services](), [Espressif](), [Internet of things](), [Bluetooth](), [Wi-Fi](), [ESP32]() Tags: [announce](), [authentication](), [aws](), [aws-iot](), [blog](), [bluetooth-le](), [digital-signature](), [esp32-c3](), [esp32-s3](), [espressif](), [flash-encryption](), [iot](), [messaging](), [newsletter](), [ota](), [provisioning](), [psram](), [secure-boot](), [security](), [wi-fi]() ### AI overview Espressif announces AWS IoT ExpressLink modules based on the ESP32-C3 SoC, with Wi-Fi and Bluetooth LE 5.0 connectivity, a serial interface for AWS IoT services, and pre-provisioned security features. ### Source excerpt Hi everyone, Espressif is proud to announce the availability of new Wi-Fi modules implementing the AWS IoT ExpressLink specification. Espressif's AWS IoT ExpressLink modules, ESP32-C3-MINI-1-N4-A, are based on the ESP32-C3 SoC and offer Wi-Fi + Bluetooth LE 5.0 connectivity, thus providing any host MCUs with out-of-the-box, seamless, AWS cloud connectivity. ## ESP32-S2: Digital Signature Peripheral DevFeed: [ESP32-S2: Digital Signature Peripheral]() Original publisher: [Read original article]() Author: John Lee Published: 2021-02-03T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Esp32 S2](), [Security](), [TLS (Transport Layer Security)](), [Cryptography](), [Internet of things](), [Encryption](), [Espressif](), [ESP32-C3](), [ESP32-S3]() Tags: [blog](), [cryptography](), [digital-signature](), [embedded-systems](), [esp-idf](), [esp32-c3](), [esp32-s2](), [esp32-s3](), [espressif](), [flash-encryption](), [iot](), [secure-boot](), [security](), [tls]() ### AI overview This tutorial explains how Espressif's Digital Signature peripheral protects an IoT device's RSA private key. Available on the ESP32-S2, ESP32-C3, and ESP32-S3, the peripheral generates hardware-accelerated RSA signatures without exposing the private key to software. It uses one-time-programmable eFuse key blocks whose software read access can be disabled. ### Source excerpt The Transport Layer Security(TLS) is an integral part of the IoT world. It facilitates a secure way of communication between the IoT device and the cloud service. The TLS uses asymmetric key cryptography for security that consists of a private key and corresponding public key (certificate). As the name suggests public key is shared with everyone and the private key is kept secured on the IoT device. It is pivotal to keep the private key secure in order to protect the identity of the IoT device. ## Medical Device Security Standards DevFeed: [Medical Device Security Standards]() Original publisher: [Read original article]() Author: Adam Published: 2019-11-02T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Cybersecurity](), [standard]() Tags: [checksums](), [connectivity](), [cost](), [cybersecurity](), [digital-signature](), [disclosure](), [funding](), [medical-devices](), [network](), [pii](), [security](), [standards]() ### AI overview This commentary compares four cybersecurity approaches for medical devices: a comprehensive process-centered framework, MITA's factual material data sheet, disclosure of device behavior and cybersecurity properties, and funded threat-modeling work. It notes that differing national requirements can increase costs and create conflicting demands. ### Source excerpt Recently, I've seen four cybersecurity approaches for medical devices, and we can learn by juxtaposing them. ## Sending and Authenticating Messages with Elliptic Curves DevFeed: [Sending and Authenticating Messages with Elliptic Curves]() Original publisher: [Read original article]() Published: 2014-04-14T10:00:38Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Security](), [Protocol (disambiguation)](), [Python](), [Code](), [Learning]() Tags: [code](), [diffie-hellman](), [digital-signature](), [discrete-logarithm](), [elliptic-curves](), [encryption](), [protocol](), [public-key](), [python](), [security](), [shamir-massey-omura]() ### AI overview A tutorial explains how the Shamir-Massey-Omura protocol can send a message without a pre-shared secret, using elliptic-curve point operations and private locking values. It also notes that the accompanying Python implementations are intended for learning rather than practical security use. ### Source excerpt Last time we saw the Diffie-Hellman key exchange protocol, and discussed the discrete logarithm problem and the related Diffie-Hellman problem, which form the foundation for the security of most protocols that use elliptic curves. Let's continue our journey to investigate some more protocols. Just as a reminder, the Python implementations of these protocols are not at all meant for practical use, but for learning purposes. We provide the code on this blog's Github page, but for the love of security don't actually use them.