On Thu, Feb 25, 2016 at 20:56:39 -0500, Simon Ruggier wrote:
> On Fri, 19 Feb 2016 23:01:24 -0500 Simon Ruggier wrote:
> > Also, my own testing seems to show that the certificate chain issue is
> > still present in the latest 1.0.1 release (as I commented on 813468), so
> > adopting the latest 1.
On Fri, 19 Feb 2016 23:01:24 -0500 Simon Ruggier wrote:
> Also, my own testing seems to show that the certificate chain issue is
> still present in the latest 1.0.1 release (as I commented on 813468), so
> adopting the latest 1.0.2 release seems like the only reasonable
> alternative.
As I commen
On Mon, 15 Feb 2016 18:59:46 + "Adam D. Barratt" <
a...@adam-barratt.org.uk> wrote:
> On Mon, 2016-02-15 at 19:46 +0100, Christian Beer wrote:
> > Hi,
> >
> > there are more people reporting that they are directly affected by a bug
> > in the Debian Jessie openssl package where it doesn't check
On Mon, 2016-02-15 at 19:46 +0100, Christian Beer wrote:
> Hi,
>
> there are more people reporting that they are directly affected by a bug
> in the Debian Jessie openssl package where it doesn't check an
> alternative certificate chain (which is fixed in the latest upstream 1.0.1).
[...]
> Right
Hi,
there are more people reporting that they are directly affected by a bug
in the Debian Jessie openssl package where it doesn't check an
alternative certificate chain (which is fixed in the latest upstream 1.0.1).
I would urge the Release Team to come to a conclusion regarding the
upgrade of o
5 matches
Mail list logo