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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Johannes Bauer <dfnsonfsduifb@xxxxxx>, "openssl-users@xxxxxxxxxxx" <openssl-users@xxxxxxxxxxx>
Subject: Re: Preferred way of passing user context void* inside SSL*
From: "Salz, Rich via openssl-users" <openssl-users@xxxxxxxxxxx>
Date: Wed, 23 Oct 2019 13:21:54 +0000
Accept-language: en-US
In-reply-to: <084d778c-2cdc-1169-e42b-a31f92a6670b@gmx.de>
References: <084d778c-2cdc-1169-e42b-a31f92a6670b@gmx.de>
Reply-to: "Salz, Rich" <rsalz@xxxxxxxxxx>
User-agent: Microsoft-MacOutlook/10.1e.0.191013

>    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)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Preferred way of passing user context void* inside SSL*
  - From: Viktor Dukhovni
- Re: Preferred way of passing user context void* inside SSL*
  - From: Johannes Bauer

References:
- Preferred way of passing user context void* inside SSL*
  - From: Johannes Bauer

Prev by Date: Preferred way of passing user context void* inside SSL*
Next by Date: Re: Preferred way of passing user context void* inside SSL*
Previous by thread: Preferred way of passing user context void* inside SSL*
Next by thread: Re: Preferred way of passing user context void* inside SSL*
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux