You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the conclusion arrived at in #32 (de-emphasizing oqs-openssl111 maintenance and support) has been reverted in yesterday's team meeting, this issue is to track tasks to re-activate interop testing between oqs-openssl111 and oqs-provider.
Implications:
Interop test scripts need to be parameterized to
o permit switching to different docker images (oqs-openssl111-curl had been used but has changed in the meantime to oqs-provider-curl)
o permit switching off RFC data encoding testing as that is not implemented in oqs-openssl111 (or are you willing to add that also to oqs-openssl111, @bhess?)
We agreed to terminate support of oqs-openssl111 and have significantly more functionality in oqs-provider, so closing as this is a truly pointless issue now.
As the conclusion arrived at in #32 (de-emphasizing oqs-openssl111 maintenance and support) has been reverted in yesterday's team meeting, this issue is to track tasks to re-activate interop testing between oqs-openssl111 and oqs-provider.
Implications:
o permit switching to different docker images (oqs-openssl111-curl had been used but has changed in the meantime to oqs-provider-curl)
o permit switching off RFC data encoding testing as that is not implemented in oqs-openssl111 (or are you willing to add that also to oqs-openssl111, @bhess?)
The text was updated successfully, but these errors were encountered: