Nicola Tuveri
Nicola Tuveri
I don't think I can push pyca/cryptography#7829 further: they'd prefer to change the test input rather than expecting a different error. Also, the errors I see on their master branch...
> Here is the tentative PR against their `38.0.x` branch (their `master` does not pass tests): [pyca/cryptography#7829](https://github.com/pyca/cryptography/pull/7829) @levitte @mspncp Here is the log of running the `test_external_pyca` on the current...
> Here is the tentative PR against their `38.0.x` branch (their `master` does not pass tests): [pyca/cryptography#7829](https://github.com/pyca/cryptography/pull/7829) I just closed pyca/cryptography#7829 in favor of pyca/cryptography#7833, as they requested to target...
@slontis makes a very good point. Hopefully they will be willing to backport to the 38.0.x branch once it lands on main..
Thanks @levitte ! Your suggestion does provide more information, but I am unsure on how to use to pinpoint the issue. Here is the new log file: [:paperclip: `newlog.txt`](https://github.com/openssl/openssl/files/10073499/newlog.txt)
The problems I was seeing when testing against `pyca-cryptography/main` where due to the issue fixed recently in `openssl-3.1` via a48081ac606c7bbce5e3adad7ad2d6dfc1b4f215. It should be soon possible to merge pyca/cryptography#7833, the patch...
Just pushed a commit that bumps the `pyca-cryptography` submodule to the just released `38.0.4` version, which includes the backport of pyca/cryptography#7833.
The vote openssl/technical-policies#59 is now closed as accepted. We can proceed with the regular review process to merge this. @hlandau I believe I addressed your change request: care to review...
@vdukhovni this is a relevant discussion https://github.com/openssl/openssl/pull/23240#issuecomment-1917532043