feat/separate fingerprint to file prepared for git commit opt out #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
neutronth
commented
Jun 30, 2024
neutronth
commented
- feat: separate fingerprint file prepared for git commit opt-out
- feat(doc): add information about the encrypt once operation mode
* Despite, the fingerprint has been encrypted but it is still has a chance to be attacked with the brute-force method. Therefore, separate the fingerprint to a file and let the user exclude it from a commit and no store in the repository could prevent the attack.
* Inform the user that the generated fingerprint file must not be store in the repository and locally keep it in the developer's environment only
neutronth
deleted the
feat/separate-fingerprint-to-file-prepared-for-git-commit-opt-out
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.