-
Notifications
You must be signed in to change notification settings - Fork 32
Develop #46
Conversation
Fixes #35 Updates tendermint/coding#27 Started a doc.go file to provide an overview/high level dive into the functionality of this repo. Also added an example_test.go file in which we can put end-to-end code examples/actual usage patterns that can be copied and pasted and will always have to compile when tests are run to ensure that we don't regress.
This commit adds salts to the library using bcrypt.
add metalinter to Makefile & apply some fixes
Nano Support
Bcrypt usability
Bugfix: ledger nano/hid compiles on osx/golang1.9
if pass == "" { | ||
return key.Bytes(), nil | ||
func (e secretbox) Encrypt(privKey crypto.PrivKey, passphrase string) (saltBytes []byte, encBytes []byte, err error) { | ||
if passphrase == "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't this be deleted, since we don't want users to encrypt keys without a passphrase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We break enough stuff with our encryption library. This is the only way to save keys between versions... export unencrypted and import unencrypted.
We should expose them and use them to migrate keys. Until production release and a stable go-crypto
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean its currently possible to migrate keys? We should defntly be trying to support that asap if possible ...
No description provided.