1 .\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.22)
4 .\" ========================================================================
5 .de Sp \" Vertical space (when we can't use .PP)
9 .de Vb \" Begin verbatim text
14 .de Ve \" End verbatim text
18 .\" Set up some character translations and predefined strings. \*(-- will
19 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
20 .\" double quote, and \*(R" will give a right double quote. \*(C+ will
21 .\" give a nicer C++. Capital omega is used to do unbreakable dashes and
22 .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
23 .\" nothing in troff, for use with C<>.
25 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
43 .\" Escape single quotes in literal strings from groff's Unicode transform.
47 .\" If the F register is turned on, we'll generate index entries on stderr for
48 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
49 .\" entries marked with X<> in POD. Of course, you'll have to process the
50 .\" output yourself in some meaningful fashion.
53 . tm Index:\\$1\t\\n%\t"\\$2"
63 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
64 .\" Fear. Run. Save yourself. No user-serviceable parts.
65 . \" fudge factors for nroff and troff
74 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
80 . \" simple accents for nroff and troff
90 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
91 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
92 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
93 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
94 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
95 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
97 . \" troff and (daisy-wheel) nroff accents
98 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
99 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
100 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
101 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
102 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
103 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
104 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
105 .ds ae a\h'-(\w'a'u*4/10)'e
106 .ds Ae A\h'-(\w'A'u*4/10)'E
107 . \" corrections for vroff
108 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
109 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
110 . \" for low resolution devices (crt and lpr)
111 .if \n(.H>23 .if \n(.V>19 \
124 .\" ========================================================================
126 .IX Title "RSA_get_ex_new_index 3"
127 .TH RSA_get_ex_new_index 3 "2012-05-10" "1.0.1c" "OpenSSL"
128 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
129 .\" way too many mistakes in technical documents.
133 RSA_get_ex_new_index, RSA_set_ex_data, RSA_get_ex_data \- add application specific data to RSA structures
135 .IX Header "SYNOPSIS"
137 \& #include <openssl/rsa.h>
139 \& int RSA_get_ex_new_index(long argl, void *argp,
140 \& CRYPTO_EX_new *new_func,
141 \& CRYPTO_EX_dup *dup_func,
142 \& CRYPTO_EX_free *free_func);
144 \& int RSA_set_ex_data(RSA *r, int idx, void *arg);
146 \& void *RSA_get_ex_data(RSA *r, int idx);
148 \& typedef int CRYPTO_EX_new(void *parent, void *ptr, CRYPTO_EX_DATA *ad,
149 \& int idx, long argl, void *argp);
150 \& typedef void CRYPTO_EX_free(void *parent, void *ptr, CRYPTO_EX_DATA *ad,
151 \& int idx, long argl, void *argp);
152 \& typedef int CRYPTO_EX_dup(CRYPTO_EX_DATA *to, CRYPTO_EX_DATA *from, void *from_d,
153 \& int idx, long argl, void *argp);
156 .IX Header "DESCRIPTION"
157 Several OpenSSL structures can have application specific data attached to them.
158 This has several potential uses, it can be used to cache data associated with
159 a structure (for example the hash of some part of the structure) or some
160 additional data (for example a handle to the data in an external library).
162 Since the application data can be anything at all it is passed and retrieved
163 as a \fBvoid *\fR type.
165 The \fB\f(BIRSA_get_ex_new_index()\fB\fR function is initially called to \*(L"register\*(R" some
166 new application specific data. It takes three optional function pointers which
167 are called when the parent structure (in this case an \s-1RSA\s0 structure) is
168 initially created, when it is copied and when it is freed up. If any or all of
169 these function pointer arguments are not used they should be set to \s-1NULL\s0. The
170 precise manner in which these function pointers are called is described in more
171 detail below. \fB\f(BIRSA_get_ex_new_index()\fB\fR also takes additional long and pointer
172 parameters which will be passed to the supplied functions but which otherwise
173 have no special meaning. It returns an \fBindex\fR which should be stored
174 (typically in a static variable) and passed used in the \fBidx\fR parameter in
175 the remaining functions. Each successful call to \fB\f(BIRSA_get_ex_new_index()\fB\fR
176 will return an index greater than any previously returned, this is important
177 because the optional functions are called in order of increasing index value.
179 \&\fB\f(BIRSA_set_ex_data()\fB\fR is used to set application specific data, the data is
180 supplied in the \fBarg\fR parameter and its precise meaning is up to the
183 \&\fB\f(BIRSA_get_ex_data()\fB\fR is used to retrieve application specific data. The data
184 is returned to the application, this will be the same value as supplied to
185 a previous \fB\f(BIRSA_set_ex_data()\fB\fR call.
187 \&\fB\f(BInew_func()\fB\fR is called when a structure is initially allocated (for example
188 with \fB\f(BIRSA_new()\fB\fR. The parent structure members will not have any meaningful
189 values at this point. This function will typically be used to allocate any
190 application specific structure.
192 \&\fB\f(BIfree_func()\fB\fR is called when a structure is being freed up. The dynamic parent
193 structure members should not be accessed because they will be freed up when
194 this function is called.
196 \&\fB\f(BInew_func()\fB\fR and \fB\f(BIfree_func()\fB\fR take the same parameters. \fBparent\fR is a
197 pointer to the parent \s-1RSA\s0 structure. \fBptr\fR is a the application specific data
198 (this wont be of much use in \fB\f(BInew_func()\fB\fR. \fBad\fR is a pointer to the
199 \&\fB\s-1CRYPTO_EX_DATA\s0\fR structure from the parent \s-1RSA\s0 structure: the functions
200 \&\fB\f(BICRYPTO_get_ex_data()\fB\fR and \fB\f(BICRYPTO_set_ex_data()\fB\fR can be called to manipulate
201 it. The \fBidx\fR parameter is the index: this will be the same value returned by
202 \&\fB\f(BIRSA_get_ex_new_index()\fB\fR when the functions were initially registered. Finally
203 the \fBargl\fR and \fBargp\fR parameters are the values originally passed to the same
204 corresponding parameters when \fB\f(BIRSA_get_ex_new_index()\fB\fR was called.
206 \&\fB\f(BIdup_func()\fB\fR is called when a structure is being copied. Pointers to the
207 destination and source \fB\s-1CRYPTO_EX_DATA\s0\fR structures are passed in the \fBto\fR and
208 \&\fBfrom\fR parameters respectively. The \fBfrom_d\fR parameter is passed a pointer to
209 the source application data when the function is called, when the function returns
210 the value is copied to the destination: the application can thus modify the data
211 pointed to by \fBfrom_d\fR and have different values in the source and destination.
212 The \fBidx\fR, \fBargl\fR and \fBargp\fR parameters are the same as those in \fB\f(BInew_func()\fB\fR
213 and \fB\f(BIfree_func()\fB\fR.
215 .IX Header "RETURN VALUES"
216 \&\fB\f(BIRSA_get_ex_new_index()\fB\fR returns a new index or \-1 on failure (note 0 is a valid
219 \&\fB\f(BIRSA_set_ex_data()\fB\fR returns 1 on success or 0 on failure.
221 \&\fB\f(BIRSA_get_ex_data()\fB\fR returns the application data or 0 on failure. 0 may also
222 be valid application data but currently it can only fail if given an invalid \fBidx\fR
225 \&\fB\f(BInew_func()\fB\fR and \fB\f(BIdup_func()\fB\fR should return 0 for failure and 1 for success.
227 On failure an error code can be obtained from \fIERR_get_error\fR\|(3).
230 \&\fB\f(BIdup_func()\fB\fR is currently never called.
232 The return value of \fB\f(BInew_func()\fB\fR is ignored.
234 The \fB\f(BInew_func()\fB\fR function isn't very useful because no meaningful values are
235 present in the parent \s-1RSA\s0 structure when it is called.
237 .IX Header "SEE ALSO"
238 \&\fIrsa\fR\|(3), \fICRYPTO_set_ex_data\fR\|(3)
241 \&\fIRSA_get_ex_new_index()\fR, \fIRSA_set_ex_data()\fR and \fIRSA_get_ex_data()\fR are
242 available since SSLeay 0.9.0.