Hi!
>> https://php.net/releases/active.php. This is used by the bug tracker
>> in conjunction with pulling version information from qa.php.net, so it
>> should be reliable.
>
> Excellent! This is a wonderful starting point :)
Note also that while this API does not list it, every release now also
> De : Leigh [mailto:lei...@gmail.com]
>
> On 7 January 2015 at 12:52, Scott Arciszewski
> wrote:
> >
> > Would it be possible for php.net to publish a cryptographically signed
> > (e.g. openssl_sign() with a RSA private key kept offline) list in a
> > pre-defined location (e.g. /stable_versions.
> That said, if you're OK trusting HTTPS and can do without the manual
signing step,
I'm not and cannot. After Diginotar and the Snowden revelations, I place
zero trust in CAs. :)
> we have an unadvertised JSON backend that can provide
> the stable release information you'd need:
> https://php.ne
(cross-posting to php-webmaster as well)
On 7 January 2015 at 04:52, Scott Arciszewski wrote:
> Would it be possible for php.net to publish a cryptographically signed
> (e.g. openssl_sign() with a RSA private key kept offline) list in a
> pre-defined location (e.g. /stable_versions.txt) so that s
On 7 January 2015 at 12:52, Scott Arciszewski wrote:
> Hello,
>
> Would it be possible for php.net to publish a cryptographically signed
> (e.g. openssl_sign() with a RSA private key kept offline) list in a
> pre-defined location (e.g. /stable_versions.txt) so that scripts can be
> written to read
