-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: Run TLS tests also when forcing all server operations on token #427
Conversation
Have you tried importing #424 to see if that improves something ? |
If that does not help it may be some issue with the group aliases, OpenSSL is quite baroque and uses multiple names for ciphers in some places, and then insists on specific names among the aliases in other places. |
Good point. Tried now, but the error is the same. |
Signed-off-by: Jakub Jelen <[email protected]>
This commit adds CKA_DERIVE flag in server's private key template which is required by optee subsystem. Tested TLS1.2 with the change. Signed-off-by: Kshitiz Varshney <[email protected]>
This has basically been done in #446, so I am going to close this PR. |
This is actually not true. The #446 added just one test forcing the operation on the token, while here I added all the existing TLS tests to be executed. But all of them seems to work now in the way how they are written. When I add the test from #449, it fails as described in the issue, but the
|
Description
This is likely the missing bit we had when trying to reproduce the issue #395. These are changes forcing all the TLS operations on token for the s_server. The s_client fails the basic key verification, because it is likely not correctly imported to the provider (?).
With this configuration the TLS 1.3 with RSA and ECDSA host certs work ok, TLS 1.2 with RSA too, but TLS 1.2 with ECDSA fails with
I was not able to figure out what OpenSSL needs at this point. I did not see any failures on the pkcs11 nor on the pkcs11 provider layer.
Checklist
Reviewer's checklist: