Closed
Description
by viriketo:
Using go 1.0.2 on linux-x86_64. It looks like go https works with a hardcoded path to ca-bundle list of accepted certificates. I think it would be nice if src/pkg/crypto/x509/root_unix.go could look at some environment variable for an exclusive ca-cert. In the GNU/Linux distribution NixOS we have the system ca-cert bundle sitting at a path different than those hardcoded in root_unix.go, and I can patch go1.0.2 to make it work. But users may want to have control about the trusted certificates, when they run go programs.
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Activity
robpike commentedon Aug 4, 2012
Comment 1:
Labels changed: added priority-later, packagechange, removed priority-triage.
Owner changed to @agl.
Status changed to Accepted.
rsc commentedon Nov 27, 2013
Comment 3:
Labels changed: added go1.3maybe.
rsc commentedon Dec 4, 2013
Comment 4:
Labels changed: added release-none, removed go1.3maybe.
rsc commentedon Dec 4, 2013
Comment 5:
Labels changed: added repo-main.
gopherbot commentedon Nov 21, 2014
Comment 6 by sokolyuk:
odeke-em commentedon Oct 10, 2016
Any thoughts on this @agl?
gopherbot commentedon Feb 2, 2017
CL https://golang.org/cl/36093 mentions this issue.