However, I was wondering if anyone has ported/refactored the pkcs11
engine stuff for OpenSSL 3.0 already? is this on the TODO list for
the OpenSC/pkcs11 team? If I wanted to try to refactor the
opensc-pkcs11 module, how would I start?
PKCS #11 support is one (of many) possible items
Hi,
On 17/06/21 15:36, Matt Caswell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 beta 1 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in beta.
Steffen Nurpmeso wrote in
<20210617151209.s_znu%stef...@sdaoden.eu>:
|Matt Caswell wrote in
| <33db69e0-0f9b-c559-43f7-e5a2f85a4...@openssl.org>:
||On 17/06/2021 15:43, Steffen Nurpmeso wrote:
||> Fyi, i have $PERL5OPT=-C permanently in my environment, in
||> conjunction with
Matt Caswell wrote in
<33db69e0-0f9b-c559-43f7-e5a2f85a4...@openssl.org>:
|On 17/06/2021 15:43, Steffen Nurpmeso wrote:
|> Fyi, i have $PERL5OPT=-C permanently in my environment, in
|> conjunction with LC_ALL=en_US.utf8 this results in the build error
|> as below. Prefixing LC_ALL=C fixes
On 17/06/2021 15:43, Steffen Nurpmeso wrote:
Fyi, i have $PERL5OPT=-C permanently in my environment, in
conjunction with LC_ALL=en_US.utf8 this results in the build error
as below. Prefixing LC_ALL=C fixes this.
Thanks. I submitted this as an issue on github here:
Hello.
Matt Caswell wrote in
<20210617133633.ga24...@openssl.org>:
...
| OpenSSL version 3.0 beta 1 released
...
Congratulations after a lot of work!
Fyi, i have $PERL5OPT=-C permanently in my environment, in
conjunction with LC_ALL=en_US.utf8 this results in the build error
as below.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
OpenSSL version 3.0 beta 1 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
https://www.openssl.org/
OpenSSL 3.0 is currently in beta.
OpenSSL 3.0 beta 1 has now been made available.
