mirror of
https://github.com/openssl/openssl.git
synced 2024-12-27 06:21:43 +08:00
f4e4382cae
This means that when loaded or created, EC EVP_PKEYs with the SM2 curve will be regarded as EVP_PKEY_SM2 type keys by default. Applications are no longer forced to check and fix this. It's still possible, for those who want this, to set the key type to EVP_PKEY_EC and thereby run the normal EC computations with the SM2 curve. This has to be done explicitly. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> (Merged from https://github.com/openssl/openssl/pull/10942)
73 lines
2.4 KiB
Plaintext
73 lines
2.4 KiB
Plaintext
=pod
|
|
|
|
=head1 NAME
|
|
|
|
SM2 - Chinese SM2 signature and encryption algorithm support
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
The B<SM2> algorithm was first defined by the Chinese national standard GM/T
|
|
0003-2012 and was later standardized by ISO as ISO/IEC 14888. B<SM2> is actually
|
|
an elliptic curve based algorithm. The current implementation in OpenSSL supports
|
|
both signature and encryption schemes via the EVP interface.
|
|
|
|
When doing the B<SM2> signature algorithm, it requires a distinguishing identifier
|
|
to form the message prefix which is hashed before the real message is hashed.
|
|
|
|
=head1 NOTES
|
|
|
|
B<SM2> signatures can be generated by using the 'DigestSign' series of APIs, for
|
|
instance, EVP_DigestSignInit(), EVP_DigestSignUpdate() and EVP_DigestSignFinal().
|
|
Ditto for the verification process by calling the 'DigestVerify' series of APIs.
|
|
|
|
Before computing an B<SM2> signature, an B<EVP_PKEY_CTX> needs to be created,
|
|
and an B<SM2> ID must be set for it, like this:
|
|
|
|
EVP_PKEY_CTX_set1_id(pctx, id, id_len);
|
|
|
|
Before calling the EVP_DigestSignInit() or EVP_DigestVerifyInit() functions,
|
|
that B<EVP_PKEY_CTX> should be assigned to the B<EVP_MD_CTX>, like this:
|
|
|
|
EVP_MD_CTX_set_pkey_ctx(mctx, pctx);
|
|
|
|
There is normally no need to pass a B<pctx> parameter to EVP_DigestSignInit()
|
|
or EVP_DigestVerifyInit() in such a scenario.
|
|
|
|
SM2 can be tested with the L<openssl-speed(1)> application since version 3.0.0.
|
|
Currently, the only valid algorithm name is B<sm2>.
|
|
|
|
=head1 EXAMPLES
|
|
|
|
This example demonstrates the calling sequence for using an B<EVP_PKEY> to verify
|
|
a message with the SM2 signature algorithm and the SM3 hash algorithm:
|
|
|
|
#include <openssl/evp.h>
|
|
|
|
/* obtain an EVP_PKEY using whatever methods... */
|
|
mctx = EVP_MD_CTX_new();
|
|
pctx = EVP_PKEY_CTX_new(pkey, NULL);
|
|
EVP_PKEY_CTX_set1_id(pctx, id, id_len);
|
|
EVP_MD_CTX_set_pkey_ctx(mctx, pctx);
|
|
EVP_DigestVerifyInit(mctx, NULL, EVP_sm3(), NULL, pkey);
|
|
EVP_DigestVerifyUpdate(mctx, msg, msg_len);
|
|
EVP_DigestVerifyFinal(mctx, sig, sig_len)
|
|
|
|
=head1 SEE ALSO
|
|
|
|
L<EVP_PKEY_CTX_new(3)>,
|
|
L<EVP_DigestSignInit(3)>,
|
|
L<EVP_DigestVerifyInit(3)>,
|
|
L<EVP_PKEY_CTX_set1_id(3)>,
|
|
L<EVP_MD_CTX_set_pkey_ctx(3)>
|
|
|
|
=head1 COPYRIGHT
|
|
|
|
Copyright 2018 The OpenSSL Project Authors. All Rights Reserved.
|
|
|
|
Licensed under the Apache License 2.0 (the "License"). You may not use
|
|
this file except in compliance with the License. You can obtain a copy
|
|
in the file LICENSE in the source distribution or at
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
=cut
|