-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Test failures with openssl 3.0.0 alpha 15 (quictls fork) #38373
Comments
richardlau
changed the title
Test failures with openssl
Test failures with openssl 3.0.0 alpha 15 (quictls fork)
Apr 23, 2021
I'm looking into these issues are part of the work of statically linking quictls/openssl 3.0.0-alpha15+quic. |
danbev
added a commit
to danbev/openssl
that referenced
this issue
Apr 28, 2021
This commit sets the error mark before calling d2i_X509_SIG and clear it if that function call is successful. The motivation for this is that if d2i_X509_SIG returns NULL then the else clause will be entered and d2i_PKCS8_PRIV_KEY_INFO will be called. If d2i_X509_SIG raised any errors those error will be on the error stack when d2i_PKCS8_PRIV_KEY_INFO gets called, and even if it returns successfully those errors will still be on the error stack. We ran into this issue when upgrading Node.js to 3.0.0-alpha15. More details can be found in the ref links below. Refs: nodejs/node#38373 Refs: https://github.com/danbev/learning-libcrypto/blob/master/notes/wrong-tag-issue2.md
1 task
danbev
added a commit
to danbev/node
that referenced
this issue
Apr 28, 2021
This commit skips some test when OpenSSL 3.0.0-alpha-15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373
danbev
added a commit
to danbev/node
that referenced
this issue
May 3, 2021
This commit skips some test when OpenSSL 3.0.0-alpha-15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373
danbev
added a commit
to danbev/node
that referenced
this issue
May 3, 2021
This commit skips some test when OpenSSL 3.0.0-alpha-15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373
danbev
added a commit
to danbev/node
that referenced
this issue
May 6, 2021
This commit skips some test when OpenSSL 3.0.0-alpha-15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373
richardlau
pushed a commit
to danbev/node
that referenced
this issue
May 6, 2021
This commit skips some test when OpenSSL 3.0.0-alpha15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373 PR-URL: nodejs#38451 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
openssl-machine
pushed a commit
to openssl/openssl
that referenced
this issue
May 9, 2021
This commit sets the error mark before calling d2i_X509_SIG and clear it if that function call is successful. The motivation for this is that if d2i_X509_SIG returns NULL then the else clause will be entered and d2i_PKCS8_PRIV_KEY_INFO will be called. If d2i_X509_SIG raised any errors those error will be on the error stack when d2i_PKCS8_PRIV_KEY_INFO gets called, and even if it returns successfully those errors will still be on the error stack. We ran into this issue when upgrading Node.js to 3.0.0-alpha15. More details can be found in the ref links below. Refs: nodejs/node#38373 Refs: https://github.com/danbev/learning-libcrypto/blob/master/notes/wrong-tag-issue2.md Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Ben Kaduk <kaduk@mit.edu> (Merged from #15067)
richardlau
pushed a commit
to richardlau/node-1
that referenced
this issue
May 14, 2021
PR-URL: nodejs#38451 Fixes: nodejs#38373 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
richardlau
pushed a commit
to richardlau/node-1
that referenced
this issue
May 14, 2021
This commit skips some test when OpenSSL 3.0.0-alpha15 is used as there is an issue that causes them to fail. This is only a temp solution until there is new OpenSSL release. Fixes: nodejs#38373 PR-URL: nodejs#38451 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
devnexen
pushed a commit
to devnexen/openssl
that referenced
this issue
Jul 7, 2021
This commit sets the error mark before calling d2i_X509_SIG and clear it if that function call is successful. The motivation for this is that if d2i_X509_SIG returns NULL then the else clause will be entered and d2i_PKCS8_PRIV_KEY_INFO will be called. If d2i_X509_SIG raised any errors those error will be on the error stack when d2i_PKCS8_PRIV_KEY_INFO gets called, and even if it returns successfully those errors will still be on the error stack. We ran into this issue when upgrading Node.js to 3.0.0-alpha15. More details can be found in the ref links below. Refs: nodejs/node#38373 Refs: https://github.com/danbev/learning-libcrypto/blob/master/notes/wrong-tag-issue2.md Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Ben Kaduk <kaduk@mit.edu> (Merged from openssl#15067)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While testing nodejs/build#2613 it looks like a number of tests fail when dynamically linking Node.js (88bc864) against https://github.com/quictls/openssl/tree/openssl-3.0.0-alpha15%2Bquic
These are not showing up on the CI yet because the openssl300 job is currently dynamically linking against openssl3.0.0-alpha14 (the previous alpha of the non-forked version).
cc @nodejs/crypto @jasnell
I've opened #38372 for
parallel/test-process-versions
.The text was updated successfully, but these errors were encountered: