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

Set up SSL certs for website and package repo #14

Closed
q5sys opened this issue Sep 4, 2018 · 3 comments
Closed

Set up SSL certs for website and package repo #14

q5sys opened this issue Sep 4, 2018 · 3 comments
Assignees

Comments

Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
@q5sys
Copy link
Member

@q5sys q5sys commented Sep 4, 2018

The thing must be done.

@jdrch
Copy link

@jdrch jdrch commented Dec 28, 2018

Just gonna chime in that this is imperative. I totally acknowledge that this is a volunteer effort, Trident is free, and the dev team have done a great job so far, but this is a serious issue that flies in the face of what BSD (typically) stands for: doing things The Right Way (TM) and security.

@beanpole135
Copy link
Member

@beanpole135 beanpole135 commented Jan 11, 2019

The package server now has an auto-renewed letsencrypt certificate for https access, and http usage is automatically redirected to https.
The website itself is still using http only at the moment, and I have WIP to move that one over as well, but since it is purely a static html landing page with no info/access to any file that one is not quite as high on the priority list.

@jdrch
Copy link

@jdrch jdrch commented Jan 12, 2019

@beanpole135 Thanks so much :) I feel better recommending people try Trident now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment