-
Notifications
You must be signed in to change notification settings - Fork 100
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
Update link to doc page #144
Comments
HTTPS is necessary in some cases, but isn't one of them. Is source code the concern? As far as I know, package builds rely on checksums, not encrypted transport. |
I was referring to the https://eradman.com/entrproject/ link which users will be going to for documentation. Even though there is no sensitive information to protect or any incentive for malicious actors to modify the documentation while in transit, HTTPS will provide the following:
Since you already have a Lets Encrypt cert and https already enabled, I think it is just good practice to serve the documentation over https. Anyway, I want to thank you for writing |
Thanks for the explanation. I had not heard of the tldr project before. Thanks for your contribution! I enabled HTTPS because people ask for it, but if it were not for Lets Encrypt I wouldn't do it. (As an aside, it's amazing that they have don't with such a small budget.) My view is that the entire chain of trust and the mechanism for renewing certificates is brittle, and I don't trust it to keep running if I am hit by a bus. Closing, but I'll keep these points in mind. |
Please update the link to the doc page to use HTTPS
The text was updated successfully, but these errors were encountered: