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.

Sign up for GitHub

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] Use crypto.PrivateKey and crypto.PublicKey where able #29

Closed
jonbonazza opened this issue Jan 23, 2015 · 0 comments
Closed

[crypto] Use crypto.PrivateKey and crypto.PublicKey where able #29

jonbonazza opened this issue Jan 23, 2015 · 0 comments
Assignees
@jonbonazza
Labels
enhancement
Milestone
Release 1

Comments

@jonbonazza
Copy link
Contributor

Instead of working with raw interface{} types, we should use the crypto.PrivateKey and crypto.PublicKey interfaces for code clarity.
@jonbonazza jonbonazza self-assigned this Jan 23, 2015
@jonbonazza jonbonazza added this to the Release 1 milestone Jan 23, 2015
jonbonazza added a commit that referenced this issue Jan 23, 2015
@jonbonazza
fixes #29
b2fc917 
uses crypto.PrivateKey and crypto.PublicKey instead of raw interface{} types where possible for clarity.
@jonbonazza jonbonazza mentioned this issue Jan 23, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonbonazza jonbonazza

Labels
enhancement
Projects
None yet
Milestone
Release 1
Development

No branches or pull requests
2 participants
@zeroXten @jonbonazza