Repository navigation
Conversation
A `tls:<port>` check dials the target through netEnv, completes a TLS handshake and fails when the leaf certificate expires within 7 days or is not yet valid. Nothing was watching certificate expiry before, and `tls:` was rejected at load time. The verified name is the DNS name of the peer that owns the address, taken from the live peer view and then the status cache, so a Tailscale IP, a short name and a full `*.ts.net` name all verify against the certificate Tailscale issued. A subnet route never supplies the name. `insecure_tls` skips chain and name verification but still enforces the leaf dates, so a self-signed NAS certificate can be watched. The check does not fetch a CRL or OCSP response. An expiry or name failure classifies as `service` without an ICMP probe, the same as a TCP refusal or an HTTP status mismatch. The window is fixed at 7 days; a per-check window is a new ROADMAP item. The monitor UI gains a TLS certificate row. `bindChecks` now goes through a `checkBinder` interface, the DNS lookup helpers moved to peerdns.go, and the main specs and CHANGELOG are updated. The add-tls-expiry-check OpenSpec change is archived. Tested with go test ./..., golangci-lint, govulncheck and the Playwright monitor UI tests. Not run against a real tailnet. Signed-off-by: Richard Shade <rshade@tailscale.com>
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
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.
A
tls:<port>check dials the target through netEnv, completes a TLS handshake and fails when the leaf certificate expires within 7 days or is not yet valid. Nothing was watching certificate expiry before, andtls:was rejected at load time.The verified name is the DNS name of the peer that owns the address, taken from the live peer view and then the status cache, so a Tailscale IP, a short name and a full
*.ts.netname all verify against the certificate Tailscale issued. A subnet route never supplies the name.insecure_tlsskips chain and name verification but still enforces the leaf dates, so a self-signed NAS certificate can be watched. The check does not fetch a CRL or OCSP response.An expiry or name failure classifies as
servicewithout an ICMP probe, the same as a TCP refusal or an HTTP status mismatch. The window is fixed at 7 days; a per-check window is a new ROADMAP item.The monitor UI gains a TLS certificate row.
bindChecksnow goes through acheckBinderinterface, the DNS lookup helpers moved to peerdns.go, and the main specs and CHANGELOG are updated. The add-tls-expiry-check OpenSpec change is archived.Tested with go test ./..., golangci-lint, govulncheck and the Playwright monitor UI tests. Not run against a real tailnet.