-
Notifications
You must be signed in to change notification settings - Fork 6k
security risk: password authentication is not enabled by default #1062
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
Comments
We don't want to force down everyone's throats password authentication since people might want to do SSO, which is on another issue. We document already that by setting |
Ok. Maybe enforcing password authentication isn't the solution. I still think out of the box this is insecure to a novice or someone who is not paying attention. It is trivial to find open instances of this with a tool like shodan.io. I won't post a link to the query here but I was able to find a few unintentionally open instances. This leaves access to the filesystem and terminal open to anyone that finds it. The different authentication options that code-server provides should be mentioned in README.md, with some kind of warning that a misconfiguration by the user could leave themselves vulnerable. |
still a risk for docker users.. I dont know now how to enable this using docker thru portainer |
Again, I'm pretty sure most users are aware how to set them up correctly, and most users who would run it open on the internet can take measures to secure a instance. |
@Dj-jom2x you can build your own Dockerfile to have it enabled by default, that's what I did. |
how do you change path? example if you had cpanel on.. and you want it to install under his dir only .. |
@Dj-jom2x you can see all available commands from the code-server binary.
You can take a look at my Dockerfile (I have 3) for reference: https://github.com/demyxco/code-server |
You forgot setting environment variables and just appending the |
I added a security section to the readme; hopefully that goes a long way. https://github.com/cdr/code-server#security If anyone has any thoughts on how to improve that section lemme know. For a few reasons I felt it was more natural to enable authentication rather than disable it. Is it common for people to manually expose If we're thinking about being secure by default we might want to re-visit the default of responding to HTTP requests, but perhaps users exposing |
Password authentication is now enabled by default. |
Post password by default era, how would one set it up for no password?
How should that be modified for enabling a no authentication? |
@Nosferican look at the comment above yours. For docker-compose, use the
|
Recently downloaded version 2.1523-vsc1.38.1 to try out. From reading the docs I saw there is some form of password auth 👍. After running code-server, the logs state
No authentication
👎This can be a huge security issue for someone who does not understand what they are doing. Password authentication should be enabled by default and disabled via param or environment variable.
I'll spare you the doomsday scenarios that I have been dreaming up for the past hour. I just want to see the internet a little more secure than it has been.
The text was updated successfully, but these errors were encountered: