Move all subdomains of launchpad.net to HTTPS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
If we have all of launchpad's subdomains served via HTTPS we can provide a higher level of security for the domain with the HSTS preload list.
The first task really would be to see if we can default all PPAs to https - 1473091
The following sites would need to be served HTTPS only:
blog.launchpad.net
ppa.launchpad.net
The following would need to have some tune-ups to the SSL config (to advertise HSTS, etc):
dev.launchpad.net
More on the preload list:
One added benefit once we get past a certain # of days (maybe 126, maybe 180) is that we can be preloaded as an HSTS site in Chrome and Firefox:
Chrome's post: http://
Firefox's: https:/
A first part of this was tracked here - https:/
no longer affects: | altlinux |
information type: | Public → Public Security |
It's not quite that simple, as certain services must remain HTTP in their current implementation. Most notably, blog.launchpad.net runs on WordPress -- not a piece of software that is even approaching sufficiently trustworthy to be in the same security domain as Launchpad.