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 a 5-strike scrubber to the CLI #10

Open
sciguyryan opened this issue Apr 22, 2022 · 1 comment
Open

Add a 5-strike scrubber to the CLI #10

sciguyryan opened this issue Apr 22, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@sciguyryan
Copy link
Owner

sciguyryan commented Apr 22, 2022

Consider adding a 5-strike scrubber to the CLI application.

This would render a file non-decodable if the wrong original file or wrong password are used 3 times. This would ideally be something that is configurable.

My thoughts for this function being that if someone were attempting to crack the password used to decode a file, or attempting to find the original file used to decode the file, the function would render it impossible to decode the file. This would prevent any efforts to brute force break the password, for example.

@sciguyryan sciguyryan added the enhancement New feature or request label Apr 22, 2022
@sciguyryan sciguyryan self-assigned this Apr 22, 2022
@sciguyryan sciguyryan added wontfix This will not be worked on and removed wontfix This will not be worked on labels Apr 25, 2022
@sciguyryan sciguyryan changed the title Add a 3-strike scrubber to the CLI Add a 5-strike scrubber to the CLI May 4, 2022
@sciguyryan
Copy link
Owner Author

Upon reflection, I think 5 strikes will be more reasonable than 3.

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

No branches or pull requests

1 participant