silentmode/site
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

site: Ariadne Resolver 0.1.6 — manifest and releases page

Browse source
This commit is contained in:
Local Dev 2026-09-27 23:47:47 +02:00
parent 2af402fff6
commit 55383430ef
2 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
releases-manifest.json
View file

@ -22,14 +22,14 @@
{
"id": "ariadne-resolver",
"product": "Ariadne Resolver (Windows)",
"version": "0.1.5",
"version": "0.1.6",
"date": "2026-09-27",
"platform": "win-x64",
"signed": false,
"signingAuthority": null,
"changes": "Other browsers open .x and every other live BNS TLD again. The installer took its TLD list from the legacy tlds.bch record (nine TLDs) while the registry had moved to per-TLD ownership with twenty, and the daemon read its certificate allow-list from a bundled config rather than the CA it had just minted, so only .bch, .p2p, .deviant and .nav actually worked outside Theseus. 0.1.5 routes and certifies every TLD on the public registry listing (asm, bch, bit, cex, coin, dea, dex, hub, nav, neo, nt, os, p2p, sia, test, vpn, x, deviant, dgb, lm), leaves ICANN-delegated collision TLDs (.cash, .gt, .sc, .sm) to the normal resolver so the local CA never covers a real internet TLD, and the daemon now takes its allow-list from the installed root CA itself. The root CA is regenerated on upgrade: restart Firefox once after installing. Upgrades in place.",
"changes": "New TLDs reach other browsers without a reinstall. The resolver daemon now keeps the routing rules and the local root certificate in step with the BNS registry on its own: 90 seconds after start and every six hours it fetches the registry's routable TLDs, adds the routing rules that are missing and drops the ones that no longer apply, and when the certified set has actually changed it rotates the root certificate, trusts the new one in the Windows store and removes the old one. A rotation is rare (only when a TLD appears or disappears) and is logged; Firefox reads trusted roots at startup, so restart it once after a rotation. Includes 0.1.5 (every live registry TLD routed and certified, collision TLDs left to ICANN, daemon allow-list taken from the installed root). Upgrades in place.",
"files": {
"AriadneResolver-Setup-0.1.5.exe": "b73a21207df81dc09bf6ff6898d00be30335a3b6a7fa9b3db4f2d4e8371d626b"
"AriadneResolver-Setup-0.1.6.exe": "e7fbe35d6e2c72e4a25db636502b7b5a2df1cf32039f7e1649154b40601a7865"
}
},
{

8
releases/index.html
View file

@ -72,12 +72,12 @@
</div>
<div class="rel">
<h2>Ariadne Resolver — Windows <span style="color:var(--acid)">0.1.5</span></h2>
<div class="meta">Windows 64-bit · unsigned · bundled Node runtime · 2026-09-27 · <b>0.1.5 — every live BNS TLD reaches other browsers again</b> — Other browsers open .x and every other live BNS TLD again. The installer took its TLD list from the legacy tlds.bch record (nine TLDs) while the registry had moved to per-TLD ownership with twenty, and the daemon read its certificate allow-list from a bundled config rather than the CA it had just minted, so only .bch, .p2p, .deviant and .nav actually worked outside Theseus. 0.1.5 routes and certifies every TLD on the public registry listing (asm, bch, bit, cex, coin, dea, dex, hub, nav, neo, nt, os, p2p, sia, test, vpn, x, deviant, dgb, lm), leaves ICANN-delegated collision TLDs (.cash, .gt, .sc, .sm) to the normal resolver so the local CA never covers a real internet TLD, and the daemon now takes its allow-list from the installed root CA itself. The root CA is regenerated on upgrade: restart Firefox once after installing. Upgrades in place.</div>
<h2>Ariadne Resolver — Windows <span style="color:var(--acid)">0.1.6</span></h2>
<div class="meta">Windows 64-bit · unsigned · bundled Node runtime · 2026-09-27 · <b>0.1.6 — new TLDs work without a reinstall</b> — New TLDs reach other browsers without a reinstall. The resolver daemon now keeps the routing rules and the local root certificate in step with the BNS registry on its own: 90 seconds after start and every six hours it fetches the registry's routable TLDs, adds the routing rules that are missing and drops the ones that no longer apply, and when the certified set has actually changed it rotates the root certificate, trusts the new one in the Windows store and removes the old one. A rotation is rare (only when a TLD appears or disappears) and is logged; Firefox reads trusted roots at startup, so restart it once after a rotation. Includes 0.1.5 (every live registry TLD routed and certified, collision TLDs left to ICANN, daemon allow-list taken from the installed root). Upgrades in place.</div>
<div class="file">
<div class="n"><a href="https://dl.silentmode.st/AriadneResolver-Setup-0.1.5.exe">AriadneResolver-Setup-0.1.5.exe</a> — ~24 MB</div>
<code>b73a21207df81dc09bf6ff6898d00be30335a3b6a7fa9b3db4f2d4e8371d626b</code>
<div class="n"><a href="https://dl.silentmode.st/AriadneResolver-Setup-0.1.6.exe">AriadneResolver-Setup-0.1.6.exe</a> — ~24 MB</div>
<code>e7fbe35d6e2c72e4a25db636502b7b5a2df1cf32039f7e1649154b40601a7865</code>
</div>
</div>