On Tue, Aug 11, 2015 at 5:46 PM Niall Douglas
On 11 Aug 2015 at 1:36, Klaim - Joël Lamotte wrote:
I noticed today that the https of boost.org is expired, and should have a new certificate: https://www.ssllabs.com/ssltest/analyze.html?d=boost.org
My understanding is that the process to renew the certificate was started few months ago but got nowhere. Not totally sure why though. The last status report from the steering committee is available there: http://permalink.gmane.org/gmane.comp.lib.boost.steering/126
We have a new SSL cert, and have had for some months.
The problem is installing it. We no longer have root access to the server in question and I understand the person who had root access isn't responding to email.
Who is this person? I am asking just in case it is someone at Indiana University. If it is someone here, it could be that they moved away and are no longer part of IU.
We would move to new servers, but need root access to copy off all the existing data. So we keep pinging emails, and hope one day the person in question replies.
This is why we need a dedicated employed person to do this stuff, to keep migration plans and plan upkeep so getting orphaned from access never occurs in the first place, and even if it did there is a live offsite backup configured using docker/drbd etc we can replicate from. The steering committee can only authorise that spending if there is consensus from boost-dev that someone should be employed to do this stuff, until that happens this situation will keep recurring into the future with no end in sight.
Niall
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost