Deleted Added
full compact
EVP_PKEY_meth_new.3 (340704) EVP_PKEY_meth_new.3 (344604)
1.\" Automatically generated by Pod::Man 4.09 (Pod::Simple 3.35)
1.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35)
2.\"
3.\" Standard preamble:
4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v
7.if n .sp
8..
9.de Vb \" Begin verbatim text

--- 39 unchanged lines hidden (view full) ---

49.\" If the F register is >0, we'll generate index entries on stderr for
50.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
51.\" entries marked with X<> in POD. Of course, you'll have to process the
52.\" output yourself in some meaningful fashion.
53.\"
54.\" Avoid warning from groff about undefined register 'F'.
55.de IX
56..
2.\"
3.\" Standard preamble:
4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v
7.if n .sp
8..
9.de Vb \" Begin verbatim text

--- 39 unchanged lines hidden (view full) ---

49.\" If the F register is >0, we'll generate index entries on stderr for
50.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
51.\" entries marked with X<> in POD. Of course, you'll have to process the
52.\" output yourself in some meaningful fashion.
53.\"
54.\" Avoid warning from groff about undefined register 'F'.
55.de IX
56..
57.if !\nF .nr F 0
58.if \nF>0 \{\
59. de IX
60. tm Index:\\$1\t\\n%\t"\\$2"
57.nr rF 0
58.if \n(.g .if rF .nr rF 1
59.if (\n(rF:(\n(.g==0)) \{\
60. if \nF \{\
61. de IX
62. tm Index:\\$1\t\\n%\t"\\$2"
61..
63..
62. if !\nF==2 \{\
63. nr % 0
64. nr F 2
64. if !\nF==2 \{\
65. nr % 0
66. nr F 2
67. \}
65. \}
66.\}
68. \}
69.\}
70.rr rF
67.\"
68.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
69.\" Fear. Run. Save yourself. No user-serviceable parts.
70. \" fudge factors for nroff and troff
71.if n \{\
72. ds #H 0
73. ds #V .8m
74. ds #F .3m

--- 49 unchanged lines hidden (view full) ---

124. ds Th \o'LP'
125. ds ae ae
126. ds Ae AE
127.\}
128.rm #[ #] #H #V #F C
129.\" ========================================================================
130.\"
131.IX Title "EVP_PKEY_meth_new 3"
71.\"
72.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
73.\" Fear. Run. Save yourself. No user-serviceable parts.
74. \" fudge factors for nroff and troff
75.if n \{\
76. ds #H 0
77. ds #V .8m
78. ds #F .3m

--- 49 unchanged lines hidden (view full) ---

128. ds Th \o'LP'
129. ds ae ae
130. ds Ae AE
131.\}
132.rm #[ #] #H #V #F C
133.\" ========================================================================
134.\"
135.IX Title "EVP_PKEY_meth_new 3"
132.TH EVP_PKEY_meth_new 3 "2018-11-20" "1.0.2q" "OpenSSL"
136.TH EVP_PKEY_meth_new 3 "2019-02-26" "1.0.2r" "OpenSSL"
133.\" For nroff, turn off justification. Always turn off hyphenation; it makes
134.\" way too many mistakes in technical documents.
135.if n .ad l
136.nh
137.SH "NAME"
138EVP_PKEY_meth_new, EVP_PKEY_meth_free, EVP_PKEY_meth_copy, EVP_PKEY_meth_find,
139EVP_PKEY_meth_add0, EVP_PKEY_METHOD,
140EVP_PKEY_meth_set_init, EVP_PKEY_meth_set_copy, EVP_PKEY_meth_set_cleanup,

--- 183 unchanged lines hidden (view full) ---

324\&\fB\s-1EVP_PKEY_METHOD\s0\fR is a structure which holds a set of methods for a
325specific public key cryptographic algorithm. Those methods are usually
326used to perform different jobs, such as generating a key, signing or
327verifying, encrypting or decrypting, etc.
328.PP
329There are two places where the \fB\s-1EVP_PKEY_METHOD\s0\fR objects are stored: one
330is a built-in static array representing the standard methods for different
331algorithms, and the other one is a stack of user-defined application-specific
137.\" For nroff, turn off justification. Always turn off hyphenation; it makes
138.\" way too many mistakes in technical documents.
139.if n .ad l
140.nh
141.SH "NAME"
142EVP_PKEY_meth_new, EVP_PKEY_meth_free, EVP_PKEY_meth_copy, EVP_PKEY_meth_find,
143EVP_PKEY_meth_add0, EVP_PKEY_METHOD,
144EVP_PKEY_meth_set_init, EVP_PKEY_meth_set_copy, EVP_PKEY_meth_set_cleanup,

--- 183 unchanged lines hidden (view full) ---

328\&\fB\s-1EVP_PKEY_METHOD\s0\fR is a structure which holds a set of methods for a
329specific public key cryptographic algorithm. Those methods are usually
330used to perform different jobs, such as generating a key, signing or
331verifying, encrypting or decrypting, etc.
332.PP
333There are two places where the \fB\s-1EVP_PKEY_METHOD\s0\fR objects are stored: one
334is a built-in static array representing the standard methods for different
335algorithms, and the other one is a stack of user-defined application-specific
332methods, which can be manipulated by using \fIEVP_PKEY_meth_add0\fR\|(3).
336methods, which can be manipulated by using \fBEVP_PKEY_meth_add0\fR\|(3).
333.PP
334The \fB\s-1EVP_PKEY_METHOD\s0\fR objects are usually referenced by \fB\s-1EVP_PKEY_CTX\s0\fR
335objects.
336.SS "Methods"
337.IX Subsection "Methods"
338The methods are the underlying implementations of a particular public key
339algorithm present by the \fB\s-1EVP_PKEY_CTX\s0\fR object.
340.PP
341.Vb 3
342\& int (*init) (EVP_PKEY_CTX *ctx);
343\& int (*copy) (EVP_PKEY_CTX *dst, EVP_PKEY_CTX *src);
344\& void (*cleanup) (EVP_PKEY_CTX *ctx);
345.Ve
346.PP
337.PP
338The \fB\s-1EVP_PKEY_METHOD\s0\fR objects are usually referenced by \fB\s-1EVP_PKEY_CTX\s0\fR
339objects.
340.SS "Methods"
341.IX Subsection "Methods"
342The methods are the underlying implementations of a particular public key
343algorithm present by the \fB\s-1EVP_PKEY_CTX\s0\fR object.
344.PP
345.Vb 3
346\& int (*init) (EVP_PKEY_CTX *ctx);
347\& int (*copy) (EVP_PKEY_CTX *dst, EVP_PKEY_CTX *src);
348\& void (*cleanup) (EVP_PKEY_CTX *ctx);
349.Ve
350.PP
347The \fIinit()\fR method is called to initialize algorithm-specific data when a new
348\&\fB\s-1EVP_PKEY_CTX\s0\fR is created. As opposed to \fIinit()\fR, the \fIcleanup()\fR method is called
349when an \fB\s-1EVP_PKEY_CTX\s0\fR is freed. The \fIcopy()\fR method is called when an \fB\s-1EVP_PKEY_CTX\s0\fR
350is being duplicated. Refer to \fIEVP_PKEY_CTX_new\fR\|(3), \fIEVP_PKEY_CTX_new_id\fR\|(3),
351\&\fIEVP_PKEY_CTX_free\fR\|(3) and \fIEVP_PKEY_CTX_dup\fR\|(3).
351The \fBinit()\fR method is called to initialize algorithm-specific data when a new
352\&\fB\s-1EVP_PKEY_CTX\s0\fR is created. As opposed to \fBinit()\fR, the \fBcleanup()\fR method is called
353when an \fB\s-1EVP_PKEY_CTX\s0\fR is freed. The \fBcopy()\fR method is called when an \fB\s-1EVP_PKEY_CTX\s0\fR
354is being duplicated. Refer to \fBEVP_PKEY_CTX_new\fR\|(3), \fBEVP_PKEY_CTX_new_id\fR\|(3),
355\&\fBEVP_PKEY_CTX_free\fR\|(3) and \fBEVP_PKEY_CTX_dup\fR\|(3).
352.PP
353.Vb 2
354\& int (*paramgen_init) (EVP_PKEY_CTX *ctx);
355\& int (*paramgen) (EVP_PKEY_CTX *ctx, EVP_PKEY *pkey);
356.Ve
357.PP
356.PP
357.Vb 2
358\& int (*paramgen_init) (EVP_PKEY_CTX *ctx);
359\& int (*paramgen) (EVP_PKEY_CTX *ctx, EVP_PKEY *pkey);
360.Ve
361.PP
358The \fIparamgen_init()\fR and \fIparamgen()\fR methods deal with key parameter generation.
359They are called by \fIEVP_PKEY_paramgen_init\fR\|(3) and \fIEVP_PKEY_paramgen\fR\|(3) to
362The \fBparamgen_init()\fR and \fBparamgen()\fR methods deal with key parameter generation.
363They are called by \fBEVP_PKEY_paramgen_init\fR\|(3) and \fBEVP_PKEY_paramgen\fR\|(3) to
360handle the parameter generation process.
361.PP
362.Vb 2
363\& int (*keygen_init) (EVP_PKEY_CTX *ctx);
364\& int (*keygen) (EVP_PKEY_CTX *ctx, EVP_PKEY *pkey);
365.Ve
366.PP
364handle the parameter generation process.
365.PP
366.Vb 2
367\& int (*keygen_init) (EVP_PKEY_CTX *ctx);
368\& int (*keygen) (EVP_PKEY_CTX *ctx, EVP_PKEY *pkey);
369.Ve
370.PP
367The \fIkeygen_init()\fR and \fIkeygen()\fR methods are used to generate the actual key for
368the specified algorithm. They are called by \fIEVP_PKEY_keygen_init\fR\|(3) and
369\&\fIEVP_PKEY_keygen\fR\|(3).
371The \fBkeygen_init()\fR and \fBkeygen()\fR methods are used to generate the actual key for
372the specified algorithm. They are called by \fBEVP_PKEY_keygen_init\fR\|(3) and
373\&\fBEVP_PKEY_keygen\fR\|(3).
370.PP
371.Vb 3
372\& int (*sign_init) (EVP_PKEY_CTX *ctx);
373\& int (*sign) (EVP_PKEY_CTX *ctx, unsigned char *sig, size_t *siglen,
374\& const unsigned char *tbs, size_t tbslen);
375.Ve
376.PP
374.PP
375.Vb 3
376\& int (*sign_init) (EVP_PKEY_CTX *ctx);
377\& int (*sign) (EVP_PKEY_CTX *ctx, unsigned char *sig, size_t *siglen,
378\& const unsigned char *tbs, size_t tbslen);
379.Ve
380.PP
377The \fIsign_init()\fR and \fIsign()\fR methods are used to generate the signature of a
378piece of data using a private key. They are called by \fIEVP_PKEY_sign_init\fR\|(3)
379and \fIEVP_PKEY_sign\fR\|(3).
381The \fBsign_init()\fR and \fBsign()\fR methods are used to generate the signature of a
382piece of data using a private key. They are called by \fBEVP_PKEY_sign_init\fR\|(3)
383and \fBEVP_PKEY_sign\fR\|(3).
380.PP
381.Vb 4
382\& int (*verify_init) (EVP_PKEY_CTX *ctx);
383\& int (*verify) (EVP_PKEY_CTX *ctx,
384\& const unsigned char *sig, size_t siglen,
385\& const unsigned char *tbs, size_t tbslen);
386.Ve
387.PP
384.PP
385.Vb 4
386\& int (*verify_init) (EVP_PKEY_CTX *ctx);
387\& int (*verify) (EVP_PKEY_CTX *ctx,
388\& const unsigned char *sig, size_t siglen,
389\& const unsigned char *tbs, size_t tbslen);
390.Ve
391.PP
388The \fIverify_init()\fR and \fIverify()\fR methods are used to verify whether a signature is
389valid. They are called by \fIEVP_PKEY_verify_init\fR\|(3) and \fIEVP_PKEY_verify\fR\|(3).
392The \fBverify_init()\fR and \fBverify()\fR methods are used to verify whether a signature is
393valid. They are called by \fBEVP_PKEY_verify_init\fR\|(3) and \fBEVP_PKEY_verify\fR\|(3).
390.PP
391.Vb 4
392\& int (*verify_recover_init) (EVP_PKEY_CTX *ctx);
393\& int (*verify_recover) (EVP_PKEY_CTX *ctx,
394\& unsigned char *rout, size_t *routlen,
395\& const unsigned char *sig, size_t siglen);
396.Ve
397.PP
394.PP
395.Vb 4
396\& int (*verify_recover_init) (EVP_PKEY_CTX *ctx);
397\& int (*verify_recover) (EVP_PKEY_CTX *ctx,
398\& unsigned char *rout, size_t *routlen,
399\& const unsigned char *sig, size_t siglen);
400.Ve
401.PP
398The \fIverify_recover_init()\fR and \fIverify_recover()\fR methods are used to verify a
402The \fBverify_recover_init()\fR and \fBverify_recover()\fR methods are used to verify a
399signature and then recover the digest from the signature (for instance, a
400signature that was generated by \s-1RSA\s0 signing algorithm). They are called by
403signature and then recover the digest from the signature (for instance, a
404signature that was generated by \s-1RSA\s0 signing algorithm). They are called by
401\&\fIEVP_PKEY_verify_recover_init\fR\|(3) and \fIEVP_PKEY_verify_recover\fR\|(3).
405\&\fBEVP_PKEY_verify_recover_init\fR\|(3) and \fBEVP_PKEY_verify_recover\fR\|(3).
402.PP
403.Vb 3
404\& int (*signctx_init) (EVP_PKEY_CTX *ctx, EVP_MD_CTX *mctx);
405\& int (*signctx) (EVP_PKEY_CTX *ctx, unsigned char *sig, size_t *siglen,
406\& EVP_MD_CTX *mctx);
407.Ve
408.PP
406.PP
407.Vb 3
408\& int (*signctx_init) (EVP_PKEY_CTX *ctx, EVP_MD_CTX *mctx);
409\& int (*signctx) (EVP_PKEY_CTX *ctx, unsigned char *sig, size_t *siglen,
410\& EVP_MD_CTX *mctx);
411.Ve
412.PP
409The \fIsignctx_init()\fR and \fIsignctx()\fR methods are used to sign a digest present by
413The \fBsignctx_init()\fR and \fBsignctx()\fR methods are used to sign a digest present by
410a \fB\s-1EVP_MD_CTX\s0\fR object. They are called by the EVP_DigestSign functions. See
414a \fB\s-1EVP_MD_CTX\s0\fR object. They are called by the EVP_DigestSign functions. See
411\&\fIEVP_DigestSignInit\fR\|(3) for detail.
415\&\fBEVP_DigestSignInit\fR\|(3) for detail.
412.PP
413.Vb 3
414\& int (*verifyctx_init) (EVP_PKEY_CTX *ctx, EVP_MD_CTX *mctx);
415\& int (*verifyctx) (EVP_PKEY_CTX *ctx, const unsigned char *sig, int siglen,
416\& EVP_MD_CTX *mctx);
417.Ve
418.PP
416.PP
417.Vb 3
418\& int (*verifyctx_init) (EVP_PKEY_CTX *ctx, EVP_MD_CTX *mctx);
419\& int (*verifyctx) (EVP_PKEY_CTX *ctx, const unsigned char *sig, int siglen,
420\& EVP_MD_CTX *mctx);
421.Ve
422.PP
419The \fIverifyctx_init()\fR and \fIverifyctx()\fR methods are used to verify a signature
423The \fBverifyctx_init()\fR and \fBverifyctx()\fR methods are used to verify a signature
420against the data in a \fB\s-1EVP_MD_CTX\s0\fR object. They are called by the various
424against the data in a \fB\s-1EVP_MD_CTX\s0\fR object. They are called by the various
421EVP_DigestVerify functions. See \fIEVP_DigestVerifyInit\fR\|(3) for detail.
425EVP_DigestVerify functions. See \fBEVP_DigestVerifyInit\fR\|(3) for detail.
422.PP
423.Vb 3
424\& int (*encrypt_init) (EVP_PKEY_CTX *ctx);
425\& int (*encrypt) (EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen,
426\& const unsigned char *in, size_t inlen);
427.Ve
428.PP
426.PP
427.Vb 3
428\& int (*encrypt_init) (EVP_PKEY_CTX *ctx);
429\& int (*encrypt) (EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen,
430\& const unsigned char *in, size_t inlen);
431.Ve
432.PP
429The \fIencrypt_init()\fR and \fIencrypt()\fR methods are used to encrypt a piece of data.
430They are called by \fIEVP_PKEY_encrypt_init\fR\|(3) and \fIEVP_PKEY_encrypt\fR\|(3).
433The \fBencrypt_init()\fR and \fBencrypt()\fR methods are used to encrypt a piece of data.
434They are called by \fBEVP_PKEY_encrypt_init\fR\|(3) and \fBEVP_PKEY_encrypt\fR\|(3).
431.PP
432.Vb 3
433\& int (*decrypt_init) (EVP_PKEY_CTX *ctx);
434\& int (*decrypt) (EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen,
435\& const unsigned char *in, size_t inlen);
436.Ve
437.PP
435.PP
436.Vb 3
437\& int (*decrypt_init) (EVP_PKEY_CTX *ctx);
438\& int (*decrypt) (EVP_PKEY_CTX *ctx, unsigned char *out, size_t *outlen,
439\& const unsigned char *in, size_t inlen);
440.Ve
441.PP
438The \fIdecrypt_init()\fR and \fIdecrypt()\fR methods are used to decrypt a piece of data.
439They are called by \fIEVP_PKEY_decrypt_init\fR\|(3) and \fIEVP_PKEY_decrypt\fR\|(3).
442The \fBdecrypt_init()\fR and \fBdecrypt()\fR methods are used to decrypt a piece of data.
443They are called by \fBEVP_PKEY_decrypt_init\fR\|(3) and \fBEVP_PKEY_decrypt\fR\|(3).
440.PP
441.Vb 2
442\& int (*derive_init) (EVP_PKEY_CTX *ctx);
443\& int (*derive) (EVP_PKEY_CTX *ctx, unsigned char *key, size_t *keylen);
444.Ve
445.PP
444.PP
445.Vb 2
446\& int (*derive_init) (EVP_PKEY_CTX *ctx);
447\& int (*derive) (EVP_PKEY_CTX *ctx, unsigned char *key, size_t *keylen);
448.Ve
449.PP
446The \fIderive_init()\fR and \fIderive()\fR methods are used to derive the shared secret
450The \fBderive_init()\fR and \fBderive()\fR methods are used to derive the shared secret
447from a public key algorithm (for instance, the \s-1DH\s0 algorithm). They are called by
451from a public key algorithm (for instance, the \s-1DH\s0 algorithm). They are called by
448\&\fIEVP_PKEY_derive_init\fR\|(3) and \fIEVP_PKEY_derive\fR\|(3).
452\&\fBEVP_PKEY_derive_init\fR\|(3) and \fBEVP_PKEY_derive\fR\|(3).
449.PP
450.Vb 2
451\& int (*ctrl) (EVP_PKEY_CTX *ctx, int type, int p1, void *p2);
452\& int (*ctrl_str) (EVP_PKEY_CTX *ctx, const char *type, const char *value);
453.Ve
454.PP
453.PP
454.Vb 2
455\& int (*ctrl) (EVP_PKEY_CTX *ctx, int type, int p1, void *p2);
456\& int (*ctrl_str) (EVP_PKEY_CTX *ctx, const char *type, const char *value);
457.Ve
458.PP
455The \fIctrl()\fR and \fIctrl_str()\fR methods are used to adjust algorithm-specific
456settings. See \fIEVP_PKEY_CTX_ctrl\fR\|(3) and related functions for detail.
459The \fBctrl()\fR and \fBctrl_str()\fR methods are used to adjust algorithm-specific
460settings. See \fBEVP_PKEY_CTX_ctrl\fR\|(3) and related functions for detail.
457.PP
458.Vb 5
459\& int (*digestsign) (EVP_MD_CTX *ctx, unsigned char *sig, size_t *siglen,
460\& const unsigned char *tbs, size_t tbslen);
461\& int (*digestverify) (EVP_MD_CTX *ctx, const unsigned char *sig,
462\& size_t siglen, const unsigned char *tbs,
463\& size_t tbslen);
464.Ve
465.PP
461.PP
462.Vb 5
463\& int (*digestsign) (EVP_MD_CTX *ctx, unsigned char *sig, size_t *siglen,
464\& const unsigned char *tbs, size_t tbslen);
465\& int (*digestverify) (EVP_MD_CTX *ctx, const unsigned char *sig,
466\& size_t siglen, const unsigned char *tbs,
467\& size_t tbslen);
468.Ve
469.PP
466The \fIdigestsign()\fR and \fIdigestverify()\fR methods are used to generate or verify
467a signature in a one-shot mode. They could be called by \fIEVP_DigetSign\fR\|(3)
468and \fIEVP_DigestVerify\fR\|(3).
470The \fBdigestsign()\fR and \fBdigestverify()\fR methods are used to generate or verify
471a signature in a one-shot mode. They could be called by \fBEVP_DigetSign\fR\|(3)
472and \fBEVP_DigestVerify\fR\|(3).
469.SS "Functions"
470.IX Subsection "Functions"
473.SS "Functions"
474.IX Subsection "Functions"
471\&\fIEVP_PKEY_meth_new()\fR creates and returns a new \fB\s-1EVP_PKEY_METHOD\s0\fR object,
475\&\fBEVP_PKEY_meth_new()\fR creates and returns a new \fB\s-1EVP_PKEY_METHOD\s0\fR object,
472and associates the given \fBid\fR and \fBflags\fR. The following flags are
473supported:
474.PP
475.Vb 2
476\& EVP_PKEY_FLAG_AUTOARGLEN
477\& EVP_PKEY_FLAG_SIGCTX_CUSTOM
478.Ve
479.PP
480If an \fB\s-1EVP_PKEY_METHOD\s0\fR is set with the \fB\s-1EVP_PKEY_FLAG_AUTOARGLEN\s0\fR flag, the
481maximum size of the output buffer will be automatically calculated or checked
482in corresponding \s-1EVP\s0 methods by the \s-1EVP\s0 framework. Thus the implementations of
483these methods don't need to care about handling the case of returning output
484buffer size by themselves. For details on the output buffer size, refer to
476and associates the given \fBid\fR and \fBflags\fR. The following flags are
477supported:
478.PP
479.Vb 2
480\& EVP_PKEY_FLAG_AUTOARGLEN
481\& EVP_PKEY_FLAG_SIGCTX_CUSTOM
482.Ve
483.PP
484If an \fB\s-1EVP_PKEY_METHOD\s0\fR is set with the \fB\s-1EVP_PKEY_FLAG_AUTOARGLEN\s0\fR flag, the
485maximum size of the output buffer will be automatically calculated or checked
486in corresponding \s-1EVP\s0 methods by the \s-1EVP\s0 framework. Thus the implementations of
487these methods don't need to care about handling the case of returning output
488buffer size by themselves. For details on the output buffer size, refer to
485\&\fIEVP_PKEY_sign\fR\|(3).
489\&\fBEVP_PKEY_sign\fR\|(3).
486.PP
490.PP
487The \fB\s-1EVP_PKEY_FLAG_SIGCTX_CUSTOM\s0\fR is used to indicate the \fIsignctx()\fR method
491The \fB\s-1EVP_PKEY_FLAG_SIGCTX_CUSTOM\s0\fR is used to indicate the \fBsignctx()\fR method
488of an \fB\s-1EVP_PKEY_METHOD\s0\fR is always called by the \s-1EVP\s0 framework while doing a
492of an \fB\s-1EVP_PKEY_METHOD\s0\fR is always called by the \s-1EVP\s0 framework while doing a
489digest signing operation by calling \fIEVP_DigestSignFinal\fR\|(3).
493digest signing operation by calling \fBEVP_DigestSignFinal\fR\|(3).
490.PP
494.PP
491\&\fIEVP_PKEY_meth_free()\fR frees an existing \fB\s-1EVP_PKEY_METHOD\s0\fR pointed by
495\&\fBEVP_PKEY_meth_free()\fR frees an existing \fB\s-1EVP_PKEY_METHOD\s0\fR pointed by
492\&\fBpmeth\fR.
493.PP
496\&\fBpmeth\fR.
497.PP
494\&\fIEVP_PKEY_meth_copy()\fR copies an \fB\s-1EVP_PKEY_METHOD\s0\fR object from \fBsrc\fR
498\&\fBEVP_PKEY_meth_copy()\fR copies an \fB\s-1EVP_PKEY_METHOD\s0\fR object from \fBsrc\fR
495to \fBdst\fR.
496.PP
499to \fBdst\fR.
500.PP
497\&\fIEVP_PKEY_meth_find()\fR finds an \fB\s-1EVP_PKEY_METHOD\s0\fR object with the \fBid\fR.
501\&\fBEVP_PKEY_meth_find()\fR finds an \fB\s-1EVP_PKEY_METHOD\s0\fR object with the \fBid\fR.
498This function first searches through the user-defined method objects and
499then the built-in objects.
500.PP
502This function first searches through the user-defined method objects and
503then the built-in objects.
504.PP
501\&\fIEVP_PKEY_meth_add0()\fR adds \fBpmeth\fR to the user defined stack of methods.
505\&\fBEVP_PKEY_meth_add0()\fR adds \fBpmeth\fR to the user defined stack of methods.
502.PP
503The EVP_PKEY_meth_set functions set the corresponding fields of
504\&\fB\s-1EVP_PKEY_METHOD\s0\fR structure with the arguments passed.
505.PP
506The EVP_PKEY_meth_get functions get the corresponding fields of
507\&\fB\s-1EVP_PKEY_METHOD\s0\fR structure to the arguments provided.
508.SH "RETURN VALUES"
509.IX Header "RETURN VALUES"
506.PP
507The EVP_PKEY_meth_set functions set the corresponding fields of
508\&\fB\s-1EVP_PKEY_METHOD\s0\fR structure with the arguments passed.
509.PP
510The EVP_PKEY_meth_get functions get the corresponding fields of
511\&\fB\s-1EVP_PKEY_METHOD\s0\fR structure to the arguments provided.
512.SH "RETURN VALUES"
513.IX Header "RETURN VALUES"
510\&\fIEVP_PKEY_meth_new()\fR returns a pointer to a new \fB\s-1EVP_PKEY_METHOD\s0\fR
514\&\fBEVP_PKEY_meth_new()\fR returns a pointer to a new \fB\s-1EVP_PKEY_METHOD\s0\fR
511object or returns \s-1NULL\s0 on error.
512.PP
515object or returns \s-1NULL\s0 on error.
516.PP
513\&\fIEVP_PKEY_meth_free()\fR and \fIEVP_PKEY_meth_copy()\fR do not return values.
517\&\fBEVP_PKEY_meth_free()\fR and \fBEVP_PKEY_meth_copy()\fR do not return values.
514.PP
518.PP
515\&\fIEVP_PKEY_meth_find()\fR returns a pointer to the found \fB\s-1EVP_PKEY_METHOD\s0\fR
519\&\fBEVP_PKEY_meth_find()\fR returns a pointer to the found \fB\s-1EVP_PKEY_METHOD\s0\fR
516object or returns \s-1NULL\s0 if not found.
517.PP
520object or returns \s-1NULL\s0 if not found.
521.PP
518\&\fIEVP_PKEY_meth_add0()\fR returns 1 if method is added successfully or 0
522\&\fBEVP_PKEY_meth_add0()\fR returns 1 if method is added successfully or 0
519if an error occurred.
520.PP
521All EVP_PKEY_meth_set and EVP_PKEY_meth_get functions have no return
522values. For the 'get' functions, function pointers are returned by
523arguments.
524.SH "COPYRIGHT"
525.IX Header "COPYRIGHT"
526Copyright 2017 The OpenSSL Project Authors. All Rights Reserved.
527.PP
528Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
529this file except in compliance with the License. You can obtain a copy
530in the file \s-1LICENSE\s0 in the source distribution or at
531<https://www.openssl.org/source/license.html>.
523if an error occurred.
524.PP
525All EVP_PKEY_meth_set and EVP_PKEY_meth_get functions have no return
526values. For the 'get' functions, function pointers are returned by
527arguments.
528.SH "COPYRIGHT"
529.IX Header "COPYRIGHT"
530Copyright 2017 The OpenSSL Project Authors. All Rights Reserved.
531.PP
532Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
533this file except in compliance with the License. You can obtain a copy
534in the file \s-1LICENSE\s0 in the source distribution or at
535<https://www.openssl.org/source/license.html>.