mastodon.ie

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.

Christoff, the humanDecided to not use <a href="https://oldbytes.space/tags/libev" class="mention hashtag" rel="nofollow noopener" target="_blank">#libev</a> and use <a href="https://oldbytes.space/tags/libevent" class="mention hashtag" rel="nofollow noopener" target="_blank">#libevent</a> instead for socket/timer/event loop/callback system. Other than I trust it more, I like the baked in <a href="https://oldbytes.space/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a> support (will use for <a href="https://oldbytes.space/tags/telnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#telnet</a>+tls later).Additionally, going to try out sqlcipher (<a href="https://oldbytes.space/tags/sqlite3" class="mention hashtag" rel="nofollow noopener" target="_blank">#sqlite3</a> + AES encryption baked in) for data storage. Everything will be stored in a sqlite3 database.Using cmake and pkg-config, <a href="https://oldbytes.space/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#C</a>, 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.<a href="https://oldbytes.space/tags/BBS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BBS</a> <a href="https://oldbytes.space/tags/NecroNeonBBS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NecroNeonBBS</a> <a href="https://oldbytes.space/tags/Vaporware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vaporware</a>

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

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>

Kushal Das :python: :tor:I wrote about <a href="https://toots.dgplug.org/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a> <a href="https://toots.dgplug.org/tags/jdk21" class="mention hashtag" rel="nofollow noopener" target="_blank">#jdk21</a> and <a href="https://toots.dgplug.org/tags/pkcs12" class="mention hashtag" rel="nofollow noopener" target="_blank">#pkcs12</a> <a href="https://toots.dgplug.org/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> <a href="https://toots.dgplug.org/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://toots.dgplug.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> <a href="https://kushaldas.in/posts/openssl-legacy-and-jdk-21.html" rel="nofollow noopener" translate="no" target="_blank">https://kushaldas.in/posts/openssl-legacy-and-jdk-21.html</a> <a href="https://toots.dgplug.org/tags/java" class="mention hashtag" rel="nofollow noopener" target="_blank">#java</a>

openSUSE LinuxMay’s <a href="https://fosstodon.org/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tumbleweed</a> update rolled out <a href="https://fosstodon.org/tags/QEMU" class="mention hashtag" rel="nofollow noopener" target="_blank">#QEMU</a> 10.0 for improved virtualization 🖥️⚡ and <a href="https://fosstodon.org/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> 3.5.0 with post-<a href="https://fosstodon.org/tags/quantum" class="mention hashtag" rel="nofollow noopener" target="_blank">#quantum</a> <a href="https://fosstodon.org/tags/crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#crypto</a> 💡Security got serious with <a href="https://fosstodon.org/tags/CVE" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE</a> fixes 🛡️ <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> <a href="https://news.opensuse.org/2025/06/02/tw-monthly-update-may/" rel="nofollow noopener" translate="no" target="_blank">https://news.opensuse.org/2025/06/02/tw-monthly-update-may/</a>

// foss.eventsNew on // foss.events: OpenSSL Conference on 07-09 October 2025 in Vienna House by Wyndham Diplomat Prague in <a href="https://fosstodon.org/tags/Prague" class="mention hashtag" rel="nofollow noopener" target="_blank">#Prague</a>, <a href="https://fosstodon.org/tags/Czech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Czech</a> Republic Find out more on <a href="https://foss.events/2025/10-07-openssl-conference.html" rel="nofollow noopener" translate="no" target="_blank">https://foss.events/2025/10-07-openssl-conference.html</a>Call for participation is running until 31.05.2025<a href="https://fosstodon.org/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://fosstodon.org/tags/floss" class="mention hashtag" rel="nofollow noopener" target="_blank">#floss</a> <a href="https://fosstodon.org/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://fosstodon.org/tags/events" class="mention hashtag" rel="nofollow noopener" target="_blank">#events</a> <a href="https://fosstodon.org/tags/europe" class="mention hashtag" rel="nofollow noopener" target="_blank">#europe</a> <a href="https://fosstodon.org/tags/openssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssl</a>

