#OpenSSL 📢 -- The OpenSSL Corporation Becomes Official General Partner of ZOO Brno’s Beringia Enclosure

🔗 https://openssl-corporation.org/post/2025-07-10-zoo-brno-gen-partner/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Corporation

#OpenSSL 📢 -- Contributors to the OpenSSL Library (June 2025)

🔗 https://openssl-library.org/post/2025-07-10-june-contributors/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Library

#OpenSSL 📢 -- The Features of 3.5: EVP_SKEY

🔗 https://openssl-foundation.org/post/2025-07-08-3.5-evp_skey/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Foundation

#OpenSSL 📢 -- The State of the OpenSSL Community (3.5)

🔗 https://openssl-foundation.org/post/2025-07-07-state-of-community-3.5/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Foundation

AmiSSL 5.21 Update Released
#AmigaOS #AmiSSL #IBrowse #OpenSSL #RetroComputing #AmigaDevelopment #SecureAmiga
https://theoasisbbs.com/amissl-5-21-update-released/?feed_id=4157&_unique_id=686bc7a91ba25

@nilz hatte schon befürchtet, dass der Podcast diese Vorurteile aufgreift. Diese Einzelentwickler*innen gibt es auch, aber ist nicht die Masse.OSS ist Big Business, problematisch sind manchmal kleine Projekte, die tatsächlich wichtig sind, aber zu wenig betreut, siehe auch #OpenSSL .Diese kleinen Projekte, die nicht essentiell sind, sind nicht so bedeutend oder problematisch, wenn was schief geht. Fehler gibt es ja auch bei closed source, das ist kein Alleinstellungsmerkmal.

I've been playing around with certificates lately and wrote a small bit to remember some #OpenSSL commands https://humberto.io/bits/extract-certificate-from-a-domain/

#OpenSSL 📢 -- There's still time to share your story

🔗 https://openssl-library.org/post/2025-07-03-wild-ending/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Library

#OpenSSL 📢 -- There's still time to share your story

🔗 https://openssl-foundation.org/post/2025-07-03-wild-ending/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Foundation

Version 5.21 of the open source encryption protocol AmiSSL has been released for AmigaOS 3 and 4, which is now based on the latest version 3.5.1 (2025/07/01) of OpenSSL.

https://www.amiga-news.de/en/news/AN-2025-07-00003-EN.html

#Amiga #AmigaOS3 #AmigaOS4 #AmiSSL #OpenSSL

#OpenSSL 3.5.1 (#LTS) has been released (#SSL / #TLS) https://openssl-library.org/

#OpenSSL 📢 -- Openssl Release Announcement for 3.5.1, 3.4.2, 3.3.4, 3.2.5, and 3.0.17

🔗 https://openssl-library.org/post/2025-07-01-release-announcement/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Library

KEKS кодек и криптографические сообщения

Данная статья напоминает о проблемах X.509 PKI и реализаций ASN.1. Предлагает компактный, быстрый, детерминированный, потоковый и простой формат кодирования данных KEKS, а также криптографические сообщения для подписи и шифрования данных с поддержкой пост-квантовых алгоритмов.

https://habr.com/ru/articles/923810/

#c #go #python #keks #asn1 #x509 #openssl #криптография #pqc #hpke #pgp #cms

@Viss @bagder
For some, it seems to work. My experience of bug bounties (through #openssl) has mostly been slop, even before AI entered the scene. @bagder has had a better experience, it seems.

Decided to not use #libev and use #libevent instead for socket/timer/event loop/callback system. Other than I trust it more, I like the baked in #openssl support (will use for #telnet+tls later).

Additionally, going to try out sqlcipher (#sqlite3 + AES encryption baked in) for data storage. Everything will be stored in a sqlite3 database.

Using cmake and pkg-config, #C, sqlite3 (sqlcipher), libevent, and openssl.

Decided to just focus on developing the software on KDE neon distro (Ubuntu LTS) and worry about other OSes later. I spent too much time worrying about ease of build/install instructions for other operating systems instead of just deciding and moving forward.

#BBS #NecroNeonBBS #Vaporware

Just released: #swad 0.12 🥂

swad is the "Simple Web Authentication Daemon". It basically offers adding form + #cookie #authentication to your reverse proxy (designed for and tested with #nginx "auth_request"). I created it mainly to defend against #malicious_bots, so among other credential checker modules for "real" logins, it offers a proof-of-work mechanism for guest logins doing the same #crypto #challenge known from #Anubis.

swad is written in pure #C with minimal dependencies (#zlib, #OpenSSL or compatible, and optionally #PAM), and designed to work on any #POSIX system. It compiles to a small binary (200 - 300 kiB depending on compiler and target platform).

This release brings (among a few bugfixes) improvements to make swad fit for "heavy load" scenarios: There's a new option to balance the load across multiple service worker threads, so all cores can be fully utilized if necessary, and it now keeps lots of transient objects in pools for reuse, which helps to avoid memory fragmentation and ultimately results in lower overall memory consumption.

Read more about it, download the .tar.xz, build and install it .... here:

https://github.com/Zirias/swad

#OpenSSL 📢 -- OpenSSL Corporation at NYC Tech Week 2025: Advancing Security, Trust, and Open Innovation

🔗 https://openssl-corporation.org/post/2025-06-23-techdays-nyc/?utm_source=atom_feed

From #OpenSSL -- Blog on OpenSSL Corporation

I added OpenSSL encryption into script for NS exchange between servers with Pihole 6.

https://codeberg.org/reddy75/pinse

#linux #openssl #bash #script #encryption #exchange

Would you say this is an accurate description of (some of the) #OpenSSL forks family tree?

(These are the OpenSSL forks #curl supports.)

Oh boy, I have a lead! And it's NOT related to #TLS. I finally noticed another pattern: #swad only #crashed when running as a #daemon. The daemonizing wasn't the problem, but the default logging configuration attached to it: "fake async", by letting a #threadpool job do the logging.

Forcing THAT even when running in foreground, I can finally reproduce a crash. And I wouldn't be surprised if that was actually the reason for crashing "pretty quickly" with #LibreSSL (and only rarely with #OpenSSL), I mean, something going rogue in your address space can have the weirdest effects.