-
Notifications
You must be signed in to change notification settings - Fork 276
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
Guard against secrets leakage #3240
Comments
I don't think it's feasible at least before we remove the config documentation from the API (as planned by hyperledger-iroha/iroha-rfcs#8). Removing |
|
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
Signed-off-by: Dmitry Murzin <[email protected]>
@dima74 should this be closed? |
Make use of the secrecy crate to prevent the secrets like
PrivateKey
(are there any other?) from being leaked accidentally by being printed in logs or serialized.Secret
wrapper also makes sure that upon dropping the field is zeroized in memoryThe text was updated successfully, but these errors were encountered: