# openssl OpenSSL is an open-source toolkit and software library for TLS, cryptography, and secure communication, including a command-line tool for cryptographic tasks. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Security updates for Wednesday DevFeed: [Security updates for Wednesday]() Original publisher: [Read original article]() Author: corbet Published: 2026-09-16T13:40:53Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security](), [Linux](), [nginx](), [openssl](), [Python](), [OpenSSH]() Tags: [debian](), [linux](), [nginx](), [openssh](), [openssl](), [python](), [security](), [updates]() ### AI overview Security updates were issued by AlmaLinux, Debian, Fedora, Oracle, Red Hat, SUSE, and Ubuntu for packages including kernels, nginx, OpenSSL, Python, Perl, Git, Docker, OpenSSH, and other software. ### Source excerpt Security updates have been issued by AlmaLinux (kernel, kernel-rt, libkcapi, nginx, nginx:1.24, openssl, osbuild-composer, perl, perl:5.32, python-tornado, rsync, and rust), Debian (cjose and nginx), Fedora (environment-modules, erlang, GitPython, knot, perl-Authen-SASL, python-configargparse, ruby, rubygems, and sblim-sfcb), Oracle (firefox, git-lfs, gstreamer1-plugins-base, kernel, libkcapi, nginx, nginx:1.26, openssl, osbuild-composer, perl, perl-YAML-Syck, postgresql18, python-tornado, and rust), Red Hat (fence-agents, git-lfs, microcode_ctl, osbuild-composer, podman, python-pyasn1, and resource-agents), SUSE (389-ds, ant, bson-devel, chirp-20260911, docker, gimp, google-cloud-sap-agent, hauler, kernel, kimi-code, libpcap, python-GitPython, python310, syncthing, yast2-samba-client, and zstd-jni), and Ubuntu (aom, imagemagick, kitty, openssh, phpseclib, policykit-1, python-sql, python-webob, shibboleth-sp, simplesamlphp, snapcast, srt, and suricata-update). ## curl 8.22.0 DevFeed: [curl 8.22.0]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-09-02T05:52:46Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Security](), [HTTP](), [openssl](), [API](), [TLS (Transport Layer Security)](), [Command-line interface]() Tags: [bugfixes](), [command-line](), [curl](), [curl-and-libcurl](), [cve](), [cves](), [http](), [openssl](), [release](), [security](), [tls]() ### AI overview The curl 8.22.0 release includes six changes, 302 bug fixes, and nine curl/libcurl security fixes plus one wcurl fix. It adds Apple GSS Framework support, API guards, experimental HTTP Message Signatures support, and Apple fast UDP, while blocking NTLM fallback in SPNEGO and dropping TLS-SRP support. ### Source excerpt Welcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new ... Continue reading curl 8.22.0 -> ## 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. ## TLS Certificate Cheat Sheet - OpenSSL & Curl DevFeed: [TLS Certificate Cheat Sheet - OpenSSL & Curl]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-09-22T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [TLS (Transport Layer Security)](), [certificates](), [Cheat sheet](), [openssl](), [cURL]() Tags: [certificates](), [cheat-sheet](), [curl](), [openssl](), [tls](), [tools]() ### AI overview A cheat sheet for creating, inspecting, signing, validating, and testing TLS certificates and related keys and CSRs using OpenSSL and cURL. ### Source excerpt https://collective.flashbots.net/t/tls-certificates-know-how-quick-reference/5292 ## FuzzSlice: Separating real CVEs from fakes through fuzzing DevFeed: [FuzzSlice: Separating real CVEs from fakes through fuzzing]() Original publisher: [Read original article]() Published: 2024-09-19T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Fuzzing/Fuzz testing](), [Vulnerabilities](), [openssl](), [Security](), [Testing](), [supply-chain-security]() Tags: [cves](), [false-positives](), [fuzzing](), [openssl](), [security](), [software-supply-chain]() ### AI overview Chainguard Labs presents FuzzSlice, a fuzzing technique for determining whether CVEs are exploitable within an application context. In an evaluation of 18 OpenSSL CVEs, it classified 12 as exploitable and six as unreachable or false positives. ### Source excerpt Chainguard Labs explores FuzzSlice, a novel fuzzing technique, to improve vulnerability remediation by distinguishing exploitable CVEs from false positives. ## Blog: Falco Weekly 46 - 2023 DevFeed: [Blog: Falco Weekly 46 - 2023]() Original publisher: [Read original article]() Published: 2023-11-17T00:00:00Z Content type: article Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Development](), [ci](), [CMake](), [openssl](), [osx](), [win32]() Tags: [blog](), [changes](), [ci](), [cmake](), [falco](), [openssl](), [osx](), [weekly](), [win32]() ### AI overview Falco Weekly 46 reviews development changes across Falco-related repositories, including library cleanups, fixes, new features, experimental ppc64le support, an OpenSSL upgrade, CI support for win32 and osx, and Kubernetes metadata work involving gRPC. ### Source excerpt This is the first of a series of weekly blog post whose aim is to give a quick overview about the development of Falco and its related projects. What happened in Falco this week? Let's go through the major changes that happened in various repositories under the falcosecurity organization. Libs Lots of cleanups happened in the libs repo; the most outstanding ones being: udig engine removal (https://github.com/falcosecurity/libs/pull/1485) dropped legacy metadata clients for k8s and mesos (https://github.com/falcosecurity/libs/pull/1478) cleaned up proc callback handling code (https://github.com/falcosecurity/libs/pull/1471) Please, note that the removal of the legacy k8s client is part of a bigger effort to entirely rewrite it as a plugin, with a more future proof architecture and language. See the tracking issue: https://github.com/falcosecurity/libs/issues/987. All of these cleanups account for ~26k loc removed!! :rocket: Moreover, some fixes landed: removed some more Undefined Behavior warnings from integer copies (https://github.com/falcosecurity/libs/pull/1481) solved win32 linking issues with zlib (https://github.com/falcosecurity/libs/pull/1484) prevent libbpf stats from being collected with no bpf stats (https://github.com/falcosecurity/libs/pull/1487) Finally, some new features were merged: libraries will now be properly installed under CMAKE_INSTALL_LIBDIR (https://github.com/falcosecurity/libs/pull/1101) added ppc64le experimental support for modern bpf driver (https://github.com/falcosecurity/libs/pull/1475) upgraded openssl to 3.1.4 (https://github.com/falcosecurity/libs/pull/1488) Also, we now have a target release date and a tracking issue for libs 0.14 and next driver release: https://github.com/falcosecurity/libs/issues/1482. Falco Now Falco builds and runs on win32 and osx too! https://github.com/falcosecurity/falco/pull/2889 While Falco won't ship for these platforms, we will now have proper CI for them. Following the huge round of cleanups in libs ## Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates DevFeed: [Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2023-06-27T17:17:25Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Azure](), [Windows Subsystem for Linux](), [SSL](), [openssl](), [apt](), [pip]() Tags: [apt](), [azure](), [certificates](), [dns](), [install](), [openssl](), [password](), [private-key](), [ssl](), [windows](), [wsl]() ### AI overview This tutorial explains how to use Certbot in Windows Subsystem for Linux with Let's Encrypt to create a wildcard certificate, convert it to a password-protected PFX containing the certificate chain, and upload it to Azure App Service. It also describes importing and exporting the certificate in Windows before updating the App Service binding. ### Source excerpt There are many let's encrypt automatic tools for azure but I also wanted to see if I could use certbot in wsl to generate a wildcard certificate for the azure Friday website and then upload the resulting certificates to azure app service. Azure app service ultimately needs a specific format called dot PFX that includes the full certificate path and all intermediates. Per the docs, App Service private certificates must meet the following requirements: Exported as a password-protected PFX file, encrypted using triple DES. Contains private key at least 2048 bits long Contains all intermediate certificates and the root certificate in the certificate chain. If you have a PFX that doesn't meet all these requirements you can have Windows reencrypt the file. I use WSL and certbot to create the cert, then I import/export in Windows and upload the resulting PFX. Within WSL, install certbot: sudo apt update sudo apt install python3 python3-venv libaugeas0 sudo python3 -m venv /opt/certbot/ sudo /opt/certbot/bin/pip install --upgrade pip sudo /opt/certbot/bin/pip install certbot Then I generate the cert. You'll get a nice text UI from certbot and update your DNS as a verification challenge. Change this to make sure it's two lines, and your domains and subdomains are correct and your paths are correct. sudo certbot certonly --manual --preferred-challenges=dns --email YOUR@EMAIL.COM --server https://acme-v02.api.letsencrypt.org/directory --agree-tos --manual-public-ip-logging-ok -d "azurefriday.com" -d "*.azurefriday.com" sudo openssl pkcs12 -export -out AzureFriday2023.pfx -inkey /etc/letsencrypt/live/azurefriday.com/privkey.pem -in /etc/letsencrypt/live/azurefriday.com/fullchain.pem I then copy the resulting file to my desktop (check your desktop path) so it's now in the Windows world. sudo cp AzureFriday2023.pfx /mnt/c/Users/Scott/OneDrive/Desktop Now from Windows, import the PFX, note the thumbprint and export that cert. Import-PfxCertificate -FilePath "AzureFriday2023.pfx" - ## Removing Calendar Invites using PowerShell + Azure CLI DevFeed: [Removing Calendar Invites using PowerShell + Azure CLI]() Original publisher: [Read original article]() Author: dustin@dustn.dev (Dustin Summers) Published: 2021-12-20T10:26:38Z Content type: tutorial Language: en Sources: [Dustin Summers]() Topics: [PowerShell](), [Command-line interface](), [openssl](), [active directory](), [Cloud]() Tags: [active-directory](), [azure](), [cli](), [commands](), [it-management-services-powershell-microsoft-azure-azure-active-directory](), [openssl](), [powershell]() ### AI overview The article describes removing calendar invitations created by a departing employee while retaining the employee's account temporarily. It discusses PowerShell access problems on updated Macs caused by differing OpenSSL versions and presents Azure CLI as an alternative for managing the Azure environment. ### Source excerpt Apart from my day job, I moonlight helping small-to-medium size companies' install and manage secure IT infrastructures, along with building and creating applications for them. I offer these services (and more) through my company, Attica, LLC. It is a passion of mine to help companies that are starting out have a solid IT/Cyber infrastructure that can scale with their company as these businesses are vulnerable and common targets of ransomware and phishing attacks. ## Node.js 12.22.8 (LTS) DevFeed: [Node.js 12.22.8 (LTS)]() Original publisher: [Read original article]() Published: 2021-12-16T23:42:46Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [Open Source](), [certificates](), [cross-platform](), [openssl](), [libuv]() Tags: [certificates](), [cross-platform](), [js](), [libuv](), [mozilla](), [node-js](), [open-source](), [openssl](), [release]() ### AI overview Node.js 12.22.8 is an LTS release that updates c-ares to fix a regression resolving CNAME records containing underscores and updates root certificates from Mozilla's Network Security Services 3.71. It also includes dependency, platform, documentation, runtime, test, and worker-process fixes. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 15.0.1 (Current) DevFeed: [Node.js 15.0.1 (Current)]() Original publisher: [Read original article]() Published: 2020-10-21T20:26:35Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [cross-platform](), [Open Source](), [npm](), [V8](), [openssl]() Tags: [cross-platform](), [javascript](), [linux](), [macos](), [node-js](), [npm](), [open-source](), [openssl](), [release](), [v8](), [windows]() ### AI overview Node.js 15.0.1 (Current) is a release update that fixes a crypto regression in randomFillSync, upgrades npm to 7.0.3, updates the V8 version patch number, and includes documentation, build, source, and test changes. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## 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. ## Accessing Yahoo and AOL Mail Features Through IMAP DevFeed: [Accessing Yahoo and AOL Mail Features Through IMAP]() Original publisher: [Read original article]() Author: marcelatoath Published: 2018-05-18T16:19:38Z Content type: tutorial Language: en Sources: [Yahoo]() Topics: [Protocol (disambiguation)](), [servers](), [client](), [openssl]() Tags: [aol](), [developers](), [openssl](), [protocol](), [server](), [yahoo](), [yahoo-engineering]() ### AI overview This tutorial explains how developers can access Yahoo and AOL Mail metadata such as DECOS and THREADID through IMAP. It demonstrates an IMAP command sequence using openssl to connect, authenticate, list folders, select the inbox, and search for message UIDs. ### Source excerpt USE IMAP TO ACCESS SOME UNIQUE FEATURES By Libby Lin, Principal Product Manager Well, we actually won't show you how we create the magic in our big OATH consumer mail factory. But nevertheless we wanted to share how interested developers could leverage some of our unique features we offer for our Yahoo and AOL Mail customers. To drive experiences like our travel and shopping smart views or message threading, we tag qualified mails with something we call DECOS and THREADID. While we will not indulge in explaining how exactly we use them internally, we wanted to share how they can be used and accessed through IMAP. So let's just look at a sample IMAP command chain. We'll just assume that you are familiar with the IMAP protocol at this point and you know how to properly talk to an IMAP server. So here's how you would retrieve DECO and THREADIDs for specific messages: 1. CONNECT openssl s_client -crlf -connect imap.mail.yahoo.com:993 2. LOGIN a login username password a OK LOGIN completed 3. LIST FOLDERS a list "" "*" * LIST (\Junk \HasNoChildren) "/" "Bulk Mail" * LIST (\Archive \HasNoChildren) "/" "Archive" * LIST (\Drafts \HasNoChildren) "/" "Draft" * LIST (\HasNoChildren) "/" "Inbox" * LIST (\HasNoChildren) "/" "Notes" * LIST (\Sent \HasNoChildren) "/" "Sent" * LIST (\Trash \HasChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Trash/l2" * LIST (\HasChildren) "/" "test level 1" * LIST (\HasNoChildren) "/" "test level 1/nestedfolder" * LIST (\HasNoChildren) "/" "test level 1/test level 2" * LIST (\HasNoChildren) "/" "&T2BZfXso-" * LIST (\HasNoChildren) "/" "&gQKAqk7WWr12hA-" a OK LIST completed 4.SELECT FOLDER a select inbox * 94 EXISTS * 0 RECENT * OK [UIDVALIDITY 1453335194] UIDs valid * OK [UIDNEXT 40213] Predicted next UID * FLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk) * OK [PERMANENTFLAGS (\Answered \Deleted \Draft \Flagged \Seen $Forwarded $Junk $NotJunk)] Permanent flags * OK [HIGHESTMODSEQ 205] a OK [READ-WRITE] SELECT completed; ## 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. ## Encrypt your data with MessageEncryptor DevFeed: [Encrypt your data with MessageEncryptor]() Original publisher: [Read original article]() Published: 2015-11-17T07:44:55Z Content type: tutorial Language: en Sources: [Jolly Good Code]() Topics: [Rails](), [openssl](), [Encryption](), [Cryptography]() Tags: [built-in](), [encryption](), [openssl](), [rails]() ### AI overview This tutorial explains that Rails' built-in MessageEncryptor uses OpenSSL::Cipher to encrypt data and is easy to use. ### Source excerpt Rails has a built-in class MessageEncryptor which uses OpenSSL::Cipher to perform encryption, and it's easy to use that to encrypt your data. ## Using Heartbleed as a starting point DevFeed: [Using Heartbleed as a starting point]() Original publisher: [Read original article]() Published: 2014-04-10T09:06:18Z Content type: opinion Language: en Sources: [Antirez]() Topics: [openssl](), [Security](), [code security](), [Static code analysis](), [C]() Tags: [c](), [code-analysis](), [code-security](), [open-source](), [openssl](), [security]() ### AI overview The article uses the Heartbleed vulnerability in OpenSSL as a starting point for discussing how to improve system software security. It argues for greater investment in security audits, open-source software development, and static and dynamic checks, while noting that changing languages or specifications is unlikely in the near term. ### Source excerpt The strong reactions about the recent OpenSSL bug are understandable: it is not fun when suddenly all the internet needs to be patched. Moreover for me personally how trivial the bug is, is disturbing. I don't want to point the finger to the OpenSSL developers, but you just usually think at those class of issues as a bit more subtle, in the case of a software like OpenSSL. Usually you fail to do sanity checks *correctly*, as opposed to this bug where there is a total *lack* of bound checks in the memcpy() call. However sometimes in the morning I read the code I wrote the night before and I'm deeply embarrassed. Programmers sometimes fail, I for sure do often, so my guess is that what is needed is a different process, and not a different OpenSSL team. There is who proposes a different language safer than C, and who proposes that the specification is broken because it is too complex. Probably there is some truth in both arguments, however it is unlikely that we move to a different specification or system language soon, so the real question is, what we can do now to improve system software security? 1) Throw money at it. Making system code safer is simple if there are investments. If different companies hire security experts to do code auditings in the OpenSSL code base, what happens is that the probability of discovering a bug like heartbleed is greater. I've seen very complex bugs that are triggered by a set of non-trivial conditions being discovered by serious code auditing efforts. A memcpy() without bound checks is something that if you analyze the code security-wise, will stand out in the first read. And guess how heartbleed was discovered? Via security auditings performed at Google. Probably the time to consider open source something that mostly we take from is over. Many companies should follow the example of Google and other companies, using workforce for OSS software development and security. 2) Static and dynamic checks. Static code analysis is, as a side ef ## Heartbleed: What the OpenSSL Bug Means for Internet Users DevFeed: [Heartbleed: What the OpenSSL Bug Means for Internet Users]() Original publisher: [Read original article]() Published: 2014-04-09T21:44:27Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [openssl](), [bug](), [Library](), [Internet]() Tags: [bug](), [internet](), [library](), [openssl](), [technical]() ### AI overview The article explains that Heartbleed is a bug in the widely used OpenSSL library affecting almost all internet users, with an explanation intended for non-technical readers. ### Source excerpt A bug in the widely used OpenSSL library named 'heartbleed' affects almost all users on the internet. Here's what it means for non-technical users. ## Security issue on the ReactOS infrastructure DevFeed: [Security issue on the ReactOS infrastructure]() Original publisher: [Read original article]() Published: 2014-04-09T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Security](), [Vulnerabilities](), [openssl](), [SSL](), [TLS (Transport Layer Security)]() Tags: [cve](), [free](), [open-source](), [openssl](), [os](), [react](), [reactos](), [release](), [security](), [ssl](), [tls](), [vulnerability](), [win32](), [winapi]() ### AI overview ReactOS reports that its infrastructure was affected by the Heartbleed vulnerability in OpenSSL. The project applied the fix, renewed its SSL certificates and private keys, and warned that account information and sessions might have been compromised. Users were advised to change their passwords and review their accounts. ### Source excerpt Dear all, In case you don't use SSL/TLS on our infrastructure (web sites - drupal, jira, fisheye), skip reading (and reconsider your choices about such non-usage). As you may (should?) have heard recently, OpenSSL has suffered a critical security vulnerability (CVE-2014-0160), known as Heartbleed Bug (http://heartbleed.com/). Most of our services were using an affected release of OpenSSL, with heartbeat feature activated. Be it, mails services, web services (Drupal, Jira). ## Generate ECDSA key with OpenSSL DevFeed: [Generate ECDSA key with OpenSSL]() Original publisher: [Read original article]() Author: Tom Published: 2013-12-17T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [ECDSA](), [openssl](), [private key]() Tags: [ecdsa](), [generate](), [linux](), [openssl](), [private-key](), [security]() ### AI overview This tutorial explains how to generate an ECDSA private key with OpenSSL, including selecting a curve and using a 256-bit key, followed by creating a self-signed certificate. ### Source excerpt After the last NSA scandal I've found some time to read some texts about PFS and ECDSA keys lately. I always used RSA keys but wanted to give a try to ECDSA so I wanted to give it a try (test performance, etc). Here is how I've done it. Firstly find your favorite curve. A short tip about bit length and complexity could be found here. From it you will now that using 256 bit ECDSA key should be enough for next 10-20 years. ## Konwersja formatu certyfikatu dla telefonów Nokia DevFeed: [Konwersja formatu certyfikatu dla telefonów Nokia]() Original publisher: [Read original article]() Author: Tom Published: 2012-04-11T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [openssl]() Tags: [openssl](), [rsa](), [x509]() ### AI overview A practical guide to converting self-signed certificates and private keys between PEM and DER formats with OpenSSL, so a certificate can be installed on a Nokia E72. ### Source excerpt Chciałem zaimportować mój certyfikat self-signed do Nokii E72 by nie krzyczała przy sprawdzaniu poczty. Potrzebowałem certyfikatu w formacie DER, a miałem w PEM - chwilę szukałem jak dokonać konwersji, więc ku pamięci zapisuję kilka gotowych poleceń: Konwersja certyfikatu z PEM na DER openssl x509 -in in.crt -inform PEM -out out.crt -outform DER Konwersja certyfikatu z DER na PEM openssl x509 -in in.crt -inform DER -out out.crt -outform DER Konwersja klucza z formatu PEM na DER openssl rsa -in in.crt -inform PEM -out out.crt -outform DER Konwersja klucza z formatu DER na PEM openssl rsa -in in.crt -inform DER -out out.crt -outform PEM Po konwersji certyfikat w formacie DER wystarczy wrzucić na kartę i otworzyć z menadżera plików, zainstalować.