Nicola Tuveri<a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> 📢 -- The OpenSSL Corporation and the OpenSSL Foundation Launch Distinguished Contributor Awards with OpenSSL 3.5 Honorees🔗 <a href="https://openssl-corporation.org/post/2025-05-20-3.5-awards/?utm_source=atom_feed" rel="nofollow noopener" translate="no" target="_blank">https://openssl-corporation.org/post/2025-05-20-3.5-awards/?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 Corporation

pfriedmaJust got to play the game that appears to go 1. OpenSSL announced a low severity issue with NPN (cve2024-5535) 2. AI posts about this raise urgency, using language like "critical" 3. A few repos create untested and unverified "exploits" using AI on GitHub 4. Tenable picks up on 2,3 marks as critical with remotely exploitable RCE citing no actual sources (just an ouroboros of machine generated content linking to other machine generated content) 5. Non-vulnerable (AFAIK server code using ALPN) machine gets flagged and we have to do something because other machine told us to 😂 Maybe I'm severely mistaken but as far as I can tell this is really not something that should actually be critical?Right? <a class="hashtag" href="https://pfedi.pfriedma.org/tag/infosec" rel="nofollow noopener" target="_blank">#infoSec</a> <a class="hashtag" href="https://pfedi.pfriedma.org/tag/openssl" rel="nofollow noopener" target="_blank">#OpenSSL</a>

Jiří EischmannA presentation by <a href="https://infosec.exchange/@mold" class="u-url mention" rel="nofollow noopener" target="_blank">@mold</a> at <a href="https://social.vivaldi.net/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> and <a href="https://mastodon.social/@openalt" class="u-url mention" rel="nofollow noopener" target="_blank">@openalt</a> crossover in <a href="https://social.vivaldi.net/tags/Brno" class="mention hashtag" rel="nofollow noopener" target="_blank">#Brno</a>.

Felix Palmen :freebsd: :c64:Adding what was missing for intermediate certificates, I had great fun with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> <a href="https://mastodon.bsd.cafe/tags/API" class="mention hashtag" rel="nofollow noopener" target="_blank">#API</a> again. I mean, it never gets old. First test gave me a nice crash of <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#swad</a>. Because ....Well, to use a certificate (type X509 *), you call SSL_CTX_use_certificate(). Docs say "On success the reference counter of the x is incremented." (where x means the certificate). Great, so, call X509_free() directly afterwards to ensure this certificate gets destroyed whenever the SSL context gets destroyed.So, just call the same function again for the intermediate certificates? No ... but there's SSL_CTX_add_extra_chain_cert() which *can* be used multiple times. Nice, call it in a loop as long as I find additional certificates in the cert file, and X509_free() them all directly after adding.And then observe the crash. Well, it's documented, the manpage for SSL_CTX_add_extra_chain_cert() tells:"The x509 certificate provided to SSL_CTX_add_extra_chain_cert() will be freed by the library when the SSL_CTX is destroyed. An application should not free the x509 object."So, clearly my fault not reading this before. Consistency in API design is so overrated. 🤪

Nicola Tuveri<a href="https://floss.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> 📢 -- Call for speakers at the inaugural OpenSSL Conference🔗 <a href="https://openssl-foundation.org/post/2025-05-14-call-for-speakers/?utm_source=atom_feed" rel="nofollow noopener" translate="no" target="_blank">https://openssl-foundation.org/post/2025-05-14-call-for-speakers/?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

Andreas ScherbaumToday's random number is 17Why, you ask? It's 17 years since the <a href="https://mastodon.social/tags/Random" class="mention hashtag" rel="nofollow noopener" target="_blank">#Random</a> Number <a href="https://mastodon.social/tags/Bug" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bug</a> in <a href="https://mastodon.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>.In this bug the seed for the <a href="https://mastodon.social/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSSL</a> PRNG was very predictable, resulting as example in a very small number of <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> keys. Plenty of keys had to be re-generated.

Recent searches

Search options

Administered by:

Server stats:

#openssl