dave2wave commented on issue #405: URL: https://github.com/apache/tooling-trusted-releases/issues/405#issuecomment-3643081793
The requirements point to https://pages.nist.gov/800-63-3/sp800-63b.html#memsecretver which has cleaner explanation. > When processing requests to establish and change memorized secrets, verifiers SHALL compare the prospective secrets against a list that contains values known to be commonly-used, expected, or compromised. For example, the list MAY include, but is not limited to: > > - Passwords obtained from previous breach corpuses. > - Dictionary words. > - Repetitive or sequential characters (e.g. ‘aaaaaa’, ‘1234abcd’). > - Context-specific words, such as the name of the service, the username, and derivatives thereof. >. If the chosen secret is found in the list, the CSP or verifier SHALL advise the subscriber that they need to select a different >. secret, SHALL provide the reason for rejection, and SHALL require the subscriber to choose a different value. It's still work to be done on `apache/infrastructure-idm` or its successor. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
