No.
The deprecated functions are not going away any time soon but there is
no direct replacement.
Pauli
On 21/9/21 6:46 am, Ken Goldman wrote:
... and RSA_get0_factors.
I know about EVP_PKEY_get_bn_param(). However, that allocates new
bignums. Therefore, the caller has to say, if
... and RSA_get0_factors.
I know about EVP_PKEY_get_bn_param(). However, that allocates new bignums.
Therefore, the caller has to say, if >3.0.0, free them, else don't.
The deprecated get0 functions just returned pointers that did not have to be
separately freed.
Is there a call to pass in
Hi Tomas,
It looks correct. This is on the ARM target:
sc3822> find / -name libcrypto.so.3 -print
/lib/libcrypto.so.3
sc3822> strings /lib/libcrypto.so.3 | grep /ssl
/ssl-3//ct_log_list.cnf
OPENSSLDIR: "/ssl-3/"
/ssl-3/
/ssl-3//private
/ssl-3//certs
/ssl-3//cert.pem
sc3822>
I will open an
Thanks Matt!
From: openssl-users on behalf of Matt
Caswell
Sent: Monday, September 20, 2021 7:43 PM
To: openssl-users@openssl.org
Subject: [EXTERNAL] Re:
On 20/09/2021 14:59, Shivakumar Poojari wrote:
> But how do i manage "f" paramater which is highlighted
On 20/09/2021 14:59, Shivakumar Poojari wrote:
But how do i manage "f" paramater which is highlighted in #define
You don't. We no longer use F codes. Just drop that value.
Matt
please suggest,
thanks,
shiva kumar
Notice: This e-mail together with any attachments may contain
Hi
#define of BIOerr and BUFerr is deprecated in openssl3.0
# ifndef OPENSSL_NO_DEPRECATED_3_0
#define BIOerr(f, r) ERR_raise_data(ERR_LIB_BIO, (r), NULL)
# define BUFerr(f, r) ERR_raise_data(ERR_LIB_BUF, (r), NULL)
#endif
The BIOerr and BUFerr are used in the code something like below
Hello,
Usually you don't, and if you compile it against the same major release, no
problems happen.
I'd suggest you to look at the backtrace.
On Mon, Sep 20, 2021 at 3:03 AM Shariful Alam wrote:
> Hello,
> I have installed OpenSSL 1.1.1c. I'm trying to make a custom OpenSSL
> engine for RSA.
This is really weird. The OPENSSLDIR as in the Makefile should be
applied during the build. If you do strings does
it show the ssl-3? Is it possible that you have some other build of
openssl-3.0 with incorrect (default) OPENSSLDIR lying on the system
somewhere?
Please open an GitHub issue so we
As this requires support for Attribute Certificates which is not
currently present in OpenSSL neither RFC 5755 is supported.
Regards,
Tomas
On Sat, 2021-09-18 at 11:34 +0800, 215104920 via openssl-users wrote:
> Hi. There
> Could you give me some help?
> Thanks a lot.
>
>
> BRs
> Mystic
