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

HTTP(retentiou)S #10

Closed
ghost opened this issue Mar 14, 2015 · 13 comments
Closed

HTTP(retentiou)S #10

ghost opened this issue Mar 14, 2015 · 13 comments
Assignees

Comments

@ghost
Copy link

ghost commented Mar 14, 2015

nobody in SF will ever look me in the eye again if we serve this this shit over raw http. I truly do not give a fuck but y'know. Support paranoid users using HTTPNowhere, etc.

@ghost ghost assigned morganastra Mar 14, 2015
@morganastra
Copy link
Contributor

Who's going to pay for our ssl keys?

@ghost
Copy link
Author

ghost commented Mar 14, 2015

how much do they cost?

@ghost
Copy link
Author

ghost commented Mar 14, 2015

oh I see, like 30-50 bucks. I don't think that's worth it. we should indicate that we accept pull requests in the form of straight cash that we could use to buy something like that. But I don't want to deal with it. Maybe we know someone at heroku who could help???

@ghost
Copy link
Author

ghost commented Mar 14, 2015

perhaps we should suggest that the paranoid user use tor+tails on a new (non-commercial, free software only) computer and burn the computer immediately after use (e-waste facilities are too slow)

@non
Copy link
Contributor

non commented Mar 15, 2015

Personally I don't see a strong reason to use HTTPS here...

...but I'd be happy to contribute some money if someone else wants to buy a cert.

@valpackett
Copy link

You don't need money for this, startssl free is, well, free

@ticky
Copy link
Contributor

ticky commented Jun 16, 2015

I notice that while there is TLS support enabled on pronoun.is, subdomains return a different certificate, which doesn’t cover the pronoun.is domain at all;

screen shot 2015-06-16 at 6 42 13 pm

I’ve seen plenty of people use my.pronoun.is for Twitter bios, for instance, and I think it’s a pretty good, cute use case and would be great to extend the TLS support to it, given the main certificate does include *.pronoun.is. I’m hoping the issue is just a Heroku configuration thing!

@morganastra
Copy link
Contributor

@grapegravity that is totally a Heroku thing (or maybe a cloudflare thing?), I never even tried to get HTTPS set up. I've actually been thinking about moving the site off of Heroku anyway since they're breaking the free tier, I'll look into this whenever I get around to that.

@nogweii
Copy link

nogweii commented Oct 14, 2015

Let's Encrypt will solve this pretty cleanly, though I'm not sure how you would deploy it on Heroku. (The project has really focused on sysadmins for the first version, just to get a client out there. It is very user friendly if you don't mind the CLI, however.)

If you don't want to wait, StartSSL is totally valid and a good way to get it sooner rather than later.

EDIT: I noticed that the site is sitting behind CloudFlare, so it should be a one click setup of SSL since they provide it for free.

@tinruufu
Copy link

are there any browsers the ssl cert doesn't work in? could you redirect http to https? most links to pronoun.is that i see are http, and https is kinda pointless if nobody is using it; people will mostly just be copying the link out of their address bar

even the link at the bottom of every page explicitly links to http, which seems… unnecessary

@morganastra
Copy link
Contributor

I don't think we're going to do this any time soon

@tinruufu
Copy link

you're already serving the site over https, all that's left to do is set up a redirect and make the internal links either relative or explicitly https. i… don't understand why you wouldn't want to take those last tiny steps

@m4lvin
Copy link

m4lvin commented May 19, 2017

Could this be reconsidered? Letsencrypt offers free certificates nowadays and I think it can be automated on heroku. Please include "www." and "my." in the certificate and fix #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants