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

Cannot use space in username #159

Closed
TheGroundZero opened this issue Sep 5, 2018 · 3 comments
Closed

Cannot use space in username #159

TheGroundZero opened this issue Sep 5, 2018 · 3 comments

Comments

@TheGroundZero
Copy link

Expected behavior

Successfully create a new credential with a space in the username.

Current behavior

(Status code: 400) Operation 'Create Credential' failed
Given login was invalid

Steps to reproduce

  1. Create a new credential
  2. Enter username with a space in it
  3. Try to save credential

GVM versions

gsa: (gsad --version)
7.0.3

gvm: (gvmd --version)
/

openvas-scanner: (openvassd --version)
5.1.3

gvm-libs:

openvas-smb:

Environment

Operating system:
Greenbone Security Manager Community Edition

Installation method / source: (packages, source installation)
ISO from site

Logfiles


@jjnicola
Copy link
Member

jjnicola commented Sep 12, 2018

Hello @TheGroundZero,
spaces in credential in username are currently not allowed. Therefore, this is not a bug, but the message shown could be improved. I suggest you to open a new issue in the right project greenbone/gvm if you have still any concern.
Regards,
Juan

Closing here since is not a proper openvas-scanner issue.

@TheGroundZero
Copy link
Author

TheGroundZero commented Sep 12, 2018

While definitely not recommended, it is possible to create accounts with spaces in the username (e.g. on Windows systems).

The current configuration of the scanner as such prevents a user from testing systems where a username contains a space (and it is not possible to create a seperate account for testing).

If not a bug, I would request you consider this to be at least a Feature Request.

@cfi-gb
Copy link
Member

cfi-gb commented Sep 12, 2018

As a side-note the scanner is not responsible for this task. It could still worth to create a new issue at https://github.com/greenbone/gvm/issues to make the error message at least include the info that an unsupported char is used.

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

3 participants