Andrew Ayer

cmd/go: telemetry data should not be in $XDG_CONFIG_HOME

5

### Go version go version go1.23.0 linux/amd64 ### Output of `go env` in your module/workspace: ```shell GO111MODULE='' GOARCH='amd64' GOBIN='' GOCACHE='/home/andrew/.cache/go-build' GOENV='/home/andrew/.config/go/env' GOEXE='' GOEXPERIMENT='' GOFLAGS='-modcacherw' GOHOSTARCH='amd64' GOHOSTOS='linux' GOINSECURE='' GOMODCACHE='/home/andrew/.go/pkg/mod' GONOPROXY='' GONOSUMDB=''...

Certificate Transparency is defined in RFC 6962, not RFC 9162

1

### MDN URL https://developer.mozilla.org/en-US/docs/Web/Security/Certificate_Transparency ### What specific section or headline is this issue about? _No response_ ### What information was incorrect, unhelpful, or incomplete? The first paragraph states that Certificate...

See https://git.glasklar.is/rgdd/silentct/-/blob/main/docs/feedback.md

Store log errors in state directory

2

Instead of writing log errors to stderr, write them to a file in the state directory. When reporting a health check failure, include the path to the file and the...

Multiple people have reported backlogs when monitoring Sectigo logs: * https://github.com/SSLMate/certspotter/issues/34#issuecomment-2959079133 * https://github.com/SSLMate/certspotter/issues/34#issuecomment-2957788163 * https://groups.google.com/a/chromium.org/g/ct-policy/c/sY0P2RwfWNs It currently appears that the rate limits are too strict and are inhibiting successful monitoring.