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

Add failure-counter mechanism #176

Closed
ionut-arm opened this issue May 30, 2020 · 0 comments
Closed

Add failure-counter mechanism #176

ionut-arm opened this issue May 30, 2020 · 0 comments
Labels
security Issues related to the security and privacy of the service

Comments

@ionut-arm
Copy link
Member

As part of our safety mechanism within the service, we could have a configuration value for the administrator which controls how many of a certain type of failure are acceptable before the service becomes unresponsive, somewhat like TPMs freeze if a number of certain failures occur.

An example of a failure that might be included is an authentication error (e.g. the JWT token wasn't signed correctly), or generic errors from providers.

This does open the possibility of a DoS, so we probably shouldn't enable it by default.

@ionut-arm ionut-arm added the security Issues related to the security and privacy of the service label Jun 8, 2020
@hug-dev hug-dev closed this as completed Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security Issues related to the security and privacy of the service
Projects
None yet
Development

No branches or pull requests

2 participants