Skip to content

security: raise minimum TLS version to 1.2 - #102

Open
tas50 wants to merge 1 commit into
ctdk:masterfrom
tas50:fix/tls-min-version
Open

security: raise minimum TLS version to 1.2#102
tas50 wants to merge 1 commit into
ctdk:masterfrom
tas50:fix/tls-min-version

Conversation

@tas50

@tas50 tas50 commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Issue

When use-ssl is enabled, the HTTPS server is configured with:

srv.TLSConfig = &tls.Config{MinVersion: tls.VersionTLS10}

tls.VersionTLS10 permits TLS 1.0 and 1.1, both deprecated by RFC 8996 and subject to downgrade and cipher-weakness attacks (BEAST, etc.). A network MITM can negotiate a client down to TLS 1.0. All authenticated request bodies — and web-UI passwords posted to /authenticate_user — traverse this connection.

Fix

Raise the minimum to tls.VersionTLS12 (one line). TLS 1.2 is universally supported by current Chef clients; modern Go negotiates 1.3 when both sides support it.

Verification

go build ./... and go vet . pass.

The HTTPS server (used when `use-ssl` is enabled) was configured with
`MinVersion: tls.VersionTLS10`, which permits TLS 1.0 and 1.1. Both are
deprecated (RFC 8996) and exposed to downgrade and cipher weaknesses
(e.g. BEAST). All authenticated request bodies and web-UI passwords sent
to /authenticate_user traverse this connection.

Raise the floor to TLS 1.2.

Signed-off-by: Tim Smith <tsmith84@proton.me>
@tas50
tas50 force-pushed the fix/tls-min-version branch from 05b32df to 0b385da Compare June 7, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant