On Thu, Aug 21, 2014, at 09:48, Ryan Hiebert wrote: > > > On Aug 21, 2014, at 11:29 AM, Martin v. Löwis <mar...@v.loewis.de> wrote: > > > > Am 21.08.14 17:44, schrieb Nick Coghlan: > >> I've now raised this issue with the infrastructure team. The current > >> hosting arrangements for bugs.python.org were put in place when the > >> PSF didn't have any on-call system administrators of its own, but now > >> that we do, it may be time to migrate that service to a location where > >> we can switch to a more appropriate SSL certificate. > > > > Just to relay Noah's response: it's actually not the hosting that > > prevents installation of a proper certificate, it's the limitation > > that the certificate we could deploy would include "python.org" as > > a server name, which is considered risky regardless of where the > > service is hosted. There are solutions to that as well, of course. > > That sounds like a limitation I’ve seen with StartSSL. Perhaps there’s a > certificate authority that would be willing to sponsor a certificate for > Python without this annoying limitation?
Perhaps some board members could comment, but I hope the PSF could just pay a few hundred a year for a proper certificate. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
