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
6 changes: 3 additions & 3 deletions docs/run-a-node/local-https.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,11 @@ Because the endpoint lives entirely on your machine's loopback, using it needs a
- **The same content, the same routes.** `https://dig.local` serves exactly what the plain-`http` endpoint does — the store content, the health check, and verification — so nothing about how you use your node changes.
- **A trusted padlock, no warnings.** Once the certificate is trusted, the browser treats `https://dig.local` like any other secure site — no scary certificate warning to click through.

## On Windows, the installer trusts it for you
## The installer provisions local HTTPS trust automatically

On Windows, the [DIG Installer](/docs/run-a-node/universal-installer) provisions the local certificate into the Windows trust store as part of installation, so your browsers trust `https://dig.local` automatically — there's nothing extra to do.
When you install the DIG node via the [DIG Installer](/docs/run-a-node/universal-installer), it automatically sets up the local HTTPS certificate trust on your operating system. On **Windows**, the installer provisions the local certificate into the Windows trust store as part of installation, so your browsers trust `https://dig.local` automatically — there's nothing extra to do. On **macOS and Linux**, the endpoint is served the same way, and browsers trust it once the local certificate has been provisioned; until then HTTPS is best-effort and clients simply read over plain `http` instead (see [the fallback](#fallback) below).

On macOS and Linux the endpoint is served the same way. Browsers trust it once the local certificate has been provisioned; until then HTTPS is best-effort and clients simply read over plain `http` instead (see [the fallback](#fallback) below).
The trust that the installer establishes is **name-constrained** — the local certificate authority can only vouch for `dig.local`, `*.dig`, and your machine's loopback addresses (`127.0.0.0/8` and `::1`). This name constraint is critical to security: even if the local CA's key were ever exposed, it could never be used to impersonate any website on the public internet — its authority is confined to your machine and DIG names only. When you uninstall the DIG node, the installer removes this trusted local CA from your operating system, so the trust is completely cleaned up.

## The certificate is short-lived and self-managing

Expand Down
2 changes: 1 addition & 1 deletion docs/run-a-node/universal-installer.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ dig-node open --json chia://<storeId>/

The installer registers **`dig.local`** for your machine so consumers on the same host resolve your node by name (`dig.local` → `localhost`) without hard-coding a port. This is what lets the [DIG Browser](../browser/chia-protocol.md) and extension prefer a local node automatically. → [Point a consumer at your node](./point-a-consumer.md)

On Windows the installer also trusts your node's local HTTPS certificate, so browsers reach it securely at `https://dig.local`. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)
The installer also automatically sets up local HTTPS trust: it provisions a name-constrained local certificate authority (restricted to `dig.local`, `*.dig`, and loopback only) that your browser trusts, so you can reach your node securely at `https://dig.local` with a valid certificate. Uninstalling the node removes this trusted CA cleanly. → [The `https://dig.local` endpoint](/docs/run-a-node/local-https)

## An always-on service, verified after install

Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "docs-dig-net",
"version": "0.11.3",
"version": "0.11.4",
"private": true,
"scripts": {
"docusaurus": "docusaurus",
Expand Down
Loading