-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support for TLS #14
Comments
Hello @amir20, I am honoured to receive a message from You because I'm a big fan of Dozzle and find it very useful. Yes, TLS would be a good idea. I had already considered implementing some TLS communication but postponed it to keep it simple. I like the suggestion, and I think I will implement it. Thanks again, and have a great weekend, |
Awesome! Here is a related issue amir20/dozzle#2536 I think ideally, it should just work by producing a similar directory to Docker with all the certs in one place. I did create some code in Golang to generate certs:
You can use it if you want. When you are ready, we can also update https://dozzle.dev/guide/remote-hosts to add a section about TLS. |
So recently I have been thinking about supporting Docker Swarm and improving remote connection. I am working on agent mode with Dozzle which is described at amir20/dozzle#3052. If implemented correctly, it would no longer require any kind of socket proxy. Let me know your thoughts... |
Hello there,
I am the creator of Dozzle. For a long time, I have been wanting to implement something like socket proxy in Go. I found your project through referral links. Many people use Tecnativa/docker-socket-proxy for simple non-secured connection.
However, I think a lot of people prefer a secured connection. I wonder if it would be best for this project to support both. Here is what I am thinking:
socket-proxy
could have a--tls
optionsocket-proxy
would only allow connections that have valid certificatesCurrently, to setup TLS over HTTP with Docker is just a pain. This solution could make it a lot simpler to setup docker for TLS with minimum effort. Even better, it would auto generated certs to be used.
What do you think?
The text was updated successfully, but these errors were encountered: