MastodonTech.de

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.

Timo J<a href="https://rattodon.nexus/@rolenthedeep" class="u-url mention" rel="nofollow noopener" target="_blank">@rolenthedeep</a> I guess I’m in the 1% who doesn’t care what <a href="https://mastodon.online/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> does from a UX perspective but would prefer it did a better job keeping <a href="https://mastodon.online/tags/libcurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#libcurl</a>, <a href="https://mastodon.online/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a>, and other core libraries up to date.

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

ClemensImproving the world, one PR at a time: <a href="https://github.com/smallstep/crypto/pull/811" rel="nofollow noopener" translate="no" target="_blank">https://github.com/smallstep/crypto/pull/811</a>The next release of <a href="https://chaos.social/tags/smallstep" class="mention hashtag" rel="nofollow noopener" target="_blank">#smallstep</a> step-ca will accept the old name "nonRepudiation" in the X.509v3 keyUsage extension as a UX improvement for users coming from, e.g., <a href="https://chaos.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a>.Inspired by <a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@jwildeboer</a>: <a href="https://social.wildeboer.net/@jwildeboer/114964280013823176" rel="nofollow noopener" translate="no" target="_blank">https://social.wildeboer.net/@jwildeboer/114964280013823176</a> This stuff is hard enough without such pitfalls, no need to make it more complicated by green bikesheds, er, naming discussions.<a href="https://chaos.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a>

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!

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.)

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>

Nicola Tuveri<a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> 📢 -- OpenSSL Foundation is hiring Software Engineer (C Developer)🔗 <a href="https://openssl-library.org/post/2025-06-19-foundation-sw-engineer/?utm_source=atom_feed" rel="nofollow noopener" translate="no" target="_blank">https://openssl-library.org/post/2025-06-19-foundation-sw-engineer/?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 Library

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 😳

LibreQoSShort stop at <a href="https://fosstodon.org/@devconf_cz" class="u-url mention" rel="nofollow noopener" target="_blank">@devconf_cz</a> 2025! Always great to meet <a href="https://social.kernel.org/users/toke" class="u-url mention" rel="nofollow noopener" target="_blank">@toke</a> of <a href="https://fosstodon.org/tags/FQ_CoDel" class="mention hashtag" rel="nofollow noopener" target="_blank">#FQ_CoDel</a> (<a href="https://fosstodon.org/tags/RFC8290" class="mention hashtag" rel="nofollow noopener" target="_blank">#RFC8290</a>) & <a href="https://fosstodon.org/tags/sch_CAKE" class="mention hashtag" rel="nofollow noopener" target="_blank">#sch_CAKE</a> fame 🙏🛜Check out his talk “Beware of the <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> RTNL <a href="https://fosstodon.org/tags/mutex" class="mention hashtag" rel="nofollow noopener" target="_blank">#mutex</a>”:<a href="https://pretalx.devconf.info/devconf-cz-2025/talk/WQDUDJ/" rel="nofollow noopener" translate="no" target="_blank">https://pretalx.devconf.info/devconf-cz-2025/talk/WQDUDJ/</a><a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/defineFUTURE" class="mention hashtag" rel="nofollow noopener" target="_blank">#defineFUTURE</a> <a href="https://fosstodon.org/tags/latency" class="mention hashtag" rel="nofollow noopener" target="_blank">#latency</a> <a href="https://fosstodon.org/tags/devconf_cz" class="mention hashtag" rel="nofollow noopener" target="_blank">#devconf_cz</a> <a href="https://fosstodon.org/tags/LibreQoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreQoS</a> <a href="https://fosstodon.org/tags/bufferbloat" class="mention hashtag" rel="nofollow noopener" target="_blank">#bufferbloat</a> <a href="https://fosstodon.org/tags/QoE" class="mention hashtag" rel="nofollow noopener" target="_blank">#QoE</a> <a href="https://fosstodon.org/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://fosstodon.org/tags/jitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#jitter</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a> <a href="https://fosstodon.org/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> <a href="https://fosstodon.org/tags/DevConf" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevConf</a> <a href="https://fosstodon.org/tags/TokeHoilandJorgensen" class="mention hashtag" rel="nofollow noopener" target="_blank">#TokeHoilandJorgensen</a> <a href="https://fosstodon.org/tags/QoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#QoS</a>

Hacker NewsApps shouldn't let users enter OpenSSL cipher-suite strings<a href="https://00f.net/2025/06/06/cipher-suites/" rel="nofollow noopener" translate="no" target="_blank">https://00f.net/2025/06/06/cipher-suites/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apps</a> <a href="https://mastodon.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> <a href="https://mastodon.social/tags/cipher" class="mention hashtag" rel="nofollow noopener" target="_blank">#cipher</a>-suites <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://mastodon.social/tags/bestpractices" class="mention hashtag" rel="nofollow noopener" target="_blank">#bestpractices</a> <a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwaredevelopment</a>

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>

Felix Palmen :freebsd: :c64:More interesting progress trying to make <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a> suitable for very busy sites!I realized that <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#TLS</a> (both with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> and <a href="https://mastodon.bsd.cafe/tags/LibreSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreSSL</a>) is a *major* bottleneck. With TLS enabled, I couldn't cross 3000 requests per second, with somewhat acceptable response times (most below 500ms). Disabling TLS, I could really see the impact of a <a href="https://mastodon.bsd.cafe/tags/lockfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#lockfree</a> queue as opposed to one protected by a <a href="https://mastodon.bsd.cafe/tags/mutex" class="mention hashtag" rel="nofollow noopener" target="_blank">#mutex</a>. With the mutex, up to around 8000 req/s could be reached on the same hardware. And with a lockfree design, that quickly went beyond 10k req/s, but crashed. 😆So I read some scientific papers 🙈 ... and redesigned a lot (*). And now it finally seems to work. My latest test reached a throughput of almost 25k req/s, with response times below 10ms for most requests! I really didn't expect to see *this* happen. 🤩 Maybe it could do even more, didn't try yet.Open issue: Can I do something about TLS? There *must* be some way to make it perform at least a *bit* better...(*) edit: Here's the design I finally used, with a much simplified "dequeue" because the queues in question are guaranteed to have only a single consumer: <a href="https://dl.acm.org/doi/10.1145/248052.248106" rel="nofollow noopener" translate="no" target="_blank">https://dl.acm.org/doi/10.1145/248052.248106</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#openssl