eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

217
active users

#tls

3 posts3 participants0 posts today
Aral Balkan<p>Introducing Web Numbers</p><p>Domains? Where we’re going, we don’t need domains!</p><p>Get ready for an exciting new (old?) way to address (small) web sites in 2026.</p><p><a href="https://ar.al/2025/06/25/web-numbers/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ar.al/2025/06/25/web-numbers/</span><span class="invisible"></span></a></p><p>💕</p><p>(Thanks to <span class="h-card" translate="no"><a href="https://infosec.exchange/@letsencrypt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>letsencrypt</span></a></span>.)</p><p><a href="https://mastodon.ar.al/tags/WebNumbers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebNumbers</span></a> <a href="https://mastodon.ar.al/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallWeb</span></a> <a href="https://mastodon.ar.al/tags/domainNames" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>domainNames</span></a> <a href="https://mastodon.ar.al/tags/IPAddresses" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPAddresses</span></a> <a href="https://mastodon.ar.al/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mastodon.ar.al/tags/HTTPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTPS</span></a> <a href="https://mastodon.ar.al/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LetsEncrypt</span></a> <a href="https://mastodon.ar.al/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a> <a href="https://mastodon.ar.al/tags/decentralisation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>decentralisation</span></a> <a href="https://mastodon.ar.al/tags/SmallTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallTech</span></a></p>
📡 Flight Radar Mechelen 🇧🇪<p>Flight: <a href="https://mastodon.social/tags/BGA151J" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGA151J</span></a><br>Registration: F-GXLJ<br>ICAO code: <a href="https://mastodon.social/tags/395D69" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>395D69</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>Type: A330 743L<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: 688 kmh<br>Altitude: 9144 m<br>Distance: 4.5 km<br>Angle ∆: 63.8°<br>Direction -&gt;: SSW<br>Track:<br><a href="https://tinyurl.com/235bgxzq" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tinyurl.com/235bgxzq</span><span class="invisible"></span></a><br>History:<br><a href="https://www.radarbox.com/data/mode-s/395D69" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">radarbox.com/data/mode-s/395D69</span><span class="invisible"></span></a><br><a href="https://www.flightradar24.com/data/aircraft/F-GXLJ" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">flightradar24.com/data/aircraf</span><span class="invisible">t/F-GXLJ</span></a><br>Photos:<br><a href="https://jetphotos.com/photo/keyword/F-GXLJ" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jetphotos.com/photo/keyword/F-</span><span class="invisible">GXLJ</span></a><br>Seen: 23x<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>
Felix Palmen :freebsd: :c64:<p>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 noreferrer" target="_blank">#<span>TLS</span></a>. I finally noticed another pattern: <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>swad</span></a> only <a href="https://mastodon.bsd.cafe/tags/crashed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>crashed</span></a> when running as a <a href="https://mastodon.bsd.cafe/tags/daemon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>daemon</span></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 noreferrer" target="_blank">#<span>threadpool</span></a> job do the logging.</p><p>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 noreferrer" target="_blank">#<span>LibreSSL</span></a> (and only rarely with <a href="https://mastodon.bsd.cafe/tags/OpenSSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSSL</span></a>), I mean, something going rogue in your address space can have the weirdest effects.</p>
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>
Gytis Repečka<p>Running e-mail servers is always fun: as the time came to renew TLS certificate on one machine doing e-mail transmission (SMTP), came to know <code>TLSA</code> records are now supposed to be <code>3 1 1</code> (no more <code>3 0 1</code>) :blobcateyes:</p><p>There is an added benefit of <code>3</code> (<code>DANE-EE</code>) <code>1</code> (subject public key) <code>1</code> (SHA2-256 hash digest) - if you do not rotate your private key to issue TLS certificate, you don't need to update the <code>TLSA</code> record - signature can be squeezed from key and certificate is not necessary at that point. If you do rotate private keys, this enables you to <a href="https://mail.sys4.de/pipermail/dane-users/2018-February/000440.html" rel="nofollow noopener noreferrer" target="_blank">pre-create DNS records</a> even before certificate is issued (given that you already generated keys) - that is really nice :blobcatthumbsup:</p><p><a href="https://social.gyt.is/tags/serveradmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>serveradmin</span></a> <a href="https://social.gyt.is/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://social.gyt.is/tags/dane" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dane</span></a> <a href="https://social.gyt.is/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a> <a href="https://social.gyt.is/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tls</span></a> <a href="https://social.gyt.is/tags/certificate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>certificate</span></a> <a href="https://social.gyt.is/tags/sha256" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sha256</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>
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>
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>
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>
Sebastian Abshoff<p>Come on SAP, it's 2025 - expired certificates in production should be a thing of the past! Let's not break trust with something so basic. <a href="https://abshoff.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a> <a href="https://abshoff.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://abshoff.social/tags/SAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SAP</span></a> <a href="https://abshoff.social/tags/Fieldglass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fieldglass</span></a></p>
DrScriptt<p>After having decided the <a href="https://oldbytes.space/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> certificate, I’m much more sure that ASN.1 is simply encoding / serializing pieces of information.</p><p>Similarly, DER, BER, etc specify what is encoded in what order and using what ASN.1 types for things.</p><p>Said another way, ASN.1 is how to do something and DER is what to do it to.</p><p>Sort of a policies vs procedure type thing.</p><p><a href="https://oldbytes.space/tags/ASN1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASN1</span></a></p>
DrScriptt<p>I managed to finish decoding the ASN.1 of my servers <a href="https://oldbytes.space/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> certificate this evening.</p><p>I did have a few identifiers that stumped me. But I continued decoding as if they used the same type / length / value format as most other identifiers and they worked.</p><p>After the fact I found some documentation confirming that I decided the identifiers correctly.</p><p>Now I need to decode all of the OIDs and make sure that I have them correct and that I have them in my .oid <a href="https://oldbytes.space/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> zone.</p><p><a href="https://oldbytes.space/tags/ASN1" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASN1</span></a> <a href="https://oldbytes.space/tags/OID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OID</span></a></p>
screwlisp<p><a href="https://gamerplus.org/tags/commonLisp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>commonLisp</span></a> <a href="https://gamerplus.org/tags/emacs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>emacs</span></a> <a href="https://gamerplus.org/tags/smallweb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>smallweb</span></a> <a href="https://gamerplus.org/tags/kitten" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kitten</span></a> <a href="https://screwlisp.small-web.org/kitten/clkitten-parenscript-kitten-2/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">screwlisp.small-web.org/kitten</span><span class="invisible">/clkitten-parenscript-kitten-2/</span></a> <a href="https://gamerplus.org/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a></p><p>Eev (and lisp secret alien technology) made it /really/ easy and convenient to generate a kitten matching <span class="h-card" translate="no"><a href="https://mastodon.ar.al/@aral" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>aral</span></a></span>'s Tutorial 2: dynamic pages, <a href="https://kitten.small-web.org/tutorials/dynamic-pages/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">kitten.small-web.org/tutorials</span><span class="invisible">/dynamic-pages/</span></a> serve it and visit it inside emacs (just press F8 over and over again and it happens on its own).</p><p>I guess you can do it too...? What do you think? How much of a Hurkle itch is this giving you Aral ;p. It seems /really/ easy to get a fancy! <a href="https://gamerplus.org/tags/tls" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tls</span></a> site up like this.</p>
Aral Balkan<p>🔒 Auto Encrypt – heads up!</p><p>In the next minor version release of Auto Encrypt¹, we’ll be moving from a hard-coded date-based certificate renewal check to using ACME Renewal Information (ARI)².</p><p>The change³ should be seamless.</p><p>If you have any concerns, now is the time to raise them :)</p><p><a href="https://mastodon.ar.al/tags/AutoEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AutoEncrypt</span></a> <a href="https://mastodon.ar.al/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://mastodon.ar.al/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LetsEncrypt</span></a> <a href="https://mastodon.ar.al/tags/SmallTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallTech</span></a> <a href="https://mastodon.ar.al/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallWeb</span></a></p><p>¹ Drop-in Node.js https server replacement that automatically provisions and renews Let’s Encrypt certificates for you. (<a href="https://codeberg.org/small-tech/auto-encrypt#auto-encrypt" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/small-tech/auto-e</span><span class="invisible">ncrypt#auto-encrypt</span></a>)<br>² <a href="https://datatracker.ietf.org/doc/draft-ietf-acme-ari/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/draft</span><span class="invisible">-ietf-acme-ari/</span></a><br>³ <a href="https://codeberg.org/small-tech/auto-encrypt/src/branch/main/CHANGELOG.md#4-4-0-2025" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/small-tech/auto-e</span><span class="invisible">ncrypt/src/branch/main/CHANGELOG.md#4-4-0-2025</span></a></p>
Aral Balkan<p>👋🤓 Goodbye Site.js, Hello Kitten!</p><p>I started working on creating a Small Web¹ server (a peer-to-peer Web server) six years ago² with Site.js.</p><p>Building Site.js was my first attempt. And it resulted in:</p><p>• Auto Encrypt (automatic Let’s Encrypt certificates): <a href="https://codeberg.org/small-tech/auto-encrypt" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/small-tech/auto-e</span><span class="invisible">ncrypt</span></a></p><p>• Auto Encrypt Localhost (automatic localhost TLS certificates): <a href="https://codeberg.org/small-tech/auto-encrypt-localhost" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/small-tech/auto-e</span><span class="invisible">ncrypt-localhost</span></a></p><p>• @small-tech/https (drop-in Node.js https module replacement with automatic TLS certs everywhere): <a href="https://codeberg.org/small-tech/https" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">codeberg.org/small-tech/https</span><span class="invisible"></span></a></p><p>• JSDB: In-process, in-memory JavaScript database that persists to append-only JavaScript logs: <a href="https://codeberg.org/small-tech/jsdb" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">codeberg.org/small-tech/jsdb</span><span class="invisible"></span></a></p><p>As Site.js reached an evolutionary dead-end, and as I learned from my experiements with replicated data types that replicated data types are *not* a prerequisite for a decentralised web (actual topological decentralisation and ease of use are), I started writing a new server/platform called Kitten from scratch while still making use of the tried and tested modules listed above.</p><p>Last week, I switched over our last site using Site.js to Kitten and, with that, today I’ve sunset³ Site.js:</p><p><a href="https://sitejs.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">sitejs.org</span><span class="invisible"></span></a></p><p>For its successor, please see Kitten:</p><p><a href="https://kitten.small-web.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">kitten.small-web.org</span><span class="invisible"></span></a></p><p>If you want to support our work at the Small Technology Foundation, please consider becoming a patron:</p><p><a href="https://small-tech.org/fund-us" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">small-tech.org/fund-us</span><span class="invisible"></span></a></p><p>:kitten:💕</p><p>¹ <a href="https://ar.al/2024/06/24/small-web-computer-science-colloquium-at-university-of-groningen/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ar.al/2024/06/24/small-web-com</span><span class="invisible">puter-science-colloquium-at-university-of-groningen/</span></a><br>² <a href="https://ar.al/2019/08/26/introducing-small-technology-foundation/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ar.al/2019/08/26/introducing-s</span><span class="invisible">mall-technology-foundation/</span></a><br>³ Using our instance of Look Over There!: <a href="https://look-over-there.small-web.org" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">look-over-there.small-web.org</span><span class="invisible"></span></a></p><p><a href="https://mastodon.ar.al/tags/SiteJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SiteJS</span></a> <a href="https://mastodon.ar.al/tags/SmallWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallWeb</span></a> <a href="https://mastodon.ar.al/tags/SmallTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallTech</span></a> <a href="https://mastodon.ar.al/tags/peerToPeerWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>peerToPeerWeb</span></a> <a href="https://mastodon.ar.al/tags/SmallTechnologyFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SmallTechnologyFoundation</span></a> <a href="https://mastodon.ar.al/tags/AutoEncrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AutoEncrypt</span></a> <a href="https://mastodon.ar.al/tags/AutoEncryptLocalhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AutoEncryptLocalhost</span></a> <a href="https://mastodon.ar.al/tags/JSDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JSDB</span></a> <a href="https://mastodon.ar.al/tags/JavaScriptDatabase" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JavaScriptDatabase</span></a> <a href="https://mastodon.ar.al/tags/https" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>https</span></a> <a href="https://mastodon.ar.al/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a></p>
📡 Flight Radar Mechelen 🇧🇪<p>Flight: <a href="https://mastodon.social/tags/BGA113Y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGA113Y</span></a><br>Registration: F-GXLI<br>ICAO code: <a href="https://mastodon.social/tags/395D68" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>395D68</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>Type: AIRBUS A330 743L<br>Country: 🇫🇷<br>From: <a href="https://mastodon.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> to <a href="https://mastodon.social/tags/XFW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XFW</span></a><br>Speed: 710 kmh<br>Altitude: 9449 m<br>Distance: 7.6 km<br>Angle ∆: 51.3°<br>Direction -&gt;: NE<br>Track:<br><a href="https://tinyurl.com/22qfxke2" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tinyurl.com/22qfxke2</span><span class="invisible"></span></a><br>History:<br><a href="https://www.radarbox.com/data/mode-s/395D68" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">radarbox.com/data/mode-s/395D68</span><span class="invisible"></span></a><br><a href="https://www.flightradar24.com/data/aircraft/F-GXLI" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">flightradar24.com/data/aircraf</span><span class="invisible">t/F-GXLI</span></a><br>Photos:<br><a href="https://jetphotos.com/photo/keyword/F-GXLI" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jetphotos.com/photo/keyword/F-</span><span class="invisible">GXLI</span></a><br>Seen: 25x<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>
Trusty<p>🔐 How can you keep your online data safe? <br>Whether you’re a web developer, IT professional, or simply interested in online security, our YouTube video will give you the confidence and know-how to secure your online presence using TLS SAN Certificates.<br>Discover how Subject Alternative Name (SAN) extensions make it possible to encrypt multiple domain names with just one TLS certificate.</p><p><a href="https://dnsimple.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> <a href="https://dnsimple.social/tags/SAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SAN</span></a></p><p>visit: <a href="https://youtu.be/R5jdnZyusew" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/R5jdnZyusew</span><span class="invisible"></span></a> for more details.</p>