-
Notifications
You must be signed in to change notification settings - Fork 66
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
feat(keystore): keystore implmenetation #1602
Conversation
652bee2
to
86b30ce
Compare
profile/profile.go
Outdated
@@ -143,6 +152,7 @@ func (p Profile) Encode() (*config.ProfilePod, error) { | |||
for _, maddr := range p.NetworkAddrs { | |||
addrs = append(addrs, maddr.String()) | |||
} | |||
// TODO(aqru): see if we should also show pubkey/keyID here |
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.
@b5 This is still TODO before I merge
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.
@dustmop any opinion on this?
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.
I think this is a no? We have the profileID, and can use that to look up the key{public,id} from the keystore. No reason to store it twice, better to keep it normalized.
4c871c6
to
c7a9a6c
Compare
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.
LGTM!
profile/profile.go
Outdated
@@ -143,6 +152,7 @@ func (p Profile) Encode() (*config.ProfilePod, error) { | |||
for _, maddr := range p.NetworkAddrs { | |||
addrs = append(addrs, maddr.String()) | |||
} | |||
// TODO(aqru): see if we should also show pubkey/keyID here |
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.
I think this is a no? We have the profileID, and can use that to look up the key{public,id} from the keystore. No reason to store it twice, better to keep it normalized.
No description provided.