Just wrote a mail. My intention is to have a version that is suitable for back
porting.
> Am 03.09.2018 um 11:16 schrieb Ruediger Pluem :
>
>
>
> On 09/03/2018 11:06 AM, ic...@apache.org wrote:
>> Author: icing
>> Date: Mon Sep 3 09:06:35 2018
>> New Revision: 1839920
>>
>> URL:
Hi Jim!
Thanks for the tip, but how can I do that? Following the make file
when "make check" is executed would be an option?
Regards,
Danesh
On Sun, Sep 2, 2018 at 9:25 PM Jim Jagielski wrote:
>
> FWIW, I've never run 'make check' but always run the test suite explicitly.
>
> > On Sep 2,
On 09/03/2018 11:06 AM, ic...@apache.org wrote:
> Author: icing
> Date: Mon Sep 3 09:06:35 2018
> New Revision: 1839920
>
> URL: http://svn.apache.org/viewvc?rev=1839920=rev
> Log:
> On the trunk:
>
> SSL protocl TLSv1.3 no longer part of 'all' when configured. Needs to be
> added
Dear SSL care takers and stake holders,
trunk has TLSv1.3 support for some time. I just now changed the 'all'
SSLProtocol selection, so that it does not include TLSv1.3. This means that in
order to enable it, admins must add an explicit '+TLSv1.3' to their config
(same for SSLProxyProtocl of
> Am 03.09.2018 um 13:56 schrieb Ruediger Pluem :
>
>
>
> On 09/03/2018 01:32 PM, Stefan Eissing wrote:
>>
>>
>>> Am 03.09.2018 um 13:19 schrieb Joe Orton :
>>>
>>> On Mon, Sep 03, 2018 at 11:17:39AM +0200, Stefan Eissing wrote:
Dear SSL care takers and stake holders,
>
>>
>>> IMO
+1! for backporting
> On Sep 3, 2018, at 5:17 AM, Stefan Eissing
> wrote:
>
> Dear SSL care takers and stake holders,
>
> trunk has TLSv1.3 support for some time. I just now changed the 'all'
> SSLProtocol selection, so that it does not include TLSv1.3. This means that
> in order to enable
> Am 03.09.2018 um 13:19 schrieb Joe Orton :
>
> On Mon, Sep 03, 2018 at 11:17:39AM +0200, Stefan Eissing wrote:
>> Dear SSL care takers and stake holders,
>>
>> trunk has TLSv1.3 support for some time. I just now changed the 'all'
>> SSLProtocol selection, so that it does not include
On 09/03/2018 01:32 PM, Stefan Eissing wrote:
>
>
>> Am 03.09.2018 um 13:19 schrieb Joe Orton :
>>
>> On Mon, Sep 03, 2018 at 11:17:39AM +0200, Stefan Eissing wrote:
>>> Dear SSL care takers and stake holders,
>
>> IMO there is no problem with supporting it by default (not needing
>>
Am 03.09.2018 um 13:19 schrieb Joe Orton:
AIUI the various bits of new API added for TLS/1.3 are not necessarily
stable until there is a final OpenSSL 1.1.1 release, so maybe we should
wait for that first?
Last mentioned date for GA release of OpenSSL 1.1.1 was Tuesday 11th
September. Not
The test framework itself is under:
https://svn.apache.org/viewvc/httpd/test/framework/trunk/
and is run using:
t/TEST
> On Sep 3, 2018, at 3:34 AM, Danesh Daroui wrote:
>
> Hi Jim!
>
> Thanks for the tip, but how can I do that? Following the make file
> when "make check" is
On Mon, Sep 03, 2018 at 11:17:39AM +0200, Stefan Eissing wrote:
> Dear SSL care takers and stake holders,
>
> trunk has TLSv1.3 support for some time. I just now changed the 'all'
> SSLProtocol selection, so that it does not include TLSv1.3. This means that
> in order to enable it, admins must
Speaking of SSL and rare renegotiation setups: Bernard and me are suspecting
that
libressl has issues here for quite some time. At least it looks that way:
https://github.com/libressl-portable/portable/issues/443
Just FYI in case someone encounters such things.
> Am 03.09.2018 um 13:32 schrieb
On 09/03/2018 09:45 AM, Jim Jagielski wrote:
+1! for backporting
>> On Sep 3, 2018, at 5:17 AM, Stefan Eissing
wrote:
>>
>> Dear SSL care takers and stake holders,
>>
>> trunk has TLSv1.3 support for some time.
TLSv1.3 is a published protocol and I see no reason why it wouldn't be
13 matches
Mail list logo
