On Tue, Dec 1, 2015 at 7:35 PM, Davey Shafik <da...@php.net> wrote: > On Mon, Nov 30, 2015 at 10:35 AM, Ferenc Kovacs <tyr...@gmail.com> wrote: > >> > PHP's certs are also "broken" for >> > svn.php.net and edit.php.net, there are browser warnings because of the >> > SHA1 certificate signatures. >> > >> >> those are separate issues, already reported on syst...@php.net >> these kind of problems are either reported there via email or on >> https://bugs.php.net/ under the the PHP.net Website problem/PHP.net >> Systems >> Operation problem. > > > As a heads up, LetsEncrypt (https://letsencrypt.org) is going public on > Dec. 3rd, have we considered using them for all php.net certs? >
we are already taking an eye on them (mostly for the php.net mirrors) but wouldn't really help with the above mentioned two sites as there the problem isn't the lack of certificates but that those people with access to those boxes seems to be unavailable atm while those would are available don't have access there. please don't cc internals@ to the future replies for this topic, this isn't a php-src related problem but a system operation one. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
