Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,16 @@ npx moshpit-pin scrambled.eggs:443 # from what a live server presents
refuses the name — there is no TOFU and no unauthenticated mode, because the pin
stands exactly where a certificate authority would.

Publish the result at [app.moshcode.sh/pit/dns](https://app.moshcode.sh/pit/dns).
Publish the result at [app.moshcode.sh/pit](https://app.moshcode.sh/pit) — sign
in, open the **Yours** tab, and use **Key pins** on the TLD.

Not `/pit/dns`, which this file used to say. That page is the instructions for
pointing a *machine's resolver* at Moshpit — it has no pin form on it, so the
old link sent operators somewhere they could never finish the job.

The same page is where a name's **points at** target lives, which is the other
half of making a name reachable.

Keep the previous pin listed alongside the new one while rotating — the client
accepts any pin in the list, so a key can change without a flag day.

Expand Down
3 changes: 2 additions & 1 deletion scripts/setup-origin.sh
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,8 @@ cat >&2 <<EOF
${BOLD}$NAME${OFF}
$PIN

Publish it at https://app.moshcode.sh/pit/dns
Publish it at https://app.moshcode.sh/pit
${DIM}sign in · the "Yours" tab · "Key pins" on .${NAME#*.}${OFF}

Until you do, every client refuses this name — that is the design, not a
fault. There is no trust-on-first-use and no unauthenticated mode, because
Expand Down
Loading