$98 GRAYBYTE WORDPRESS FILE MANAGER $16

SERVER : premium201.web-hosting.com #1 SMP Wed Mar 26 12:08:09 UTC 2025
SERVER IP : 104.21.43.35 | ADMIN IP 216.73.216.180
OPTIONS : CRL = ON | WGT = ON | SDO = OFF | PKEX = OFF
DEACTIVATED : mail

/opt/cpanel/ea-openssl11/share/doc/openssl/html/man7/

HOME
Current File : /opt/cpanel/ea-openssl11/share/doc/openssl/html/man7//SM2.html
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>SM2</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>



<ul id="index">
  <li><a href="#NAME">NAME</a></li>
  <li><a href="#DESCRIPTION">DESCRIPTION</a></li>
  <li><a href="#NOTES">NOTES</a></li>
  <li><a href="#EXAMPLES">EXAMPLES</a></li>
  <li><a href="#SEE-ALSO">SEE ALSO</a></li>
  <li><a href="#COPYRIGHT">COPYRIGHT</a></li>
</ul>

<h1 id="NAME">NAME</h1>

<p>SM2 - Chinese SM2 signature and encryption algorithm support</p>

<h1 id="DESCRIPTION">DESCRIPTION</h1>

<p>The <b>SM2</b> 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</b> is actually an elliptic curve based algorithm. The current implementation in OpenSSL supports both signature and encryption schemes via the EVP interface.</p>

<p>When doing the <b>SM2</b> signature algorithm, it requires a distinguishing identifier to form the message prefix which is hashed before the real message is hashed.</p>

<h1 id="NOTES">NOTES</h1>

<p><b>SM2</b> signatures can be generated by using the &#39;DigestSign&#39; series of APIs, for instance, EVP_DigestSignInit(), EVP_DigestSignUpdate() and EVP_DigestSignFinal(). Ditto for the verification process by calling the &#39;DigestVerify&#39; series of APIs.</p>

<p>There are several special steps that need to be done before computing an <b>SM2</b> signature.</p>

<p>The <b>EVP_PKEY</b> structure will default to using ECDSA for signatures when it is created. It should be set to <b>EVP_PKEY_SM2</b> by calling:</p>

<pre><code> EVP_PKEY_set_alias_type(pkey, EVP_PKEY_SM2);</code></pre>

<p>Then an ID should be set by calling:</p>

<pre><code> EVP_PKEY_CTX_set1_id(pctx, id, id_len);</code></pre>

<p>When calling the EVP_DigestSignInit() or EVP_DigestVerifyInit() functions, a preallocated <b>EVP_PKEY_CTX</b> should be assigned to the <b>EVP_MD_CTX</b>. This is done by calling:</p>

<pre><code> EVP_MD_CTX_set_pkey_ctx(mctx, pctx);</code></pre>

<p>And normally there is no need to pass a <b>pctx</b> parameter to EVP_DigestSignInit() or EVP_DigestVerifyInit() in such a scenario.</p>

<h1 id="EXAMPLES">EXAMPLES</h1>

<p>This example demonstrates the calling sequence for using an <b>EVP_PKEY</b> to verify a message with the SM2 signature algorithm and the SM3 hash algorithm:</p>

<pre><code> #include &lt;openssl/evp.h&gt;

 /* obtain an EVP_PKEY using whatever methods... */
 EVP_PKEY_set_alias_type(pkey, EVP_PKEY_SM2);
 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)</code></pre>

<h1 id="SEE-ALSO">SEE ALSO</h1>

<p><a href="../man3/EVP_PKEY_CTX_new.html">EVP_PKEY_CTX_new(3)</a>, <a href="../man3/EVP_PKEY_set_alias_type.html">EVP_PKEY_set_alias_type(3)</a>, <a href="../man3/EVP_DigestSignInit.html">EVP_DigestSignInit(3)</a>, <a href="../man3/EVP_DigestVerifyInit.html">EVP_DigestVerifyInit(3)</a>, <a href="../man3/EVP_PKEY_CTX_set1_id.html">EVP_PKEY_CTX_set1_id(3)</a>, <a href="../man3/EVP_MD_CTX_set_pkey_ctx.html">EVP_MD_CTX_set_pkey_ctx(3)</a></p>

<h1 id="COPYRIGHT">COPYRIGHT</h1>

<p>Copyright 2018-2020 The OpenSSL Project Authors. All Rights Reserved.</p>

<p>Licensed under the OpenSSL license (the &quot;License&quot;). 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 <a href="https://www.openssl.org/source/license.html">https://www.openssl.org/source/license.html</a>.</p>


</body>

</html>




Current_dir [ NOT WRITEABLE ] Document_root [ NOT WRITEABLE ]


[ Back ]
NAME
SIZE
LAST TOUCH
USER
CAN-I?
FUNCTIONS
..
--
3 Mar 2024 8.38 PM
root / root
0755
Ed25519.html
4.327 KB
4 Dec 2023 4.35 PM
root / root
0644
Ed448.html
4.327 KB
4 Dec 2023 4.35 PM
root / root
0644
RAND.html
4.558 KB
4 Dec 2023 4.35 PM
root / root
0644
RAND_DRBG.html
15.549 KB
4 Dec 2023 4.35 PM
root / root
0644
RSA-PSS.html
3.252 KB
4 Dec 2023 4.35 PM
root / root
0644
SM2.html
3.849 KB
4 Dec 2023 4.35 PM
root / root
0644
X25519.html
3.531 KB
4 Dec 2023 4.35 PM
root / root
0644
X448.html
3.531 KB
4 Dec 2023 4.35 PM
root / root
0644
bio.html
4.357 KB
4 Dec 2023 4.35 PM
root / root
0644
crypto.html
2.841 KB
4 Dec 2023 4.35 PM
root / root
0644
ct.html
2.677 KB
4 Dec 2023 4.35 PM
root / root
0644
des_modes.html
7.91 KB
4 Dec 2023 4.35 PM
root / root
0644
evp.html
7.306 KB
4 Dec 2023 4.35 PM
root / root
0644
ossl_store-file.html
3.195 KB
4 Dec 2023 4.35 PM
root / root
0644
ossl_store.html
3.927 KB
4 Dec 2023 4.35 PM
root / root
0644
passphrase-encoding.html
8.803 KB
4 Dec 2023 4.35 PM
root / root
0644
proxy-certificates.html
14.178 KB
4 Dec 2023 4.35 PM
root / root
0644
scrypt.html
5.363 KB
4 Dec 2023 4.35 PM
root / root
0644
ssl.html
49.886 KB
4 Dec 2023 4.35 PM
root / root
0644
x509.html
3.688 KB
4 Dec 2023 4.35 PM
root / root
0644

GRAYBYTE WORDPRESS FILE MANAGER @ 2025 CONTACT ME
Static GIF