Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spaces in Passwords Not Allowed #89

Open
frankcrawford opened this issue Feb 25, 2020 · 2 comments
Open

Spaces in Passwords Not Allowed #89

frankcrawford opened this issue Feb 25, 2020 · 2 comments

Comments

@frankcrawford
Copy link
Contributor

The test in htdocs/user/login-process.php files if the user's password has a space in it. The test is:

$password = security_form_input("/^\S*$/", "password_namedmanager", 1, "Please enter a password.");

The message appears to be ensure that it isn't an empty string entered, but fails. I've changed it to:

$password = security_form_input("/^\S.*$/", "password_namedmanager", 1, "Please enter a password.");

Which is less stringent, in that it only expects a non-space as the first character, and then accepts the rest of the line, although I'm sure there are other ways to do his test.

@waitspring
Copy link

Hello Frank Crawford.

I have meet a problem which is not noted by any logs: I have installed namedmanage-bind.noarch and namedmanage-www.noarch successfully from YUM, and updated all configure files following the wiki documents step by step.

When I executed this command:
php -q /usr/share/namedmanager/bind/namedmanager_bind_configwriter.php

My shell return as:

Debug: debug      | start                | 
Debug: debug      | start                | AMBERPHPLIB STARTED
Debug: debug      | start                | Debugging for: 
Debug: debug      | start                | 
Debug: debug      | start                | Framework Load Complete.
Debug: debug      | start                | 
Debug: debug      | start                | NAMEDMANAGER LIBRARIES LOADED
Debug: debug      | start                | 
Debug: debug      | script               | Obtained filelock
Debug: debug      | bind_config          | Executing check_permissions()
Debug: debug      | soap_api             | Executing authenticate()
Debug: debug      | soap_api             | Authenticating with API as DNS server dns.test.zbj.com...
Debug: debug      | soap_api             | Authentication successful
Debug: debug      | soap_api             | Executing check_update_version()
Debug: debug      | soap_api             | System configuration is uptodate, no changes nessacary

According to the wiki documents, my configure files were checked successfully.

But in the NamedManager web, the Configuration Status & Logging Status are showing as:

  • Configuration Status | status_unsynced Last synced on 1970-01-01 08:00:01
  • Logging Status | status_unsynced Logging appears stale, last synced on 1970-01-01 08:00:01

Have you ever had this problem? If so, where should I solve the problem?

@frankcrawford
Copy link
Contributor Author

@waitspring I don't remember ever seen this error before, although I'm not certain. I don't currently have it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants