# RSA Published articles for RSA. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Honest Migration Playbook - IPsec Series, Part 11 DevFeed: [The Honest Migration Playbook - IPsec Series, Part 11]() Original publisher: [Read original article]() Author: Julio Gomez Published: 2026-09-14T19:41:59Z Content type: article Language: en Sources: [Cisco Blogs]() Topics: [migration](), [Post-Quantum](), [Authentication](), [Networks]() Tags: [authentication](), [cisco](), [developer](), [migration](), [networks](), [post](), [post-quantum](), [post-quantum-authentication](), [post-quantum-cryptography-pqc](), [rsa](), [series]() ### AI overview This article presents an operational playbook for migrating authentication in a live multi-router IPsec network from RSA certificates to ML-DSA. It contrasts authentication with key exchange, explains a mixed hub-and-spoke deployment using ML-KEM-768, and reports that changing signature algorithms cannot be performed without tunnel disruption. ### Source excerpt The final post in the IPsec series: a fully quantum-safe tunnel on Cisco 8000 routers, both pillars live on real hardware. Part 11 closes the arc with the migration playbook and what a healthy post-quantum tunnel actually looks like. ## Sign JWTs from your Functions without managing private keys DevFeed: [Sign JWTs from your Functions without managing private keys]() Original publisher: [Read original article]() Author: Jeff Pope Published: 2026-08-18T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [JSON Web Tokens](), [OpenID connect (OIDC)](), [JSON Schema](), [Command-line interface](), [dashboards]() Tags: [cli](), [configuration](), [jwks](), [oidc](), [openid-connect](), [rsa](), [tokens](), [vercel]() ### AI overview Vercel KMS enables Vercel Functions to sign JWTs and arbitrary messages with managed asymmetric keys, keeping private keys out of application code and environment variables. It supports issuer and key management, environment-specific access grants, claim constraints, JSON Schema validation, and standard OIDC and JWKS-based verification. ### Source excerpt Vercel KMS lets you sign JWTs and arbitrary messages from your Vercel Functions using managed asymmetric signing keys, so private keys never live in your code or environment variables. Your function authenticates with its Vercel OIDC token, and the private key stays inside Vercel's key management service while verifiers use only the public key. With Vercel KMS you can: Create and rotate issuers and signing keys (RSA, ECDSA, and EdDSA) from the CLI and dashboard. Sign JWTs with custom claims and a configurable TTL, or sign raw bytes, using the @vercel/kms package. Grant a project signing access per environment, including production, preview, development, and custom environments. Constrain the claims a project can request per grant, and validate token claims against a JSON Schema. Verify signed tokens anywhere. Each issuer publishes a public OpenID Connect Discovery document at https://kms.vercel.com//.well-known/openid-configuration and a JWK set at https://kms.vercel.com//jwks.json, so any standard OIDC or JOSE library can validate tokens without Vercel-specific code. Sign a token inside a function: Verify a token anywhere with a standard JOSE library, using the issuer's public JWKS: Set up an issuer and grant a project access from the CLI: As a best practice, create a separate issuer per project and environment. Isolating issuers keeps each token audience distinct, scopes signing access to exactly one project and environment, and lets you rotate or revoke keys for one without affecting the others. To get started, read the docs or open Key Management in your team's dashboard. Read more ## Developer and security research roundup: DNS resilience, RIPE NCC token exposure, IPv6 measurement, and quantum cryptography DevFeed: [Developer and security research roundup: DNS resilience, RIPE NCC token exposure, IPv6 measurement, and quantum cryptography]() Original publisher: [Read original article]() Author: Russ Published: 2026-06-19T12:04:04Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [Amazon Route 53](), [Resilience](), [Network](), [Security, Privacy and Abuse Prevention](), [Quantum Computing](), [Cryptography](), [Internet]() Tags: [cryptography](), [dns](), [ipv6](), [network](), [public-key](), [quantum](), [resilience](), [rsa](), [worth-reading]() ### AI overview A roundup of developer and security research covering authoritative DNS resilience, exposed RIPE NCC single sign-on session tokens, IPv6 address measurement, asset speculation, and progress toward quantum computers breaking RSA-based public-key cryptography. ### Source excerpt In this post, I discuss our recent work that models and analyses the resilience of authoritative DNS infrastructure that supports individual domain names on the Internet. The RIPE NCC made its all-powerful single sign-on tokens available to over 1000 third parties. From a single link click, any logged-in RIPE NCC user would leak their session token. Identifying active IPv6 addresses is a challenging task, but it's also an important one. As researchers and network operators, it helps us understand the current deployment, identify weak spots that need strengthening, and detect vulnerable devices for disclosure. The fundamental bubble barometer is that speculators buy an asset because they expect the price to keep rising, not because they want the income generated by the asset. Indeed, most speculators don't plan on holding the asset long enough receive any income. Recently, there has been a surge in progress in quantum computing that has shortened the hypothetical timeline on which quantum computers can 'break' traditional public-key cryptography that uses the RSA scheme. ## Five Minutes of Prime Time DevFeed: [Five Minutes of Prime Time]() Original publisher: [Read original article]() Published: 2026-05-16T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [Mathematics]() Tags: [games](), [mathematics](), [mobile](), [number](), [puzzles](), [rsa]() ### AI overview A personal story about nerd culture at RSA, including mathematics and physics forums, monthly team challenges, and a five-minute contest to write as many prime numbers between 1 and 1000 as possible. ### Source excerpt Let me share a very silly story from roughly 18 years ago! In 2008, I joined RSA, the network security company named after the initials of the inventors of the RSA algorithm, Rivest, Shamir and Adleman, who were also the founders of RSA, the company. There was a bit of a nerd culture in the workplace where topics like prime numbers, combinatorics, probability theory, etc. were discussed fervently. A prime-number employee number was considered a lucky charm. I had a rather nice large five-digit prime number as my employee number, which I remember being quite pleased about. There were internal forums for almost all kinds of topics. A few I remember fondly were a mathematics forum where colleagues would challenge each other with mathematical puzzles and a similar physics forum where, for some reason, crafting contrived paradoxes using special and general relativity and putting them up for debate was a common activity. The participants would analyse each paradox to determine if it truly was one or if it could be resolved into something that was no longer a paradox. I loved hanging out on those forums and made many friends there. The mathematics forum, in particular, gave me plenty of fun problems to think about. In fact, my Langford Pairing (2011) post was the result of a question I had stumbled upon there. The human resources (HR) department used to organise afternoon games once every month where people would self-organise into teams and solve a small challenge. There was a cash prize for the winning team each time. The HR folks were very well aware of the nerd culture and the fascination with prime numbers, but they probably did not know enough about exactly what type of problems we were fascinated with. So in one of the monthly game events, the HR team gave us this challenge. Write as many prime numbers between 1 and 1000 as you can in 5 minutes. The 5-minute timer started immediately. Really, that was the challenge. We all looked at each other in surprise, wondering ## How to protect your organization from the telnyx PyPI compromise DevFeed: [How to protect your organization from the telnyx PyPI compromise]() Original publisher: [Read original article]() Published: 2026-03-27T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Malware](), [open-source-security](), [SDKs](), [C2](), [Python](), [API keys](), [Encryption](), [Open Source](), [chainguard](), [ssh](), [GitHub Actions]() Tags: [api-keys](), [c2](), [chainguard](), [chainguard-libraries](), [encryption](), [github-actions](), [malware](), [open-source-security](), [pypi](), [pypi-attack](), [pypi-compromise](), [rsa](), [security](), [ssh](), [supply-chain](), [teampcp](), [telnyx](), [telnyx-attack](), [telnyx-compromise](), [trivy]() ### AI overview The article explains that malicious versions 4.87.1 and 4.87.2 of the Telnyx Python SDK were published to PyPI after publishing credentials were compromised. The malware executes at module scope, downloads from a remote C2 server, and uses a WAV file to conceal a Windows persistence binary or credential harvester for Linux and macOS. It recommends immediate removal, version pinning, credential rotation, and persistence checks. The article also attributes the attack to TeamPCP and connects it to a broader coordinated supply chain campaign. ### Source excerpt Malicious telnyx versions hit PyPI in a wider supply chain attack. Chainguard customers stayed protected by using source-built, verified libraries. ## MCUboot - Getting Started Guide for ESP32 DevFeed: [MCUboot - Getting Started Guide for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2026-01-09T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Embedded Software Dev](), [Espressif](), [NuttX](), [Zephyr RTOS](), [configuration]() Tags: [blog](), [bootloader](), [building](), [configuration](), [ecdsa](), [ed25519](), [embedded](), [esp32](), [espressif](), [firmware](), [flashing](), [getting-started](), [mcuboot](), [nuttx](), [rsa](), [secure-boot](), [security](), [zephyr]() ### AI overview A practical guide to using MCUboot on ESP32-based projects. It explains MCUboot's secure bootloader role, environment and application configuration, bootloader building, and flashing, with examples for NuttX and Zephyr RTOS applications. ### Source excerpt This guide provides a practical getting-started walkthrough for using MCUboot on ESP32. It covers step-by-step environment setup, bootloader building, application configuration, and flashing. It also gives an overview of MCUboot's execution flow. ## Blog: GPG Key Rotation for Falco Packages (2026) DevFeed: [Blog: GPG Key Rotation for Falco Packages (2026)]() Original publisher: [Read original article]() Published: 2025-12-12T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Security](), [Package manager](), [releases](), [apt]() Tags: [announcements](), [apt](), [falco](), [import](), [installation](), [releases](), [rotation](), [rsa](), [security]() ### AI overview Falco maintainers are rotating the 4096-bit RSA GPG key used to sign official RPM and DEB packages because the existing key expires on January 17, 2026. The transition uses a soft launch followed by a hard cut-over, and existing users should update their keyrings before January 12, 2026. ### Source excerpt The GPG key used to sign official Falco packages (RPM and DEB) is set to expire on January 17, 2026. To ensure the security and continuity of our software distribution, the Falco maintainers will be rotating to a new 4096-bit RSA key. We have designed a two-phase "Soft Launch" strategy to make this transition as smooth as possible, providing a one-month transition window before the old key is retired. The Rotation Plan To avoid immediate disruption, we are rolling out the new key in two distinct phases. You can follow the detailed progress in our tracking issue #3750. Phase 1: Soft Launch (Dec 12, 2025) What happens: The new GPG key has been published and added to our repository configuration. Dev Builds: Will begin using the New Key immediately. Stable Builds: No stable releases are planned for this phase. If any hotfixes are released, they will be signed with New Key as well. Key Bundle: The official key URL has been updated to serve a bundle containing both the Old (valid) and New (valid) keys. Phase 2: Hard Cut-Over (Jan 12-17, 2026) What happens: This is the maintenance window where we fully switch to the new key. Mass Resign: All existing stable packages on download.falco.org will be resigned with the New Key. Revocation: The Old Key will be officially revoked and removed from the active bundle. Impact: If you have not updated your keyring by this date, your package manager (apt or yum) will reject updates with a signature verification error. Action Items for Users We strongly recommend all users update their GPG keyring before January 12, 2026 to avoid interruption. New Users If you are installing Falco for the first time following our Install on a host (DEB,RPM) instructions, no action is required. The installation process will guide you to fetch the new key bundle, ensuring you are ready for both phases. Existing Users If you have an existing Falco installation, you must manually import the new key. We have updated the key file at our standard URL to includ ## Signing Git commits and tags with SSH DevFeed: [Signing Git commits and tags with SSH]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2025-11-19T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Git](), [ssh](), [ECDSA](), [ed25519]() Tags: [dsa](), [ecdsa](), [ed25519](), [git](), [rsa](), [signing](), [ssh]() ### AI overview The article explains that Git commits and tags can be signed with SSH keys instead of GPG. It states that Ed25519, ECDSA, and RSA keys are supported, while DSA keys are not. ### Source excerpt You can sign Git commits and tags with SSH keys instead of GPG. ## Introducing JWT Signing Keys DevFeed: [Introducing JWT Signing Keys]() Original publisher: [Read original article]() Author: Stojan Dimitrovski Published: 2025-07-14T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [JSON Web Tokens](), [Security](), [Cryptography](), [Supabase](), [API keys]() Tags: [api-keys](), [compliance](), [cryptography](), [jwt](), [latency](), [public-key](), [rotation](), [rsa](), [security](), [soc2]() ### AI overview Supabase introduces asymmetric JWT signing keys for Supabase Auth, along with new API keys to support migration and improve application security. The system uses a private key for signing and a public key for local token verification, reducing dependence on the Auth server, network latency, and shared-secret management. It supports RSA and elliptic-curve signing algorithms and safer key rotation. ### Source excerpt A new JWT signing keys system based on public key cryptography to improve your project's security and performance. ## Meet Chainguard at RSA 2025 in San Francisco on April 28-May 1 DevFeed: [Meet Chainguard at RSA 2025 in San Francisco on April 28-May 1]() Original publisher: [Read original article]() Published: 2025-04-21T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard containers](), [chainguard libraries](), [chainguard vms](), [Containers]() Tags: [2025](), [announcements](), [article](), [bsides](), [chainguard](), [chainguard-containers](), [events](), [rsa](), [rsa-conference](), [security-events]() ### AI overview Chainguard announces its participation in RSA 2025 in San Francisco from April 28 to May 1. The company will exhibit at Booth #2441, demonstrate Chainguard Containers, Chainguard Libraries, and Chainguard VMs, and host a nearby lounge with refreshments, networking, and private meeting rooms. Chainguard will also sponsor BSides San Francisco and offer opportunities to meet its team during RSA week. ### Source excerpt Chainguard will be at RSA 2025 at Booth #2441 on April 28-May 1, and will also be participating in ancillary events throughout the week. ## How Ditching RSA Made Teleport 77% More CPU-Efficient DevFeed: [How Ditching RSA Made Teleport 77% More CPU-Efficient]() Original publisher: [Read original article]() Author: info@goteleport.com (Nic Klaassen) Published: 2025-03-13T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Cryptography](), [ECDSA](), [ed25519](), [Latency](), [cpu](), [Security]() Tags: [cryptography](), [ecdsa](), [ed25519](), [latency](), [performance](), [rsa](), [security](), [ssh](), [ssl](), [switching]() ### AI overview Teleport's switch from RSA to ECDSA and Ed25519 in Teleport 17 reduced benchmarked CPU usage by 77% and latency by 37%, while requiring compatibility work across deployed environments and third-party tools. ### Source excerpt How switching from RSA to ECDSA and Ed25519 reduced Teleport CPU usage by 77% and decreased latency by 37% ## Can Snyk Detect JWT Security Issues? DevFeed: [Can Snyk Detect JWT Security Issues?]() Original publisher: [Read original article]() Author: Liran Tal Published: 2025-03-04T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [JSON Web Tokens](), [Authentication](), [Security](), [API](), [JSON](), [Microservices](), [distributed-systems]() Tags: [api](), [apis](), [authentication](), [awareness](), [best-practices](), [blog](), [code-security](), [developer](), [devrel](), [distributed-systems](), [how-to](), [json](), [jwt](), [microservices](), [payload](), [rsa](), [security](), [security-best-practices](), [signing](), [snyk](), [snyk-code](), [stateless](), [token](), [tokens](), [verify](), [vulnerability]() ### AI overview This article explains what JSON Web Tokens are, how their header, payload, and signature work, and how their stateless design supports authentication for APIs, microservices, and distributed systems. It focuses on detecting and preventing JWT security risks, including broken authentication vulnerabilities and the danger of storing sensitive data in unencrypted tokens. ### Source excerpt How to detect and prevent JWT security risks? Follow Snyk's JWT security best practices for enhanced security. ## Going beyond "shift left" to extend AppSec in all directions DevFeed: [Going beyond "shift left" to extend AppSec in all directions]() Original publisher: [Read original article]() Author: Ben Desjardins Published: 2024-07-09T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Application Security](), [Security](), [sdlc](), [Testing](), [Artificial Intelligence]() Tags: [application-security](), [awareness](), [blog](), [devops](), [executive](), [interest](), [megawatt](), [rsa](), [sdlc](), [security](), [shift-left](), [snyk-platform]() ### AI overview The article argues that application security should move beyond a visibility-only or narrowly "shift left" approach. It advocates extending proactive security across the software development life cycle, with stronger prioritization, remediation, visibility, and context for applications and assets. The article introduces a multi-directional application security model, though the supplied text ends during its discussion of the model's first direction. ### Source excerpt Read thoughts from our Vice President of Product Marketing after his time at RSA Conference 2024, including his thoughts on proactive security. ## Join Chainguard at RSAC 2024: Immersive art, expert talks, and karaoke DevFeed: [Join Chainguard at RSAC 2024: Immersive art, expert talks, and karaoke]() Original publisher: [Read original article]() Published: 2024-04-26T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Application Security](), [container-security](), [open-source-security](), [Cybersecurity]() Tags: [article](), [chainguard](), [conference](), [container-security](), [cybersecurity](), [open-source-security](), [rsa](), [rsac](), [talks]() ### AI overview Chainguard invites attendees to RSAC 2024 in San Francisco for an immersive lounge experience, expert and lightning talks, movie screenings, karaoke, and container security challenge workshops in the AppSec Village. The article also provides event logistics and a conference discount code. ### Source excerpt RSAC 2024 with Chainguard: Lounge, movies, lightning talks, karaoke reception at MoAD, & AppSec Village workshops. Get your discount code here! ## Build affordable Secure connected devices with ESP32-H2 DevFeed: [Build affordable Secure connected devices with ESP32-H2]() Original publisher: [Read original article]() Author: John Lee Published: 2023-05-11T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Security](), [Espressif](), [Hardware](), [cyber resilience act]() Tags: [blog](), [connectivity](), [ecdsa](), [embedded-systems](), [encryption](), [esp32](), [esp32-h2](), [espressif](), [flash-encryption](), [hardware](), [matter](), [mcu](), [rsa](), [secure-boot](), [security]() ### AI overview This article explains the ESP32-H2's hardware and software security features for connected devices, including Secure Boot, flash encryption, debug-interface protection, secure storage, memory protection, and device identity protection. It also describes RSA-PSS and ECDSA verification options, public-key storage and revocation, and the encryption of off-chip flash memory. ### Source excerpt The awareness, as well as the associated concerns, about connected device security, is ever-increasing. With the European Union's Cyber Resilience Act also coming into effect soon, it has become ever so important to have security features built-in to the devices in hardware. The Espressif ESP32-H2 has been built to provide an affordable security solution to all and thus integrates a variety of security features. ## New Chainguard Academy tutorial: Cosign the manual way DevFeed: [New Chainguard Academy tutorial: Cosign the manual way]() Original publisher: [Read original article]() Published: 2023-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [Tutorial](), [sigstore](), [Security](), [supply-chain-security](), [Command-line interface](), [Software]() Tags: [algorithm](), [chainguard](), [chainguard-academy](), [cli](), [cosign](), [rekor](), [rsa](), [security](), [sha-256](), [signing](), [sigstore](), [software-artifact-signing](), [transparency-log](), [trust](), [tutorial](), [verify]() ### AI overview This article introduces a Chainguard Academy tutorial that explains Cosign's blob-signing capabilities. It covers generating an RSA key pair, signing data with SHA-256, uploading signatures to the Rekor transparency log, and verifying the signature. ### Source excerpt New Chainguard Academy tutorial unpacks Cosign the manual way and explores Cosign's blob signing capabilities. ## SSH Keys Compared: RSA, ECDSA, Ed25519 DevFeed: [SSH Keys Compared: RSA, ECDSA, Ed25519]() Original publisher: [Read original article]() Author: ev@goteleport.com (Ev Kontsevoy) Published: 2022-04-07T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [OpenSSH](), [Cryptography](), [Authentication](), [public key](), [private key](), [certificates](), [Post-Quantum]() Tags: [authentication](), [certificates](), [cryptography](), [ecdsa](), [ed25519](), [openssh](), [post-quantum](), [private-key](), [public-key](), [rsa](), [ssh]() ### AI overview A guide to SSH public-key authentication that compares RSA, ECDSA, and EdDSA (Ed25519), recommends Ed25519 for most uses, and discusses older-system compatibility, key generation, fingerprints, rotation, and certificates. ### Source excerpt Comparing SSH keys: RSA, DSA, ECDSA, and Ed25519 explained, with a straight algorithm recommendation and the move from keys to certificates. Read on. ## Espressif Releases the ESP32-S2 Datasheet and Describes Its Features DevFeed: [Espressif Releases the ESP32-S2 Datasheet and Describes Its Features]() Original publisher: [Read original article]() Author: John Lee Published: 2019-10-09T00:00:00Z Content type: news Language: en Sources: [Blog on Developer Portal]() Topics: [Esp32 S2](), [SOC](), [Wi-Fi](), [Espressif](), [Internet of things](), [Security](), [USB]() Tags: [blog](), [esp32-s2](), [espressif](), [flash-encryption](), [instagram](), [internet-of-things](), [iot](), [newsletter](), [rsa](), [secure-boot](), [security](), [soc](), [wi-fi]() ### AI overview Espressif announces the release of the ESP32-S2 datasheet and outlines the chip's Wi-Fi, low-power, peripheral, USB, and hardware security capabilities. The newsletter also mentions other Espressif and partner news. ### Source excerpt Hi everyone, Apologies for the typo in our latest newsletter, at the beginning of which ESP32-S3 was mentioned, instead of the correct ESP32-S2 . So, it is the ESP32-S2 datasheet that has been released. You can now find it online in the documentation section of our website. ESP32-S2 is a low-power 2.4 GHz Wi-Fi System-on-Chip (SoC) solution. ## Analyzing a simple encryption scheme using GitHub SSH keys DevFeed: [Analyzing a simple encryption scheme using GitHub SSH keys]() Original publisher: [Read original article]() Published: 2018-09-30T17:54:00Z Content type: opinion Language: en Sources: [Latacora]() Topics: [Encryption](), [Cryptography](), [GitHub](), [ssh](), [openssl](), [OpenSSH](), [SSL](), [Command-line interface]() Tags: [attacks](), [channel](), [encryption](), [github](), [openssl](), [padding](), [public-key](), [rsa](), [ssh](), [ssl]() ### AI overview This introductory analysis examines encrypting secrets for recipients using their GitHub SSH public keys and an OpenSSL RSA command. It explains that the scheme's PKCS#1 v1.5 and SSLv2 padding variants are vulnerable to Bleichenbacher's oracle attack, while noting that the described offline threat model does not provide access to a decryption oracle. ### Source excerpt (This is an introductory level analysis of a scheme involving RSA. If you're already comfortable with Bleichenbacher oracles you should skip it.) Someone pointed me at the following suggestion on the Internet for encrypting secrets to people based on their GitHub SSH keys. I like the idea of making it easier for people to leverage key material and tools they already have. The encryption instructions are: echo "my secret" > message.txt curl -q "https://github.com/${USER}.keys" \ | head -n 1 \ > recipient.pub ssh-keygen -e -m pkcs8 -f recipient.pub > recipient.pem openssl rsautl \ -encrypt \ -pubin \ -inkey recipient.pem \ -ssl \ -in message.txt \ -out encrypted.txt Anything using an openssl command line tool makes me a little uncomfortable. Let's poke at it a little. ## ROCA vs. ROBOT: Comparing Candidates for the 2018 Best Cryptographic Attack Pwnie Award DevFeed: [ROCA vs. ROBOT: Comparing Candidates for the 2018 Best Cryptographic Attack Pwnie Award]() Original publisher: [Read original article]() Published: 2018-08-08T22:52:00Z Content type: opinion Language: en Sources: [Latacora]() Topics: [Cryptography](), [Exploit](), [Security, Privacy and Abuse Prevention](), [email](), [TLS (Transport Layer Security)]() Tags: [black-hat](), [conference](), [crypto](), [exploit](), [rsa](), [vulnerabilities]() ### AI overview This commentary compares the ROCA RSA key generation flaw and the ROBOT "Return Of Bleichenbacher" attack as candidates for the 2018 Best Cryptographic Attack Pwnie award. It also considers Efail and IOTA as notable cryptographic research and attack work from the same period. ### Source excerpt The ROCA RSA key generation flaw or ROBOT, the "Return Of Bleichenbacher" attack: which is most deserving of the "Best Cryptographic Attack" Pwnie award at the 2018 Black Hat USA conference? Only one can survive. Let us consider. Assume for the moment that it's down to those two: ROBOT and ROCA. But first take a moment to consider the best cases for the "runners up". They are all excellent; it was a very good year for crypto research. ## The default OpenSSH key encryption is worse than plaintext DevFeed: [The default OpenSSH key encryption is worse than plaintext]() Original publisher: [Read original article]() Published: 2018-08-03T14:02:00Z Content type: opinion Language: en Sources: [Latacora]() Topics: [OpenSSH](), [Encryption](), [Cryptography](), [public key]() Tags: [credentials](), [encryption](), [github](), [openssh](), [openssl](), [public-key](), [rsa](), [ssh]() ### AI overview The article examines default OpenSSH encryption for RSA private keys and argues that deriving the AES key with MD5 of the password and part of the IV makes the protection vulnerable to efficient password guessing. It concludes that the encryption can be ineffective, especially when passwords are reused. ### Source excerpt Update: I don't know if we can take credit for it or if it's random chance, but I note OpenSSH changed its default in the release after this blog post. The system works! The eslint-scope npm package got compromised recently, stealing npm credentials from your home directory. We started running tabletop exercises: what else would you smash-and-grab, and how can we mitigate that risk? Most people have an RSA SSH key laying around. That SSH key has all sorts of privileges: typically logging into prod and GitHub access. Unlike an npm credential, an SSH key is encrypted, so perhaps it's safe even if it leaks? Let's find out! ## Byzantium HF Announcement DevFeed: [Byzantium HF Announcement]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2017-10-12T07:51:59Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [Development](), [client]() Tags: [2017](), [announcement](), [cryptographic](), [development](), [ethereum](), [fork](), [implement](), [network](), [protocol-announcements](), [rsa](), [upgrade]() ### AI overview Ethereum announced a planned Byzantium hard fork at block 4,370,000, expected between 12:00 and 13:00 UTC on October 16, 2017. The announcement lists client versions and protocol changes, including new opcodes, transaction receipt status fields, cryptographic operations, a delayed difficulty bomb, and a reduced block reward. ### Source excerpt The Ethereum network will be undergoing a planned hard fork at block number 4.37mil (4,370,000), which will likely occur between 12:00 UTC and 13:00 UTC on Monday, October 16, 2017. The Ropsten test network underwent a hard fork on September 19th (UTC) at block number 1.7mil (1,700,000). A countdown timer can be... ## Setup up HTTPS for your e-commerce site with Let's Encrypt and Google App Engine. DevFeed: [Setup up HTTPS for your e-commerce site with Let's Encrypt and Google App Engine.]() Original publisher: [Read original article]() Author: Tristan Sokol Published: 2017-05-09T00:37:36Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Tutorial](), [Security](), [Google](), [Web](), [hosting](), [openssl]() Tags: [apis](), [e-commerce](), [google](), [how-to](), [openssl](), [private-key](), [rsa](), [security](), [web-hosting]() ### AI overview A tutorial explaining how to set up HTTPS for an e-commerce website hosted on Google App Engine using Let's Encrypt. It covers the prerequisites and begins the process of generating a private key and certificate signing request with OpenSSL. ### Source excerpt HTTPS is an important part of keeping your customer's information secure on the web--here's a quick tutorial on how to set up HTTPS on your App Engine website to use our e-commerce APIs. ## Let's Encrypt Announces Public Certificate Release Starting September 14, 2015 DevFeed: [Let's Encrypt Announces Public Certificate Release Starting September 14, 2015]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2015-06-16T18:20:00Z Content type: news Language: en Sources: [Andrea Corbellini]() Topics: [certificates](), [ECDSA]() Tags: [automated](), [cryptography](), [ecdsa](), [free](), [launch](), [let-s-encrypt](), [open](), [rsa](), [security](), [technical](), [tls](), [web]() ### AI overview Let's Encrypt announced that its certificates would be released to the public starting the week of September 14, 2015. The article also discusses its IdenTrust-signed intermediate certificates and planned ECDSA keys. ### Source excerpt Let's Encrypt (the free, automated and open certificate authority) has just announced its launch schedule. According to it, certificates will be released to the public starting from the week of September 14, 2015. Their intermediate certificates, which were generated a few days ago, will be signed by IdenTrust. What this means is that if you browse a web page secured by Let's ... [Next page]()