Please allow --strict to be chained with --symbols
#1941
Assignees
Comments
|
Yes, I agree that this should be supported. |
dominikschulz
added a commit
to dominikschulz/gopass
that referenced
this issue
Jul 1, 2021
Fixes gopasspw#1941 RELEASE_NOTES=[BUGFIX] Allow --strict to be chained with --symbols Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
dominikschulz
added a commit
that referenced
this issue
Jul 1, 2021
Fixes #1941 RELEASE_NOTES=[BUGFIX] Allow --strict to be chained with --symbols Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
kpitt
pushed a commit
to kpitt/gopass
that referenced
this issue
Jul 21, 2022
Fixes gopasspw#1941 RELEASE_NOTES=[BUGFIX] Allow --strict to be chained with --symbols Signed-off-by: Dominik Schulz <dominik.schulz@gauner.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Right now it seems that
--strictand--symbols/-sare mutually exclusive, with strict taking priority. These should have the option to be chained together in order to form passwords that have strictly have one member from each char group, symbols included.The reason these should be chained rather than overriding the behavior of
--strictis there are websites which require uppercase letters, lowercase letters, digits, and special characters, just as there are websites that require strict passwords that do not allow special characters(for some stupid reason).the former currently requires continuously generating passwords with the
-sflag until one meets the requirements.Steps To Reproduce
gopass generate --symbols --strict any.given.website/user@emailExpected behavior
a password with a member from each class
a-z,A-Z,0-9!@#$%^&*()-_+=[{]},<.>/?;:'"\~\|`Environment
daftaupe/gopassThe text was updated successfully, but these errors were encountered: