Lines Matching refs:I
204 All of the functions described on this page that have a I<TYPE> of B<DH>, B<DSA>
216 brevity the term "B<I<TYPE>> functions" will be used below to collectively
220 Some operations have additional variants that take a library context I<libctx>
221 and a property query string I<propq>. The B<X509>, B<X509_REQ> and B<X509_CRL>
241 PKCS#5 v2.0 password based encryption algorithms. The I<cipher> argument
244 I<cipher> is NULL then no encryption is used and a PKCS#8 PrivateKeyInfo
250 to use is specified in the I<nid> parameter and should be the NID of the
284 key parameters, it will be a PKCS#3 DHparameter structure. I<These functions
322 The I<bp> BIO parameter (if present) specifies the BIO to read from
325 The I<fp> FILE parameter (if present) specifies the FILE pointer to
328 The PEM read functions all take an argument I<B<TYPE> **x> and return
329 a I<B<TYPE> *> pointer. Where I<B<TYPE>> is whatever structure the function
330 uses. If I<x> is NULL then the parameter is ignored. If I<x> is not
331 NULL but I<*x> is NULL then the structure returned will be written
332 to I<*x>. If neither I<x> nor I<*x> is NULL then an attempt is made
333 to reuse the structure at I<*x> (but see BUGS and EXAMPLES sections).
334 Irrespective of the value of I<x> a pointer to the structure is always
339 The PEM functions which write private keys take an I<enc> parameter
344 The I<cb> argument is the callback to use when querying for the pass
347 For the PEM write routines if the I<kstr> parameter is not NULL then
348 I<klen> bytes at I<kstr> are used as the passphrase and I<cb> is
351 If the I<cb> parameters is set to NULL and the I<u> parameter is not
352 NULL then the I<u> parameter is interpreted as a NUL terminated string
353 to use as the passphrase. If both I<cb> and I<u> are NULL then the
363 I<buf> is the buffer to write the passphrase to. I<size> is the maximum
364 length of the passphrase (i.e. the size of buf). I<rwflag> is a flag
367 for it twice) if I<rwflag> is 1. The I<u> parameter has the same
368 value as the I<u> parameter passed to the PEM routine. It allows
371 I<must> return the number of characters in the passphrase or -1 if
376 operation. If this is the case and I<libctx> and I<propq> parameters have been
404 this is a bug because an attempt will be made to reuse the data at I<x>
424 The line beginning with I<Proc-Type> contains the version and the
425 protection on the encapsulated data. The line beginning I<DEK-Info>
432 initialization vector is passed to EVP_BytesToKey() as the I<salt>
435 password is passed to EVP_BytesToKey() using the I<data> and I<datal>
439 The I<key> derived by EVP_BytesToKey() along with the original initialization
440 vector is then used to decrypt the encrypted data. The I<iv> produced by
468 where I<x> already contains a valid certificate, may not work, whereas:
473 is guaranteed to work. It is always acceptable for I<x> to contain a newly
