MirBSD manpage: CRYPTO_get_ex_data(3), CRYPTO_set_ex_data(3)



     CRYPTO_set_ex_data, CRYPTO_get_ex_data - internal applica-
     tion specific data functions


      int CRYPTO_set_ex_data(CRYPTO_EX_DATA *r, int idx, void *arg);

      void *CRYPTO_get_ex_data(CRYPTO_EX_DATA *r, int idx);


     Several OpenSSL structures can have application specific
     data attached to them. These functions are used internally
     by OpenSSL to manipulate application specific data attached
     to a specific structure.

     These functions should only be used by applications to mani-
     pulate CRYPTO_EX_DATA structures passed to the new_func(),
     free_func() and dup_func() callbacks: as passed to
     RSA_get_ex_new_index() for example.

     CRYPTO_set_ex_data() is used to set application specific
     data, the data is supplied in the arg parameter and its pre-
     cise meaning is up to the application.

     CRYPTO_get_ex_data() is used to retrieve application
     specific data. The data is returned to the application, this
     will be the same value as supplied to a previous
     CRYPTO_set_ex_data() call.


     CRYPTO_set_ex_data() returns 1 on success or 0 on failure.

     CRYPTO_get_ex_data() returns the application data or 0 on
     failure. 0 may also be valid application data but currently
     it can only fail if given an invalid idx parameter.

     On failure an error code can be obtained from


     RSA_get_ex_new_index(3), DSA_get_ex_new_index(3),


     CRYPTO_set_ex_data() and CRYPTO_get_ex_data() have been
     available since SSLeay 0.9.0.

MirBSD #10-current         2005-02-05                           1

Generated on 2022-12-24 01:00:14 by $MirOS: src/scripts/roff2htm,v 1.113 2022/12/21 23:14:31 tg Exp $ — This product includes material provided by mirabilos.

These manual pages and other documentation are copyrighted by their respective writers; their sources are available at the project’s CVSweb, AnonCVS and other mirrors. The rest is Copyright © 2002–2022 MirBSD.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.

Kontakt / Impressum & Datenschutzerklärung