On 23/03/15 14:19, Jakob Bohm wrote:
> On 23/03/2015 14:48, Matt Caswell wrote:
>> On 23/03/15 13:45, Viktor Dukhovni wrote:
>>> On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
>>>
> As Viktor states RFC 4492 says if the client sends no TLS extension
> containing the curves
On 23/03/2015 14:48, Matt Caswell wrote:
On 23/03/15 13:45, Viktor Dukhovni wrote:
On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
As Viktor states RFC 4492 says if the client sends no TLS extension
containing the curves supported then the server can choose any supported
curve. S
On 23/03/15 13:45, Viktor Dukhovni wrote:
> On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
>
>>> As Viktor states RFC 4492 says if the client sends no TLS extension
>>> containing the curves supported then the server can choose any supported
>>> curve. So your fix is to continue w
On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
> > As Viktor states RFC 4492 says if the client sends no TLS extension
> > containing the curves supported then the server can choose any supported
> > curve. So your fix is to continue when we reach the second iteration if
> > there a
On 23/03/15 11:54, Linsell, StevenX wrote:
> On 20/0315 15:51, Matt Caswell wrote:
>> On 20/03/15 12:44, Linsell, StevenX wrote:
>>> On Thu, Mar 19, 2015, Steve Linsell wrote:
>>> Following further testing I see identical failures in the master branch
>>> using the \
>>> following cipher/pr
On 20/0315 15:51, Matt Caswell wrote:
>On 20/03/15 12:44, Linsell, StevenX wrote:
>> On Thu, Mar 19, 2015, Steve Linsell wrote:
>> >
>> Following further testing I see identical failures in the master branch
>> using the \
>> following cipher/protocol combinations:
>> ECDH-ECDSA-AES128-SHA
On Sat, Mar 21, 2015 at 06:58:38AM +, Viktor Dukhovni wrote:
> > Don't check that the curve appears in the list of acceptable curves for the
> > peer, if they didn't send us such a list (for example this will always be
> > the case in SSL3)
>
> Are you sure that's a bug. I recall a recent di
On Fri, Mar 20, 2015 at 03:51:17PM +, Matt Caswell wrote:
> >> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and
> >> s_server on
> >> the master branch. (cloned at commit
> >> f7683aaf36341dc65672ac2ccdbfd4a232e3626d) and then retested with a more
> >> recent clone: (commit
On 20/03/15 12:44, Linsell, StevenX wrote:
> On Thu, Mar 19, 2015, Steve Linsell wrote:
>>
>> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server
>> on
>> the master branch. (cloned at commit
>> f7683aaf36341dc65672ac2ccdbfd4a232e3626d) and then retested with a more
>> r
On Thu, Mar 19, 2015, Steve Linsell wrote:
>
> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server on
> the master branch. (cloned at commit
> f7683aaf36341dc65672ac2ccdbfd4a232e3626d) and then retested with a more
> recent clone: (commit da27006df06853a33b132133699a7aa9d4
I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server on
the master branch. (cloned at commit f7683aaf36341dc65672ac2ccdbfd4a232e3626d)
and then retested with a more recent clone: (commit
da27006df06853a33b132133699a7aa9d4277920).
We are running a test suite that tests all
11 matches
Mail list logo
