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

Feature: Automatic (Lets Encrypt) / Self-signed TLS #41

Open
warcode opened this issue Mar 7, 2016 · 3 comments
Open

Feature: Automatic (Lets Encrypt) / Self-signed TLS #41

warcode opened this issue Mar 7, 2016 · 3 comments

Comments

@warcode
Copy link

warcode commented Mar 7, 2016

Having a self-signed cert is better than no TLS at all.

@jpillora
Copy link
Owner

jpillora commented Mar 8, 2016

@jpillora jpillora changed the title Auto generate self-signed TLS cert to use by default Feature: Automatic Caddy-like TLS Mar 8, 2016
@warcode
Copy link
Author

warcode commented Mar 8, 2016

That would work for servers where you have control of the DNS, but not for shared servers where all you have is an application port. Having the option for both would be nice.

@jpillora
Copy link
Owner

jpillora commented Mar 8, 2016

All you need is control of port 80 and 443, your own DNS is really cheap, $8 per
year, free management on cloudflare. Nevertheless, I guess a self signed
option won't hurt.
On Wed, 9 Mar 2016 at 3:44 AM warcode notifications@github.com wrote:

That would work for servers where you have control of the DNS, but not for
shared servers where all you have is an application port. Having the option
for both would be nice.


Reply to this email directly or view it on GitHub
#41 (comment)
.

@jpillora jpillora changed the title Feature: Automatic Caddy-like TLS Feature: Automatic (Lets Encrypt) / Self-signed TLS Apr 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants