On Tue, Dec 1, 2015 at 7:35 PM, Davey Shafik wrote:
> On Mon, Nov 30, 2015 at 10:35 AM, Ferenc Kovacs 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 issue
On Mon, Nov 30, 2015 at 10:35 AM, Ferenc Kovacs 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
> 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
2015-11-30 14:49 GMT+01:00 Chris Riley :
> Anyone else getting an invalid cert on https://pear.php.net ?
>
Yes and it points to cweiske.de. PHP's certs are also "broken" for
svn.php.net and edit.php.net, there are browser warnings because of the
SHA1 certificate signatures.
Hi:
> Anyone else getting an invalid cert on https://pear.php.net ?
The pear webserver died. Christian Weiske is doing the move. He's
temporarily using his cert.
Thanks for the heads up.
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive
