chore(release): v0.20.0 - #283
Merged
Merged
Conversation
A Moshpit name now survives the TLS handshake without a per-name detour. `dns trust <name>` installs the leaf a name serves, but only when its key matches a pin the registry already published, and `dns start --trust-all` does that as names resolve (#279, #281). Minor, not patch: two new ways to invoke the tool. Also carries two commands that used to report success they had not earned -- `update --timer --install` when systemctl refused (#282), and `site --proxy` with a port outside 1-65535 (#280). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreatCrush Security Scan88 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 38
…and 38 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
package.jsonto0.20.0. No other file changes.Minor rather than patch: #279/#281 add two new ways to invoke the tool (
dns trust <name>anddns start --trust-all), which is more than a fix.What ships
dns trust <name>and--trust-all(#279, #281) — the certificate error that survived #275. The local root installed there signs nothing, because nothing routes to the proxy that would re-sign: the resolver answers the origin and the proxy sits on loopback, unconnected. Trusting the leaf a name serves closes that without the proxy at all, and the pin check is what keeps it defensible — the leaf is installed only when its key matches one the registry already published for that name.--trust-alldoes the same as names resolve, so browsing does not mean a command per site.update --timer --installreports a refused timer (#282) — it wrote the units, ransystemctl enable --now, then printed "checking on a schedule now" and exited 0 whether or not the enable worked. On a host without systemd or without root the timer never started and the tool still promised auto-updates.site --proxyrejects an impossible port (#280) —^\d+$accepted0(falsy downstream, so the site silently fell back to a static root) and99999(wrote aproxy_passto a port that cannot exist). Both exited 0 and called the site live.Release
On merge: tag
v0.20.0and publish notes.selfupdatereads the latest release, so nothing above reachesmoshcode updateuntil that tag exists.🤖 Generated with Claude Code