Re: Preferred way of passing user context void* inside SSL*

2019-10-23 Thread Viktor Dukhovni
On Wed, Oct 23, 2019 at 01:21:54PM +, Salz, Rich via openssl-users wrote: > >Is there a way for me to piggyback a void* inside the SSL structure so > that I can access it from within the callback? > > Yes, you can use SSL_set_app_data and SSL_get_app_data which are documented > in h

Re: Preferred way of passing user context void* inside SSL*

2019-10-23 Thread Johannes Bauer
On 23.10.19 15:21, Salz, Rich wrote: >>Is there a way for me to piggyback a void* inside the SSL structure so > that I can access it from within the callback? > > Yes, you can use SSL_set_app_data and SSL_get_app_data which are documented > in https://github.com/openssl/openssl/pull/10216

Re: Preferred way of passing user context void* inside SSL*

2019-10-23 Thread Salz, Rich via openssl-users
>Is there a way for me to piggyback a void* inside the SSL structure so that I can access it from within the callback? Yes, you can use SSL_set_app_data and SSL_get_app_data which are documented in https://github.com/openssl/openssl/pull/10216 (and due to be merged to master soon)

Preferred way of passing user context void* inside SSL*

2019-10-23 Thread Johannes Bauer
Hi list, yet another question. In my process with TLS13-PSK, I've noticed that the PSK callback does not have a user-definable callback context value. However, the callback is passed the SSL* which I created when the session was established. Is there a way for me to piggyback a void* inside the S