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.

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

Introduce SensitiveError class to indicate errors which should not bubble up #1527

Open
larabr opened this issue Jun 1, 2022 · 0 comments
Open

Comments

@larabr
Copy link
Collaborator

larabr commented Jun 1, 2022

Currently we hide low-level errors that are potentially sensitive in certain higher-level functions (such as message.decrypt). It'd be best to allow the code that throws the error to mark whether it is sensitive, to avoid accidental re-throwing. A SensitiveError should never bubble up to top-level functions.

This distinction can also help debugging since not all errors need to be hidden in principle, even when e.g. parsing a private key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant