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

bubble up route uuid parse errors to user #598

Merged
merged 2 commits into from
Aug 16, 2023

Conversation

jeffgrunewald
Copy link
Contributor

alternative to #597 to expose the route id uuid parsing error to the user when it occurs instead of swallowing it in a less descriptive "auth error".

my basic approach to returning errors to the caller of a public-facing API is to provide as few details as possible for an attacker to exploit and then slowly add more details to make the system usable for the normal good operators just trying to use the system as designed, hence the large default reliance on "not much to see here". i think this is definitely a case where providing the detail of a typoed or invalid UUID format is reasonable detail to return to the user.

@jeffgrunewald jeffgrunewald merged commit b07ee4a into main Aug 16, 2023
1 check passed
@jeffgrunewald jeffgrunewald deleted the jg/expose-route-id-parse-error branch August 16, 2023 13:15
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

Successfully merging this pull request may close these issues.

4 participants