> On Aug 9, 2019, at 3:42 PM, Osama Mazahir via openssl-users
> wrote:
>
> Is there a way to serialize and deserialize the ssl_st state (i.e. including
> any child objects)?
>
> Background: I would like to handoff all the SSL state (along my own managed
> state, file descriptors, etc) to
Not without a lot of work. It’s not part of the current API.
We have tried doing an internal implementation; it was over 1K of new code, and
it wasn’t complete.
--
-Todd Short
// tsh...@akamai.com
// “One if by land, two if by sea, threeif by the Internet."
> On Aug 9, 2019, at 3:42 PM, Osama
Is there a way to serialize and deserialize the ssl_st state (i.e. including
any child objects)?
Background: I would like to handoff all the SSL state (along my own managed
state, file descriptors, etc) to another Linux running process (I will handle
the IPC handoff). The connection already
On 09/08/2019 14:33, Dan Heinz wrote:
> I have a static library using OpenSSL (built as static library with the
> no-pinshared parameter in the configuration) that is then included in a DLL
> that
> gets loaded and unloaded many times by the calling application. Now that the
> code is in
I have a static library using OpenSSL (built as static library with the
no-pinshared parameter in the configuration) that is then included in a DLL
that gets loaded and unloaded many times by the calling application. Now that
the code is in 1.1.1c to allow me to manually shutdown the OpenSSL
Hi,
Your issue is not with BIO_read(), but with the differing signedness of the
char type on your two platforms.
On your PPC platform the char type defaults to unsigned, on your x86 platform
it is signed. The %x format expects an unsigned int, so on x86 the signed char
values are being
Hi Experts,
I am using openssl 1.0.2
I recently moved my app from a PPC to x86 platform (application is compiled on
the respective platform) where I met an issue with BIO_read().
I read a 20bytes of data using BIO_read like following..
int res = BIO_read(bio, buf, 20);char *ptr = buf;
The
