:01 PM, Matt Caswell <m...@openssl.org> wrote:
>
>
>
> On 01/03/17 23:52, Suman Paul wrote:
>> What I have seen in my trials with s_server and s_client is that if run
>> s_server with an ECDSA cert/key and I specify one RSA and one ECDSA
>> cipher with the
a RSA
cipher. RSA cipher fail shows up at the s_server as
140480482967256:error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared
cipher:s3_srvr.c:1417:
Your thoughts on this?
Suman
> On Mar 1, 2017, at 1:51 AM, Matt Caswell <m...@openssl.org> wrote:
>
>
>
> On 01/03
gt; On 01/03/17 05:55, Suman Paul wrote:
>> I have been looking at WebRTC DTLS handshake and don’t understand the
>> logic of how it works.
>>
>> My Firefox client has support for both RSA and ECDSA ciphers while my
>> DTLS server only supports DHE-RSA-AES128-SHA and has
I have been looking at WebRTC DTLS handshake and don’t understand the logic of
how it works.
My Firefox client has support for both RSA and ECDSA ciphers while my DTLS
server only supports DHE-RSA-AES128-SHA and has a RSA key. I see that Firefox
sends a ECDSA key during client hello. What ends
Hi,
I have a server that implements DTLS using OpenSSL 1.0.1 but supports only RSA
keys as of today. I want to add support to this server to accept EC keys to be
able to implement the newer ECDHE-ECDSA cipher suites while retaining support
for RSA. Any pointers as to how to go about this?
