https://hackingpassion.com/openssl-12-cves-ai-january-2026/
AI found 12 of 12 #OpenSSL #CVE's . CVE-2025-15467 is most remarkable
Fled from the birdsite to a separate account.
Toots mostly in EN about testssl.sh and related stuff.
https://hackingpassion.com/openssl-12-cves-ai-january-2026/
AI found 12 of 12 #OpenSSL #CVE's . CVE-2025-15467 is most remarkable
RE: https://mastodon.social/@drwetter/115827783533894665
Testssl activities had to wait a bit as the main contributor was busy ๐
testssl.sh 3.3dev update:
- shellcheck ensures better code quality when check in, thanks to MFTabriz
- flag --rating only does the bare minimum of checks for SSLlabs rating, thanks to magnuslarsen
Both branches had some CA stores update
testssl.sh 3.3dev now has (finally) early data support a.k.a 0-RTT .
Btw: the new server for testssl.sh also supports #QUIC and other nice smaller bells and whistles
Come on, guys . Not even a pcap file ?
@pu
See link
OpenSSL 3.6 Officially Released with LMS Signature Verification Support, More
Willing to help? See https://github.com/testssl/testssl.sh/issues/2908
I am curious whether Apple finally made a step toward #PQC to catch up with all other major browser vendors with the release of version 26 of their operating systems. They lag behind since months:
Just the command line for testing the next incarnation of my server (IPs aren't final, thus masked here)
Much appreciated, thanks!
Willing to help? See https://github.com/testssl/testssl.sh/issues/2908
I am curious whether Apple finally made a step toward #PQC to catch up with all other major browser vendors with the release of version 26 of their operating systems. They lag behind since months:
New release for the stable branch 3.2
... also for 3.2 now
testssl.sh now also has an FAQ: https://github.com/testssl/testssl.sh/blob/3.3dev/FAQ.md
Don't know whether anybody of you guys uses #Apple Mail but I'd rather be careful:
https://www.linkedin.com/feed/update/urn:li:activity:7349803754226868224/
TL;DR: UI prefers #STARTTLS over #TLS for #IMAP (but actually for some reason uses both ports). Apple Product Security doesn't see a reason for immediate action.
My bottom line: a) Apple doesn't take security as relevant as they say b) there are probably lots of users like I was who have STARTTLS configured and don't know that.
I recommend to check whether you're affected. If so I'd configure that as recommended above and change your passwords.
testssl.sh 3.3dev got a bit snappier, most notably for Macs:
PR for always scanning #IPv6 ๐๐ผmerged.
In addition there's a small&nice hint: If there's no IPv6 activity you get a hint "scanning all IPv4 addresses". And the listed IPv6 addresses appear in round brackets.
Man pages / docs were updated accordingly
#IPv6 PR incoming to automagically check also IPv6: