J.

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    J. supported this idea  · 
  2. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Mailgun Dashboard » Control Panel/Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    J. supported this idea  · 
    An error occurred while saving the comment
    J. commented  · 

    Actually, neither of these solutions is acceptable. The correct solution is:
    3) Accept all printing ASCII and Unicode chatacters (including spaces) in the password. See NIST Special Publication 800-63B, Section 5.1.1.2 and Appendix A (https://doi.org/10.6028/NIST.SP.800-63b).

    Barring that, 4) All password restrictions should be well documented in documents, help text, and error messages. A password should NEVER be accepted in setup and then rejected in use.

    I spent two hours beating my head against this wall until I finally found this post.

Feedback and Knowledge Base