NewTLSConfig parses CA bundle even when insecure is set #599
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/thwap-pagesd#599
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NewTLSConfigininternal/tpagectl/client/client.goreads and validates the CA bundle file whenevercaCertFileis non-empty, even wheninsecureis also true. As a resulttpagectl --insecure --ca-cert <missing-or-empty-file> ...fails on the CA load despite TLS verification being disabled (and the CA being pointless).When
insecureis set, skip the CA file handling (or document that the two flags are mutually exclusive).See #597
Fixed in #634:
NewTLSConfigreturnsInsecureSkipVerify: trueimmediately when--insecureis set, ignoring any CA bundle (test added).