ioc.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
INDICATORS OF COMPROMISE (IOC) InfoSec Community within the Fediverse. Newbies, experts, gurus - Everyone is Welcome! Instance is supposed to be fast and secure.

Administered by:

Server stats:

1.3K
active users

#tls

10 posts10 participants0 posts today
Jan Schaumann<p>At Akamai, we're launching a blog post series on various topics relating to post-quantum cryptography. The first post is by <span class="h-card" translate="no"><a href="https://ioc.exchange/@rsalz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>rsalz</span></a></span>, discussing some related IETF initiatives, including the two <a href="https://mstdn.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> drafts he co-authored:</p><p><a href="https://www.akamai.com/blog/trends/building-quantum-safe-internet-ietf-plan-tls" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">akamai.com/blog/trends/buildin</span><span class="invisible">g-quantum-safe-internet-ietf-plan-tls</span></a></p><p><a href="https://mstdn.social/tags/pqc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pqc</span></a></p>
📡 Flight Radar Mechelen 🇧🇪<p>Flight: <a href="https://mastodon.social/tags/BGA151G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGA151G</span></a><br>ICAO code: <a href="https://mastodon.social/tags/395D66" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>395D66</span></a><br>Callsign: <a href="https://mastodon.social/tags/BELOUGA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BELOUGA</span></a><br>Operator: Airbus Transport International<br>Country: 🇫🇷<br>From: <a href="https://mastodon.social/tags/BRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BRE</span></a> to <a href="https://mastodon.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a><br>Speed: 753 kmh<br>Altitude: 8534 m<br>Distance: 1.3 km<br>Angle ∆: 81.4°<br>Direction -&gt;: SSW<br>Track:<br><a href="https://tinyurl.com/28dm659g" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tinyurl.com/28dm659g</span><span class="invisible"></span></a><br>History:<br><a href="https://www.radarbox.com/data/mode-s/395D66" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">radarbox.com/data/mode-s/395D66</span><span class="invisible"></span></a><br>Seen: 18x<br><a href="https://mastodon.social/tags/Airbus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Airbus</span></a> <a href="https://mastodon.social/tags/BelugaXL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BelugaXL</span></a> <a href="https://mastodon.social/tags/A330" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>A330</span></a> <a href="https://mastodon.social/tags/Transport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Transport</span></a> <a href="https://mastodon.social/tags/RadarMechelen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RadarMechelen</span></a></p>
patpro<p>Hello, I’m hosting a <a href="https://social.patpro.net/tags/vaultwarden" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Vaultwarden</span></a> server behind <a href="https://social.patpro.net/tags/caddy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Caddy</span></a> 2.10 and made the following test:</p><p>Tuning Caddy to allow only <a href="https://social.patpro.net/tags/pqc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PQC</span></a> curves:</p><pre><code> tls { curves x25519mlkem768 } </code></pre><p>Trying to connect with <a href="https://social.patpro.net/tags/firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Firefox</span></a> Mac -&gt; OK<br>Trying to connect with <a href="https://social.patpro.net/tags/bitwarden" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Bitwarden</span></a> <a href="https://social.patpro.net/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>android</span></a> client -&gt; Fail</p><p>Without the <a href="https://social.patpro.net/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> tuning, the Bitwarden Android client will happily connect to the server.</p><p>Is it a problem with the Bitwarden Android client or with Android, or both?</p>
golangРазгоняем Go TLS до 100 Gbps с сервера: опыт Kinescope Современные пользователи ожидают, что видео загрузится мгновенн...<br><br><a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/golang" target="_blank">#golang</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/tls" target="_blank">#tls</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/шифрование" target="_blank">#шифрование</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/zero-copy" target="_blank">#zero-copy</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/хардкор" target="_blank">#хардкор</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/библиотеки" target="_blank">#библиотеки</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/handshake" target="_blank">#handshake</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/производительность" target="_blank">#производительность</a><br><br><a href="https://habr.com/ru/companies/oleg-bunin/articles/913272/?utm_source=habrahabr&amp;utm_medium=rss&amp;utm_campaign=913272" rel="nofollow noopener noreferrer" target="_blank">Origin</a> | <a href="https://awakari.com/sub-details.html?id=golang" rel="nofollow noopener noreferrer" target="_blank">Interest</a> | <a href="https://awakari.com/pub-msg.html?id=ORgxXgiNHQNtkFZns9fi3W7MBDk&amp;interestId=golang" rel="nofollow noopener noreferrer" target="_blank">Match</a>
Felix Palmen :freebsd: :c64:<p>Next <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>swad</span></a> release will still be a while. 😞 </p><p>I *thought* I had the version with multiple <a href="https://mastodon.bsd.cafe/tags/reactor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reactor</span></a> <a href="https://mastodon.bsd.cafe/tags/eventloop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>eventloop</span></a> threads and quite some <a href="https://mastodon.bsd.cafe/tags/lockfree" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>lockfree</span></a> stuff using <a href="https://mastodon.bsd.cafe/tags/atomics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>atomics</span></a> finally crash free. I found that, while <a href="https://mastodon.bsd.cafe/tags/valgrind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>valgrind</span></a> doesn't help much, <a href="https://mastodon.bsd.cafe/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>clang</span></a>'s <a href="https://mastodon.bsd.cafe/tags/thread" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>thread</span></a> <a href="https://mastodon.bsd.cafe/tags/sanitizer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sanitizer</span></a> is a very helpful debugging tool.</p><p>But I tested without <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> (to be able to handle "massive load" which seemed necessary to trigger some of the more obscure data races). Also without the credential checkers that use child processes. Now I deployed the current state to my prod environment ... and saw a crash there (only after running a load test).</p><p>So, back to debugging. I hope the difference is not <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a>. This just doesn't work (for whatever reason) when enabling the address sanitizer, but I didn't check the thread sanitizer yet...</p>
Hacker News<p>Why SSL was renamed to TLS in late 90s (2014)</p><p><a href="https://tim.dierks.org/2014/05/security-standards-and-name-changes-in.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tim.dierks.org/2014/05/securit</span><span class="invisible">y-standards-and-name-changes-in.html</span></a></p><p><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HackerNews</span></a> <a href="https://mastodon.social/tags/SSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSL</span></a> <a href="https://mastodon.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/history" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>history</span></a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://mastodon.social/tags/standards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>standards</span></a></p>
Conan the Sysadmin<p>Merely saying 'We speak a secret tongue' is not enough. One's wizards must speak the appropriate tongue, and speak it only in a most cautious fashion. <a href="https://mstdn.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://mstdn.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://cromwell-intl.com/cybersecurity/ssl-tls.html?s=mc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cromwell-intl.com/cybersecurit</span><span class="invisible">y/ssl-tls.html?s=mc</span></a></p>
Conan the Sysadmin<p>With the proper documents, any may pass and be trusted. <a href="https://mstdn.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mstdn.social/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LetsEncrypt</span></a> <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://cromwell-intl.com/open-source/letsencrypt-tls-cert-godaddy.html?s=mc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cromwell-intl.com/open-source/</span><span class="invisible">letsencrypt-tls-cert-godaddy.html?s=mc</span></a></p>
Dendrobatus Azureus<p>A recent research has exposed more than 40 * 10³ IoT cameras happily showing their feed _and_ location to anyone who can browse and use search engines specialized in the indexing of the misconfigured devices.</p><p>More than 14 * 10³ are localised in the USA.</p><p>Read more here.</p><p>Note: <br>I know that there are more than a million of these cameras world wide misconfigured an open on just port 80 http not even TLS 443, with admin / admin as credentials 🪪 </p><p><a href="https://www.theregister.com/2025/06/10/40000_iot_cameras_exposed/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/06/10/400</span><span class="invisible">00_iot_cameras_exposed/</span></a></p><p><a href="https://mastodon.bsd.cafe/tags/Infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Infosec</span></a> <a href="https://mastodon.bsd.cafe/tags/nightmare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nightmare</span></a> <a href="https://mastodon.bsd.cafe/tags/not" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>not</span></a> <a href="https://mastodon.bsd.cafe/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>news</span></a> <a href="https://mastodon.bsd.cafe/tags/IoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IoT</span></a> <a href="https://mastodon.bsd.cafe/tags/cameras" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cameras</span></a> <a href="https://mastodon.bsd.cafe/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://mastodon.bsd.cafe/tags/misconfigured" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>misconfigured</span></a> <a href="https://mastodon.bsd.cafe/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>streaming</span></a> <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mastodon.bsd.cafe/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTP</span></a></p>
Jan ☕🎼🎹☁️🏋️‍♂️<p>I came across this news post on b.root-servers.org that they're researching the activation of TLS on their root server. It's been running like that since 2023.</p><p>I wonder why not more root servers have this... Load issue?</p><p> <a href="https://b.root-servers.org/research/tls.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">b.root-servers.org/research/tl</span><span class="invisible">s.html</span></a></p><p><a href="https://fedi.kcore.org/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a> <a href="https://fedi.kcore.org/tags/rootserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rootserver</span></a> <a href="https://fedi.kcore.org/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tls</span></a></p>
dan_nanni<p>A secure HTTPS connection starts with an SSL/TLS handshake, during which the browser and the server verify each other’s identities, choose encryption protocols, and share cryptographic keys to create a protected communication channel</p><p>Here is how SSL/TLS handshake works step by step 😎👇 <a href="https://mastodon.social/tags/infoeec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infoeec</span></a> <a href="https://mastodon.social/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> <a href="https://mastodon.social/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tls</span></a> <a href="https://mastodon.social/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>encryption</span></a></p><p>Find high-res pdf books with all my <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> related infographics at <a href="https://study-notes.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">study-notes.org</span><span class="invisible"></span></a></p>
FirefoxGoogle Chrome to Distrust Chunghwa Telecom and Netlock Certificates from August 2025 Google Chrom...<br><br><br><a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/SSL" target="_blank">#SSL</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/Certificate" target="_blank">#Certificate</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/Distrust" target="_blank">#Distrust</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/SSL" target="_blank">#SSL</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/TLS" target="_blank">#TLS</a> <a rel="nofollow noopener noreferrer" class="mention hashtag" href="https://mastodon.social/tags/Certificates" target="_blank">#Certificates</a><br><a href="https://certera.com/blog/google-chrome-to-distrust-chunghwa-telecom-and-netlock-certificates/" rel="nofollow noopener noreferrer" target="_blank">Origin</a> | <a href="https://awakari.com/sub-details.html?id=Firefox" rel="nofollow noopener noreferrer" target="_blank">Interest</a> | <a href="https://awakari.com/pub-msg.html?id=Cbnf6qNGKRMMxdHta6eQKSYF5uq&amp;interestId=Firefox" rel="nofollow noopener noreferrer" target="_blank">Match</a>
Sebastian<p>I have a feeling that many people misunderstood the new <a href="https://social.karotte.org/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> Certificate requirements for browsers/public CAs… No, a public CA trusted by browsers doesn’t need to issue certificates with the Client Authentication EKU. Why would you trust a client that presents a certificate which was issued for server use anyway? <a href="https://social.karotte.org/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cryptography</span></a></p>
qbi<p>Nutzt du Client Authentication mit TLS-Zertifikaten?</p><p><a href="https://freie-re.de/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://freie-re.de/tags/letsencrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>letsencrypt</span></a> <a href="https://freie-re.de/tags/EKU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EKU</span></a> <a href="https://freie-re.de/tags/X509" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>X509</span></a></p>
Felix Palmen :freebsd: :c64:<p>More interesting progress trying to make <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>swad</span></a> suitable for very busy sites!</p><p>I realized that <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> (both with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSSL</span></a> and <a href="https://mastodon.bsd.cafe/tags/LibreSSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LibreSSL</span></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 noreferrer" target="_blank">#<span>lockfree</span></a> queue as opposed to one protected by a <a href="https://mastodon.bsd.cafe/tags/mutex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mutex</span></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. 😆</p><p>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.</p><p>Open issue: Can I do something about TLS? There *must* be some way to make it perform at least a *bit* better...</p><p>(*) 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 noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dl.acm.org/doi/10.1145/248052.</span><span class="invisible">248106</span></a></p>
Conan the Sysadmin<p>By consulting the proper documents, one may speak a secure and secret tongue. <a href="https://mstdn.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mstdn.social/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LetsEncrypt</span></a> <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://cromwell-intl.com/open-source/google-freebsd-tls/tls-certificate.html?s=mc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cromwell-intl.com/open-source/</span><span class="invisible">google-freebsd-tls/tls-certificate.html?s=mc</span></a></p>
Conan the Sysadmin<p>Learn the subtle battle language used in the realm of the clouds. <a href="https://mstdn.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mstdn.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeBSD</span></a> <a href="https://mstdn.social/tags/GoogleCloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GoogleCloud</span></a> <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a> <a href="https://cromwell-intl.com/open-source/google-freebsd-tls/https-headers.html?s=mc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cromwell-intl.com/open-source/</span><span class="invisible">google-freebsd-tls/https-headers.html?s=mc</span></a></p>
jesterchen42<p>Es gab doch mal diesen Vorstoß, daß Browser- unf Betriebssystemhersteller in der EU verpflichtet werden sollen, EU-CAs für <a href="https://social.tchncs.de/tags/x509" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>x509</span></a> als vetrauenswürdig aufzunehmen - was ja auch jeglicher <a href="https://social.tchncs.de/tags/Chatkontrolle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chatkontrolle</span></a> stark in die Hände spielte...</p><p>Gibt es dazu Neuerungen? Und wie hießen die nochmal? qwacs oder so?</p><p><a href="https://social.tchncs.de/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tls</span></a> <a href="https://social.tchncs.de/tags/ca" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ca</span></a></p>
Felix Palmen :freebsd: :c64:<p>Solved! 🥳 </p><p>This was a pretty "interesting" bug. Remember when I invented a way to implement <a href="https://mastodon.bsd.cafe/tags/async" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>async</span></a> / <a href="https://mastodon.bsd.cafe/tags/await" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>await</span></a> in <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>C</span></a>, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.</p><p>Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.</p><p>It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.</p><p>Only it didn't, at least here on <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeBSD</span></a>, and I finally understood the reason for this was that I was using <a href="https://mastodon.bsd.cafe/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> (thread-local storage) to find the context to restore.</p><p>Well, most architectures store a pointer to the current thread metadata in a register. <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>POSIX</span></a> user <a href="https://mastodon.bsd.cafe/tags/context" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>context</span></a> <a href="https://mastodon.bsd.cafe/tags/switching" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>switching</span></a> saves and restores registers. I found a source claiming that the <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> (<a href="https://mastodon.bsd.cafe/tags/glibc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>glibc</span></a>) implementation explicitly does NOT include the register holding a thread pointer. Obviously, <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeBSD</span></a>'s implementation DOES include it. POSIX doesn't have to say anything about that.</p><p>In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯</p>
Pyrzout :vm:<p>Chrome to Distrust Chunghwa Telecom and Netlock Certificates – Source: www.securityweek.com <a href="https://ciso2ciso.com/chrome-to-distrust-chunghwa-telecom-and-netlock-certificates-source-www-securityweek-com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ciso2ciso.com/chrome-to-distru</span><span class="invisible">st-chunghwa-telecom-and-netlock-certificates-source-www-securityweek-com/</span></a> <a href="https://social.skynetcloud.site/tags/rssfeedpostgeneratorecho" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rssfeedpostgeneratorecho</span></a> <a href="https://social.skynetcloud.site/tags/CyberSecurityNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurityNews</span></a> <a href="https://social.skynetcloud.site/tags/securityweekcom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securityweekcom</span></a> <a href="https://social.skynetcloud.site/tags/Dataprotection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Dataprotection</span></a> <a href="https://social.skynetcloud.site/tags/certificates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>certificates</span></a> <a href="https://social.skynetcloud.site/tags/securityweek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>securityweek</span></a> <a href="https://social.skynetcloud.site/tags/Chunghwa" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chunghwa</span></a> <a href="https://social.skynetcloud.site/tags/Netlock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Netlock</span></a> <a href="https://social.skynetcloud.site/tags/Chrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chrome</span></a> <a href="https://social.skynetcloud.site/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> <a href="https://social.skynetcloud.site/tags/remove" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>remove</span></a> <a href="https://social.skynetcloud.site/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://social.skynetcloud.site/tags/CA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CA</span></a></p>