-
Notifications
You must be signed in to change notification settings - Fork 210
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
Chef Server API should not allow client-names with newline characters #124
Comments
Similar to #90, I tried to recreate this. I got a 400 response from the server with the message The input here was:
Is it possible that this client was modified through an external means? |
This is possible via the API on a PUT to an existing client:
|
Hello, The solution proposed by stevendanna id not working with Chef Server 12. I tried to change the name with: The result indicated that the name changed correctly but after executing the command "clients.all", the name of the client is still always: name => 'XXXXXX |
Any tips for getting rid of a client with a newline? |
We solved this by renaming the client from within postgres, and then deleting the client with knife. For example, if the bad hostname was "foobar\n", I'd do something like this:
Then, optionally, you can delete it with knife:
This worked fine for us, but may have consequences. Perform at your own risk! 🤷 |
In the current chef-server we can create a client with name "staging-mike\n".
That should not be allowed.
REF: #90
Issue noted in : https://getchef.zendesk.com/agent/tickets/3212
The text was updated successfully, but these errors were encountered: