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,
Thank you Salz Rich for the confirmation.
So, whether application can perform manual TLS handshakes when
SOCK_SEQPACKET is used ?
Regards,
Sanjaya
On Tue, Feb 28, 2017 at 7:03 PM, Salz, Rich wrote:
> > But these calls don't work when SOCK_SEQPACKET (one-to-many connections)
> is used. Does
> But these calls don't work when SOCK_SEQPACKET (one-to-many connections) is
> used. Does openssl provide any alternatives for these calls ? Or an
> application need to perform the TLS handshakes manually ?
This is not supported, and there are no demo's available.
--
openssl-users mailing list
On Tue, Feb 28, 2017, Tobias Nie?en wrote:
> Hello,
>
> we are currently discussing support for RSASSA-PSS padding in the
> node.js built-in crypto module:
> https://github.com/nodejs/node/issues/1127
>
> So far, the crypto module uses the older EVP_Sign/EVP_Verify APIs,
> which do not support s
Hello,
we are currently discussing support for RSASSA-PSS padding in the
node.js built-in crypto module:
https://github.com/nodejs/node/issues/1127
So far, the crypto module uses the older EVP_Sign/EVP_Verify APIs, which
do not support specifying
the padding (and salt length). We considered s
Hello,
I understand that when implementing TLS over SCTP, if socket is opened with
SOCK_STREAM (one-to-one connection), then normal openssl calls (SSL_accept,
SSL_connect) can be used for TLS handshakes in a client/server program.
But these calls don't work when SOCK_SEQPACKET (one-to-many connect
