Hi all, I would like to ask for advise.
We are building a firefox extension and we are using our own
implementation of SSL server and client implemented closely to the ssl
sample (security\nss\cmd\SSLsample). We are not using PSM socket
provider implementation.
All certificates (CAs and
Julien Pierre napsal:
NSS only supports RSA ECDHE cipher suites on the client side at this
time, so this is expected. If you are using NSS on the server side, you
need to enable alternate cipher suites - and of course you need to
enable them on the client side as well.
Thanks for advise,
Honzab,
Honzab wrote:
Julien Pierre napsal:
NSS only supports RSA ECDHE cipher suites on the client side at this
time, so this is expected. If you are using NSS on the server side, you
need to enable alternate cipher suites - and of course you need to
enable them on the client side as well.
[EMAIL PROTECTED] wrote:
Hi,
HASH_* APIs provide a good wrapper for the hashing algorithms.
But secsign.c does not use any of these. It instead calls
create/update/end directly on the hash context.
Would it be better to use HASH_* APIs in secsign.c?
We could use HASH_* APIs in secsign.c.
4 matches
Mail list logo