-
I have tested the workarounds with a single global instance for AES and SHA-1 HMAC mentioned in this [comment](https://github.com/openssl/openssl/issues/17064#issuecomment-973058052) and this [comment…
-
Hi! I have a project that targets many platforms. Among them iOS and Android. Among my dependencies I have C++ projects like Ring. When I change the target on my VSCode settings like this:
```
"…
-
For a provider implementation of the RSA algorithm (asym-cipher & signature) one must implement the RSA padding schemes PKCS1, OAEP, PSS, X.931 (and maybe more).
In general, it is a good thing that…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
When I start the container for the BackEnd, I have this error :
`...
Backend Server | Pris…
-
I have built an OpenSSL TLS provider for mono. I have tested a couple of simple test csses on s390x and x86_64 and it seems okay. I am trying to determine what "flaws" OpenSSL may have with regard to …
-
NODE_OPTIONS=--openssl-legacy-provider yarn build
-
When trying to load certificates with `openssl storeutl` or `openssl cmp` from PKCS#12 files generated by the (Java-based) EJBCA, such as in the attached example [test_123456.zip](https://github.com/o…
DDvO updated
3 months ago
-
There are a number of TODOs in the code that suggest we should expect changes for OAEP support, but those changes do not seem to have happened. Is OAEP support complete, and therefore these TODOs are …
-
I used the tpm2-openssl https://github.com/tpm2-software/tpm2-openssl/tree/master with openssl to generate a CSR for signing. The below command worked fine
`openssl req -new -newkey rsa:2048 -out t…
-
Ever since upgrading to Node.js 18, we have needed to use the `--openssl-legacy-provider` flag in several locations. This is because some of our code (mostly tests and build steps) rely on legacy Open…