URL:
<http://gna.org/task/?7988>
Summary: HTTPS for freeciv.org websites
Project: Freeciv
Submitted by: jtn
Submitted on: Mon 04 Jul 2016 10:52:30 PM BST
Should Start On: Mon 04 Jul 2016 12:00:00 AM BST
Should be Finished on: Mon 04 Jul 2016 12:00:00 AM BST
Category: None
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
Planned Release:
_______________________________________________________
Details:
None of the freeciv.org websites apart from play.freeciv.org offer HTTPS. We
ought to, on general principles.
Now that Let's Encrypt <https://letsencrypt.org/> exists this should be
relatively easy. There's no actually RPM-packaged letsencrypt/ACME client
specifically for CentOS 6 (colossus) but I'm sure one can be deployed fairly
easily.
The main thing I haven't sorted out in my mind is what operational
arrangements we need to make in the team for continuity of credentials etc
before we do this.
(This is about publishing, and mainly aimed at www, forum, etc. Making Freeciv
clients use HTTPS for meta.freeciv.org is more fraught and will be a separate
ticket. That's no reason not to make meta.freeciv.org also available over
HTTPS since it has a web front end.)
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?7988>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Freeciv-dev mailing list
[email protected]
https://mail.gna.org/listinfo/freeciv-dev
