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/tls: needs a convenience function for reading encrypted keys #6722

Open
gopherbot opened this issue Nov 6, 2013 · 7 comments
Open

crypto/tls: needs a convenience function for reading encrypted keys #6722

gopherbot opened this issue Nov 6, 2013 · 7 comments
Milestone
Unplanned

Comments

@gopherbot
Copy link

by jeff.allen:

crypto/tls.X509KeyPair can't deal with encrypted key files. This wouldn't be much of a
big deal except that the quantity of code needed to work around it is really big and
repeats lots of code from the std library.

See this message: https://groups.google.com/d/msg/golang-nuts/ht_gQ2ET0c0/efaGZdIxCmAJ

It would be nicer to have crypto/tls.X509EncryptedKeyPair(certPEMBlock, keyPEMBlock,
password []byte) (cert Certificate, err error) that would use password to decrypt
keyPEMBlock.
@rsc
Copy link
Contributor

rsc commented Nov 27, 2013

Comment 1:

Labels changed: added go1.3maybe.

@dsymonds
Copy link
Contributor

dsymonds commented Dec 2, 2013

Comment 2:

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

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 3:

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

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 4:

Labels changed: added repo-main.

@bradfitz bradfitz removed the new label Dec 18, 2014
@jfcg
Copy link

jfcg commented Mar 13, 2015

Hi,
is there any plan on implementing this?
there is a working sample code here: http://play.golang.org/p/8OYTuZtZIQ

@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@odeke-em
Copy link
Member

/cc @agl

@odeke-em odeke-em mentioned this issue Oct 10, 2016
Open
@odeke-em
Copy link
Member

Hello there @jfcg, might you still be interested in working on this issue?
Perhaps putting it in a CL would re-ignite the conversation and make it reviewable
thus implementing the feature.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
6 participants
@bradfitz @dsymonds @rsc @jfcg @odeke-em @gopherbot