Closed
Bug 1441121
Opened 7 years ago
Closed 7 years ago
OpenSSL server/NSS client - Resumption with session id and 8k keys
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: sdordevi, Unassigned)
References
Details
Attachments
(1 file)
60.83 KB,
application/gzip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20180118150322
Steps to reproduce:
Seems that resumption with session id in TLS1.2 with DHE kex algorithms, using 8k RSA keys and 8k dh params is not working.
Looks like a nss problem, utility used for client side or library itself.
Version of software:
nss-3.34.0
openssl-1.0.2k
Steps to Reproduce:
1. unpack attached certs and dh parms, or generate on your own
2. prepare nss database
# mkdir nssdb/
# certutil -N --empty-password -d sql:./nssdb
# certutil -A -d sql:./nssdb -n ca -t 'cCT,,' -a -i ca/cert.pem
# pk12util -i rsa-client/bundle.p12 -d sql:./nssdb -W ''
# certutil -L -d sql:./nssdb
3. Start openssl server
# openssl s_server -www -key rsa-server/key.pem -cert rsa-server/cert.pem -CAfile ca/cert.pem -cipher DHE-RSA-AES128-SHA256 -no_ticket -dhparam dhparm8192.pem >server.log 2>server.err &
4. run strsclnt
/usr/lib64/nss/unsupported-tools/strsclnt -p 4433 -d sql:./nssdb/ -c 100 -P 20 localhost
Output will show next:
strsclnt: -- SSL: Server Certificate Validated.
strsclnt: 0 cache hits; 1 cache misses, 0 cache not reusable
0 stateless resumes
It's expected that should contain '80 cache hits'. Which is a results with 2k RSA keys and dh params.
Same results with forced client side certificate, which is also expected to work with 8k keys.
Actual results:
No resumption with session id, with DHE and 8k RSA keys and 8k dh params.
0 cache hits.
Expected results:
Resumption with session id is working, with DHE and 8k RSA keys and 8k dh params.
80 cache hits.
Regular and client side cert. without resumption are working as expected with 8k keys and 8k dh params with openssl as server, and also resumption (ticket and session id) with RSA kex.
So with 8k keys, 8k dh params using DHE kex and resumption is expected to work.
Updated•7 years ago
|
Priority: -- → P3
Comment 1•7 years ago
|
||
NSS doesn't accept RSA or DH keys with more than 8192 bits. The DH key share here has 8196. By now there's an error code for this that didn't exist in 3.34.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•