Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ACME and FreeDNS password symbols causing pfSenseConfigurator errors

    Scheduled Pinned Locked Moved ACME
    3 Posts 2 Posters 792 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • w0wW
      w0w
      last edited by

      When creating new certificate and using method freedns and entering as a password "O?A OuU$?U§y~oe" I am getting an error

      "
      pfSenseConfigurator
      
          pfSense is restoring the configuration /cf/conf/backup/config-1511681170.xml @ 2017-11-26 09:26:47
      
      "
      

      The other thing is that password should be hidden and it's not.

      2.4.3-DEVELOPMENT (amd64)
      built on Sat Nov 25 19:44:06 CST 2017
      FreeBSD 11.1-RELEASE-p4

      The system is on the latest version.
      Version information updated at Sun Nov 26 8:07:02 EET 2017

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That's not entirely unexpected when you use non-XML-safe characters in some fields. We've been slowly trying to fix that up over time but some fields are still not quite ready to handle that.

        Side note, you may want to read the new NIST guidelines for passwords which favor length and drop the complexity requirements. You're only making it harder on yourself by using those characters in passwords these days.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • w0wW
          w0w
          last edited by

          AFAIK the NIST guideline sounded like
          "Drop the algorithmic complexity song and dance
          No more arbitrary password complexity requirements needing mixtures of upper case letters, symbols and numbers. Like frequent password changes, it’s been shown repeatedly that these types of restrictions often result in worse passwords."
          Yes it was about that you can not require a complex password with short length over much more longer password but without any complexity. The length is limited by freeDNS and I am sure in case of limited length complexity always wins  ;)

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.