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

Docker container is not https-enabled by default #417

Closed
arkenoi opened this issue Mar 13, 2017 · 2 comments
Closed

Docker container is not https-enabled by default #417

arkenoi opened this issue Mar 13, 2017 · 2 comments

Comments

@arkenoi
Copy link
Member

arkenoi commented Mar 13, 2017

Currently it accepts plaintext http connections. Might be intended behavior if we do not publish ports directly, but still confusing.

@arkenoi arkenoi changed the title Docker container is not http-enabled by default Docker container is not https-enabled by default Mar 13, 2017
@MrSeccubus
Copy link
Member

Either I have to put some work in place to get to HTTPS with self signed certificates. Or we expect the user to set up a ngnix/apache container and proxy https to http.
Since we cannot rely on this having a domain name and being externally visible we can do self signed certificates at best.

@arkenoi
Copy link
Member Author

arkenoi commented Mar 14, 2017

Yes.

We need to understand what data interfaces should docker container have.
Certificate deployment/setting hostname is the obvious one, but there are more.
Like, importing certificates for validation chain (when talking to Nessus/OpenVAS servers), database persistence/backup/whatever, log export, reports export, maybe something else.
Let's make a list -- do you have more suggestions?

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