-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Recommend using certificates from LetsEncrypt instead of self-signed certs #359
Comments
@arunasank: actually the documentation documents the usage of self signed certificates only for testing purposes. It would be valuable to re-integrate inside Tor2web the code of GlobaLeaks that implement the letsencrypt request and renewal. |
Or it would be even more valuable to integrate the Tor2web functionalities inside GlobaLeaks to achieve not just LetsEncrypt but also the web administration interface, Tor management, software lifecycle, data retention, Statistics and a bullet proof software lifecycle. De facto Tor2web is a minor feature of GlobaLeaks |
That would be a preatty easy but ugly way in my opinion; it would really complicate the maintainance of the two softwares. Let's consider eventually to package some shared components as dependencies to build the two softeare (included eventually the management interfaces that you are looking for) |
The docs recommend using self-signed certificates. They might as well recommend LetsEncrypt.
The text was updated successfully, but these errors were encountered: