digitalcourage.social

openSUSE LinuxSecurity & tooling got stronger too! <a href="https://fosstodon.org/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#vim</a> 9.1.1508 now supports <a href="https://fosstodon.org/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a> clipboard & new language syntax, <a href="https://fosstodon.org/tags/myrlyn" class="mention hashtag" rel="nofollow noopener" target="_blank">#myrlyn</a> 0.9.7 improves sudo env handling, and key fixes landed in bind, <a href="https://fosstodon.org/tags/sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#sudo</a>, php8, <a href="https://fosstodon.org/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>, libxml2, git & more. <a href="https://fosstodon.org/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tumbleweed</a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://news.opensuse.org/2025/08/01/tw-monthly-update-july/" rel="nofollow noopener" translate="no" target="_blank">https://news.opensuse.org/2025/08/01/tw-monthly-update-july/</a>

Kevin Karhan :verified:<a href="https://social.glitched.systems/@froge" class="u-url mention" rel="nofollow noopener" target="_blank">@froge</a> that's a question I'd like to ask <a href="https://mastodon.social/@mozilla_support" class="u-url mention" rel="nofollow noopener" target="_blank">@mozilla_support</a> ...<ul><li>My assumption is that <a href="https://infosec.space/tags/Mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mozilla</a>'s <a href="https://infosec.space/tags/NSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NSS</a> not only supports a shitton of architectures with specific, custom code but also includes the <a href="https://infosec.space/tags/certificates" class="mention hashtag" rel="nofollow noopener" target="_blank">#certificates</a> to trust per default, and those are thousands of CAs with potentially dozens of certificates each...</li></ul>AFAIK <a href="https://infosec.space/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> doesn't ship with any certificates at all...

NickSome interesting vulnerabilities were patched and <a href="https://infosec.exchange/tags/apache2" class="mention hashtag" rel="nofollow noopener" target="_blank">#apache2</a> has released Apache/2.4.65.<a href="https://infosec.exchange/tags/SSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSL</a> <a href="https://infosec.exchange/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a>

ClemensAnother commit landed in <a href="https://chaos.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>: <a href="https://github.com/openssl/openssl/commit/6b93db7bfd572e81fac581c5be7b0d7509febb80" rel="nofollow noopener" translate="no" target="_blank">https://github.com/openssl/openssl/commit/6b93db7bfd572e81fac581c5be7b0d7509febb80</a>This time, it's a drive-by thing inspired by <a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@jwildeboer</a> who's working on S/MIME X.509 certificates: the X.509 standards renamed one of the bits in the keyUsage extension from `nonRepudiation` to `contentCommitment`, and OpenSSL only understood the old name.Slowly improving the world one commit at a time.

Richard Levitte<a href="https://mastodon.sl/@afink" class="u-url mention" rel="nofollow noopener" target="_blank">@afink</a> <a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> <a href="https://mastodon.nu/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> has some migration guides, are those functions not included in there? Which two?

daniel:// stenberg://I nominate <a href="https://docs.openssl.org/3.3/man3/d2i_X509/" rel="nofollow noopener" translate="no" target="_blank">https://docs.openssl.org/3.3/man3/d2i_X509/</a> as <a href="https://mastodon.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>'s worst man page. And there's fierce competition for that award.And in the end it does not even mention the weird behavior: it stores errors in an internal queue which mysteriously makes the *next* invoked function fail...

Nicola Tuveri<a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> 📢 -- OpenSSL Foundation endorses UN Open Source Principles🔗 <a href="https://openssl-foundation.org/post/2025-08-07-un-open-source-principles/?utm_source=atom_feed" rel="nofollow noopener" translate="no" target="_blank">https://openssl-foundation.org/post/2025-08-07-un-open-source-principles/?utm_source=atom_feed</a>From <a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> -- Blog on OpenSSL Foundation

Clemens'We are pleased to inform you that we accept your proposal “<a href="https://chaos.social/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a>'s path to post-quantum cryptography with OpenSSL” for the <a href="https://chaos.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> Conference'Looks like I'm going to Prague in October!

MynacolAnd for some more context: Did you know <a class="hashtag" href="https://social.mynacol.xyz/tag/openssl" rel="nofollow noopener" target="_blank">#openssl</a> 3.x is quite poor in its performance? <a href="https://www.haproxy.com/blog/state-of-ssl-stacks" rel="nofollow noopener" target="_blank">https://www.haproxy.com/blog/state-of-ssl-stacks</a>

MynacolI finally tried to replace <a class="hashtag" href="https://social.mynacol.xyz/tag/openssl" rel="nofollow noopener" target="_blank">#openssl</a> with <a class="hashtag" href="https://social.mynacol.xyz/tag/aws" rel="nofollow noopener" target="_blank">#aws</a>-lc on some of my services. Unfortunately, <a class="hashtag" href="https://social.mynacol.xyz/tag/nginx" rel="nofollow noopener" target="_blank">#nginx</a> and <a class="hashtag" href="https://social.mynacol.xyz/tag/mosquitto" rel="nofollow noopener" target="_blank">#mosquitto</a> lack support for it. Instead, I successfully switched <a class="hashtag" href="https://social.mynacol.xyz/tag/bind" rel="nofollow noopener" target="_blank">#BIND</a> to use aws-lc.I later also noticed that the <a class="hashtag" href="https://social.mynacol.xyz/tag/rustls" rel="nofollow noopener" target="_blank">#rustls</a> compatibility shim is in nixpkgs 25.05, but here BIND is missing some variables. And despite the wrapper being explicitly made for nginx, it also fails here with<pre><code>/nix/store/mkvc0lnnpmi604rqsjdlv1pmhr638nbd-binutils-2.44/bin/ld: objs/src/stream/ngx_stream_ssl_module.o: in function `ngx_stream_ssl_servername': /build/nginx-1.28.0/src/stream/ngx_stream_ssl_module.c:606:(.text+0xd59): undefined reference to `SSL_SESSION_get0_hostname' </code></pre>A shame. I wanted to change to more modern libraries.Untested: <a class="hashtag" href="https://social.mynacol.xyz/tag/dovecot" rel="nofollow noopener" target="_blank">#dovecot</a> and <a class="hashtag" href="https://social.mynacol.xyz/tag/postfix" rel="nofollow noopener" target="_blank">#postfix</a> (they lack a <code>services.(dovecot2|postfix).package</code> variable to easily change the used package. A PR for dovecot is already open to add support for it.

testssl.sh :verified:testssl.sh makes it easier now for also for MacOS users to run a <a href="https://infosec.exchange/tags/QUIC" class="mention hashtag" rel="nofollow noopener" target="_blank">#QUIC</a> protocol test -- if you have <a href="https://infosec.exchange/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a> from e.g. <a href="https://infosec.exchange/tags/homebrew" class="mention hashtag" rel="nofollow noopener" target="_blank">#homebrew</a> installed.It automagically uses that one for testing QUIC then, in 3.3dev.

KielKontrovers Blog<a href="https://norden.social/@nilz" class="u-url mention" rel="nofollow noopener" target="_blank">@nilz</a> 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 <a href="https://norden.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> .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.

Richard Levitte<a href="https://mastodon.social/@Viss" class="u-url mention" rel="nofollow noopener" target="_blank">@Viss</a> <a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> For some, it seems to work. My experience of bug bounties (through <a href="https://mastodon.nu/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a>) has mostly been slop, even before AI entered the scene. <a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> has had a better experience, it seems.

Felix Palmen :freebsd: :c64:Just released: <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> 0.12 🥂swad is the "Simple Web Authentication Daemon". It basically offers adding form + <a href="https://mastodon.bsd.cafe/tags/cookie" class="mention hashtag" rel="nofollow noopener" target="_blank">#cookie</a> <a href="https://mastodon.bsd.cafe/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> to your reverse proxy (designed for and tested with <a href="https://mastodon.bsd.cafe/tags/nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#nginx</a> "auth_request"). I created it mainly to defend against <a href="https://mastodon.bsd.cafe/tags/malicious_bots" class="mention hashtag" rel="nofollow noopener" target="_blank">#malicious_bots</a>, so among other credential checker modules for "real" logins, it offers a proof-of-work mechanism for guest logins doing the same <a href="https://mastodon.bsd.cafe/tags/crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#crypto</a> <a href="https://mastodon.bsd.cafe/tags/challenge" class="mention hashtag" rel="nofollow noopener" target="_blank">#challenge</a> known from <a href="https://mastodon.bsd.cafe/tags/Anubis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Anubis</a>.swad is written in pure <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a> with minimal dependencies (<a href="https://mastodon.bsd.cafe/tags/zlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#zlib</a>, <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> or compatible, and optionally <a href="https://mastodon.bsd.cafe/tags/PAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#PAM</a>), and designed to work on any <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> 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:<a href="https://github.com/Zirias/swad" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/swad</a>

daniel:// stenberg://Would you say this is an accurate description of (some of the) <a href="https://mastodon.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> forks family tree?(These are the OpenSSL forks <a href="https://mastodon.social/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> supports.)

Felix Palmen :freebsd: :c64:Oh boy, I have a lead! And it's NOT related to <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLS</a>. I finally noticed another pattern: <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> only <a href="https://mastodon.bsd.cafe/tags/crashed" class="mention hashtag" rel="nofollow noopener" target="_blank">#crashed</a> when running as a <a href="https://mastodon.bsd.cafe/tags/daemon" class="mention hashtag" rel="nofollow noopener" target="_blank">#daemon</a>. The daemonizing wasn't the problem, but the default logging configuration attached to it: "fake async", by letting a <a href="https://mastodon.bsd.cafe/tags/threadpool" class="mention hashtag" rel="nofollow noopener" target="_blank">#threadpool</a> 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 <a href="https://mastodon.bsd.cafe/tags/LibreSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreSSL</a> (and only rarely with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>), I mean, something going rogue in your address space can have the weirdest effects.

Nicola TuveriI’ve been elected to represent the Academic community in the OpenSSL’s Foundation BAC/TAC and Corporation TAC! 🎓🔐If you’re working in crypto, systems security, or FOSS research, join the conversation on the OpenSSL Communities Forum—especially the Academic community. Your input can shape OpenSSL’s roadmap.<a href="https://openssl-communities.org/d/4cn9aVQH/welcome-from-your-academic-representative-in-the-openssl-foundation-bac-tac-and-corporation-tacs" rel="nofollow noopener" translate="no" target="_blank">https://openssl-communities.org/d/4cn9aVQH/welcome-from-your-academic-representative-in-the-openssl-foundation-bac-tac-and-corporation-tacs</a><a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> <a href="https://floss.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://floss.social/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://floss.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> <a href="https://floss.social/tags/Academia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Academia</a> <a href="https://floss.social/tags/AcademicChatter" class="mention hashtag" rel="nofollow noopener" target="_blank">#AcademicChatter</a>

Felix Palmen :freebsd: :c64:I need help. First the question: On <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>, with all ports built with <a href="https://mastodon.bsd.cafe/tags/LibreSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreSSL</a>, can I somehow use the <a href="https://mastodon.bsd.cafe/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> <a href="https://mastodon.bsd.cafe/tags/thread" class="mention hashtag" rel="nofollow noopener" target="_blank">#thread</a> <a href="https://mastodon.bsd.cafe/tags/sanitizer" class="mention hashtag" rel="nofollow noopener" target="_blank">#sanitizer</a> on a binary actually using LibreSSL and get sane output?What I now observe debugging <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a>:- A version built with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> (from base) doesn't crash. At least I tried very hard, really stressing it with <a href="https://mastodon.bsd.cafe/tags/jmeter" class="mention hashtag" rel="nofollow noopener" target="_blank">#jmeter</a>, to no avail. Built with LibreSSL, it does crash. - Less relevant: the OpenSSL version also performs slightly better, but needs almost twice the RAM - The thread sanitizer finds nothing to complain when built with OpenSSL - It complains a lot with LibreSSL, but the reports look "fishy", e.g. it seems to intercept some OpenSSL API functions (like SHA384_Final) - It even complains when running with a single-thread event loop. - I use a single SSL_CTX per listening socket, creating SSL objects from it per connection ... also with multithreading; according to a few sources, this should be supported and safe. - I can't imagine doing that on a *single* thread could break with LibreSSL, I mean, this would make SSL_CTX pretty much pointless - I *could* imagine sharing the SSL_CTX with multiple threads to create their SSL objects from *might* not be safe with LibreSSL, but no idea how to verify as long as the thread sanitizer gives me "delusional" output 😳

PurpleJillybeans :PrideDisk::DuckDuckGo: <a href="https://kind.social/tags/DuckDuckFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#DuckDuckFedi</a> :Where could I find docs for historical versions of <a href="https://kind.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>? I'm trying to set up a CA for <a href="https://kind.social/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a> machines with OpenSSL 0.9.6b, but the little bit of documentation that came with it isn't telling me much. Basically need to create a CA certificate I can put on client machines so that they won't complain about self-signed certs.

daniel:// stenberg://"download time is reduced by ~13%" (for <a href="https://mastodon.social/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a>)... by adding some odd <a href="https://mastodon.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> functions we didn't know existed.<a href="https://github.com/curl/curl/pull/17548" rel="nofollow noopener" translate="no" target="_blank">https://github.com/curl/curl/pull/17548</a>

Recent searches

Search options

Administered by:

Server stats:

#openssl