-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add new Pin type with secrecy/zeroize wrapper #128
Conversation
Related to #126 Signed-off-by: Simon Bihel <[email protected]>
I think it looks mostly OK. I'm a liiiitle bit worried about name confusion with |
That's fair, and I mistakenly imported
I would vote for 2 but I don't have a strong preference. |
Hey, sorry for the long delay. I think I'd go for something like 4, 5, or 6 from your list, but I don't have any strong feelings between them. The reason I'd avoid 2 is exactly what you mentioned, that it's technically incorrect and perhaps confusing, if it does cover both SO and User PINs. |
Yep. Maybe let's go with |
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.
That was fast! Thanks for the patch, I think at least one of your commits is missing a sign-off, though.
Signed-off-by: Simon Bihel <[email protected]>
Sorry about that, fixed |
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 👍
Related to #126
In the end, I don't know if it's such a good idea. The code is only handling
&str
so it is up to you to decide if you think this breaking change is worth it to make users aware that they should be careful with their pins.