Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

crypto/x509: allow cert bundle path to be set by environment variable #3905

Closed
gopherbot opened this issue Aug 4, 2012 · 7 comments
Closed

crypto/x509: allow cert bundle path to be set by environment variable #3905

gopherbot opened this issue Aug 4, 2012 · 7 comments
Labels
FrozenDueToAge
Milestone
Unplanned

Comments

@gopherbot
Copy link

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.
@robpike
Copy link
Contributor

robpike commented Aug 4, 2012

Comment 1:

Labels changed: added priority-later, packagechange, removed priority-triage.

Owner changed to @agl.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 3:

Labels changed: added go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 4:

Labels changed: added release-none, removed go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 5:

Labels changed: added repo-main.

@gopherbot
Copy link
Author

Comment 6 by sokolyuk:

Please add
"/etc/ssl/cacert.pem",                      // OmniOS
into  pkg/crypto/x509/root_unix.go

@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@mwielgoszewski mwielgoszewski mentioned this issue Feb 26, 2016
Closed
@odeke-em
Copy link
Member

Any thoughts on this @agl?

@gopherbot
Copy link
Author

CL https://golang.org/cl/36093 mentions this issue.

@golang golang locked and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
4 participants
@rsc @robpike @odeke-em @gopherbot