You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
Currently it accepts plaintext http connections. Might be intended behavior if we do not publish ports directly, but still confusing.
The text was updated successfully, but these errors were encountered: