On Fri, Nov 11, 2016 at 12:46:49PM +0100, Moritz Muehlenhoff wrote:
B0;115;0cOn Fri, Nov 04, 2016 at 10:03:02AM +0200, Christos Trochalakis wrote:
On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
>On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
>>
>>The issue hasn
B0;115;0cOn Fri, Nov 04, 2016 at 10:03:02AM +0200, Christos Trochalakis wrote:
> On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
> >On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
> >>
> >>The issue hasn't been diagnosed upstream, but this will likely also affect
>
On Fri, Nov 04, 2016 at 10:03:02AM +0200, Christos Trochalakis wrote:
> On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
> > On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
> > >
> > > The issue hasn't been diagnosed upstream, but this will likely also
> > > affect
On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
The issue hasn't been diagnosed upstream, but this will likely also affect nginx
once rebuilt against openssl 1.1.
It seems it was fixed in OpenSSL in the mean time
On Wed, Nov 02, 2016 at 05:22:21PM +0100, Kurt Roeckx wrote:
> On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
> >
> > The issue hasn't been diagnosed upstream, but this will likely also affect
> > nginx
> > once rebuilt against openssl 1.1.
>
> It seems it was fixed in OpenS
On Wed, Nov 02, 2016 at 10:39:29AM +0100, Moritz Muehlenhoff wrote:
>
> The issue hasn't been diagnosed upstream, but this will likely also affect
> nginx
> once rebuilt against openssl 1.1.
It seems it was fixed in OpenSSL in the mean time.
Kurt
On Sat, Oct 29, 2016 at 12:53:54PM +0200, Kurt Roeckx wrote:
> On Sat, Oct 29, 2016 at 12:34:51PM +0300, Christos Trochalakis wrote:
> > On Sat, Oct 29, 2016 at 11:29:12AM +0200, Kurt Roeckx wrote:
> > > On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
> > > >
> > > > I am not
On Sat, Oct 29, 2016 at 12:34:51PM +0300, Christos Trochalakis wrote:
> On Sat, Oct 29, 2016 at 11:29:12AM +0200, Kurt Roeckx wrote:
> > On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
> > >
> > > I am not sure if the first lua patch is safe (regarding the
> > > "ssl_conn->tl
On Sat, Oct 29, 2016 at 11:29:12AM +0200, Kurt Roeckx wrote:
On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
I am not sure if the first lua patch is safe (regarding the
"ssl_conn->tlsext_status_expected = 1;" removal).
I'm not sure which patch you're talking about. I rem
On Sat, Oct 29, 2016 at 11:21:05AM +0200, Kurt Roeckx wrote:
On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
On Tue, Oct 11, 2016 at 10:41:01AM +0300, Christos Trochalakis wrote:
> On Fri, Sep 02, 2016 at 10:52:15PM +0200, Kurt Roeckx wrote:
> > Hi,
> >
> > It seems the ver
On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
>
> I am not sure if the first lua patch is safe (regarding the
> "ssl_conn->tlsext_status_expected = 1;" removal).
I'm not sure which patch you're talking about. I remember
something about something doing weird things with the
On Sat, Oct 29, 2016 at 11:04:33AM +0300, Christos Trochalakis wrote:
> On Tue, Oct 11, 2016 at 10:41:01AM +0300, Christos Trochalakis wrote:
> > On Fri, Sep 02, 2016 at 10:52:15PM +0200, Kurt Roeckx wrote:
> > > Hi,
> > >
> > > It seems the version in experimental needs this patch to build
> > >
On Tue, Oct 11, 2016 at 10:41:01AM +0300, Christos Trochalakis wrote:
On Fri, Sep 02, 2016 at 10:52:15PM +0200, Kurt Roeckx wrote:
Hi,
It seems the version in experimental needs this patch to build
nginx itself:
http://hg.nginx.org/nginx/rev/1891b2892b68
You might also want this one:
http://hg
13 matches
Mail list logo
