> Is it valid to call:
>
> size_t size = SSL_get_finished(ssl, NULL, 0);
No
> Because SSL_get_finished invokes memcpy even if the size is 0, so is the
> undefined behaviour?
Yes
> Creating a temporary buffer and then consolidating the
> vector is a problem because of the performance cost associated with
> memory copy.
Did you actually benchmark this or do you just think this is the case?
Consider that SSL_write/read will normally do something like AES or
Chapoly on your C
SLES 10 is 13 years old and stopped receiving (security) updates three
years ago.
The best course of action here is to upgrade the operating system.
-Marian
Am 22.05.19 um 11:16 schrieb pcraghavendra.pra...@dell.com:
> Hi Team,
>
>
>
> Need help on the openssl library.
>
> We want to upgrad
sToKey algorithm but thank you for providing
> that page. i suspect it might be easier to have the folks encrypting
> the data specifiy an IV rather than trying to figure out how to
> implement EVP_BytesToKey in python. its not inconsequential.
>
> On Mon, Mar 25, 2019 at 5:
Well let's just read the man pages, shall we?
>-kfile filename
> Read the password to derive the key from the first line of filename.
Then
>-md digest
> Use the specified digest to create the key from the passphrase.
> The default algorithm is sha-256.
And
> -iv IV
> ...
"Stitching" is an optimization where you have algorithm A (e.g. AES-CBC)
and algorithm B (e.g. HMAC-SHA2) working on the same data, and you
interleave the instructions of A and B. (This can improve performance by
increasing port and EU utilization relative to running A and B
sequentially).
I belie
On 23.05.2018 20:39, Michael Wojcik wrote:
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
Of redpath
Sent: Wednesday, May 23, 2018 13:08
To: openssl-users@openssl.org
Subject: Re: [openssl-users] PEM_write_bio_RSAPrivateKey assure
Randomness of PK
SO if I add this RAND
