<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[Форум Рутокен &mdash; Установка и настройка openSSL (windows7)]]></title>
		<link>https://forum.rutoken.ru/topic/3173/</link>
		<atom:link href="https://forum.rutoken.ru/feed/rss/topic/3173" rel="self" type="application/rss+xml" />
		<description><![CDATA[Недавние сообщения в теме «Установка и настройка openSSL (windows7)».]]></description>
		<lastBuildDate>Fri, 16 Dec 2022 10:39:46 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19139/#p19139</link>
			<description><![CDATA[<div class="quotebox"><cite>Аверченко Кирилл пишет:</cite><blockquote><p><strong>kolshik</strong>, попробуйте изменить эти пути:<br />dynamic_path = Users/kolyan_test/bin/sdk-rutoken/openssl/rtengine.dll<br />pkcs11_path = Users/kolyan_test/bin/sdk-rutoken/pkcs11/rtpkcs11ecp.dll</p><p>на<br />dynamic_path = &quot;C:\\Users\\kolyan_test\\bin\\sdk-rutoken\\openssl\\rtengine.dll&quot;<br />pkcs11_path = &#039;C:\\Users\\kolyan_test\\bin\\sdk-rutoken\\pkcs11\\rtpkcs11ecp.dll&quot;</p></blockquote></div><p>Спасибо Вам огромное!!! Я столько времени потратил на этот gost, что уже начал думать, что это просто не сможет никогда заработать. Глядя на эти строки, понимаю, что изучая инструкции в интернете, я бы так и не дошел до положительного результата.</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Fri, 16 Dec 2022 10:39:46 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19139/#p19139</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19138/#p19138</link>
			<description><![CDATA[<p><strong>kolshik</strong>, попробуйте изменить эти пути:<br />dynamic_path = Users/kolyan_test/bin/sdk-rutoken/openssl/rtengine.dll<br />pkcs11_path = Users/kolyan_test/bin/sdk-rutoken/pkcs11/rtpkcs11ecp.dll</p><p>на<br />dynamic_path = &quot;C:\\Users\\kolyan_test\\bin\\sdk-rutoken\\openssl\\rtengine.dll&quot;<br />pkcs11_path = &#039;C:\\Users\\kolyan_test\\bin\\sdk-rutoken\\pkcs11\\rtpkcs11ecp.dll&quot;</p>]]></description>
			<author><![CDATA[null@example.com (Аверченко Кирилл)]]></author>
			<pubDate>Fri, 16 Dec 2022 09:56:34 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19138/#p19138</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19135/#p19135</link>
			<description><![CDATA[<p>Можете посмотреть, может я что-то не так делаю и ошибка таится в мелочи?<br /><span class="postimg"><a class="fancybox fancybox.image" rel="group" href="https://forum.rutoken.ru/uploads/images/2022/12/bb11dbf12633e0e172da711fdf796f7d.png"><img class="fb_img" src="https://forum.rutoken.ru/uploads/previews/2022/12/bb11dbf12633e0e172da711fdf796f7d.png" alt="" /></a></span> <br /><span class="postimg"><a class="fancybox fancybox.image" rel="group" href="https://forum.rutoken.ru/uploads/images/2022/12/1a1cf4979358af7ab7460d37054ffa69.png"><img class="fb_img" src="https://forum.rutoken.ru/uploads/previews/2022/12/1a1cf4979358af7ab7460d37054ffa69.png" alt="" /></a></span> <br /><span class="postimg"><a class="fancybox fancybox.image" rel="group" href="https://forum.rutoken.ru/uploads/images/2022/12/75fb6b0c331cd92e7417697befe9def8.png"><img class="fb_img" src="https://forum.rutoken.ru/uploads/previews/2022/12/75fb6b0c331cd92e7417697befe9def8.png" alt="" /></a></span> </p><p>openssl_conf = openssl_def</p><p>#<br /># OpenSSL example configuration file.<br /># This is mostly being used for generation of certificate requests.<br />#</p><p># Note that you can include other files from the main configuration<br />openssl_conf = openssl_def</p><p># file using the .include directive.<br />#.include filename</p><p># This definition stops the following lines choking if HOME isn&#039;t<br /># defined.<br />HOME&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = .</p><p># Extra OBJECT IDENTIFIER info:<br />#oid_file&nbsp; &nbsp; &nbsp; &nbsp; = $ENV::HOME/.oid<br />oid_section&nbsp; &nbsp; &nbsp; &nbsp; = new_oids</p><p># To use this configuration file with the &quot;-extfile&quot; option of the<br /># &quot;openssl x509&quot; utility, name here the section containing the<br /># X.509v3 extensions to use:<br /># extensions&nbsp; &nbsp; &nbsp; &nbsp; =<br /># (Alternatively, use a configuration file that has only<br /># X.509v3 extensions in its main [= default] section.)</p><p>[ new_oids ]</p><p># We can add new OIDs in here for use by &#039;ca&#039;, &#039;req&#039; and &#039;ts&#039;.<br /># Add a simple OID like this:<br /># testoid1=1.2.3.4<br /># Or use config file substitution like this:<br /># testoid2=${testoid1}.5.6</p><p># Policies used by the TSA examples.<br />tsa_policy1 = 1.2.3.4.1<br />tsa_policy2 = 1.2.3.4.5.6<br />tsa_policy3 = 1.2.3.4.5.7</p><p>####################################################################<br />[ ca ]<br />default_ca&nbsp; &nbsp; = CA_default&nbsp; &nbsp; &nbsp; &nbsp; # The default ca section</p><p>####################################################################<br />[ CA_default ]</p><p>dir&nbsp; &nbsp; &nbsp; &nbsp; = ./demoCA&nbsp; &nbsp; &nbsp; &nbsp; # Where everything is kept<br />certs&nbsp; &nbsp; &nbsp; &nbsp; = $dir/certs&nbsp; &nbsp; &nbsp; &nbsp; # Where the issued certs are kept<br />crl_dir&nbsp; &nbsp; &nbsp; &nbsp; = $dir/crl&nbsp; &nbsp; &nbsp; &nbsp; # Where the issued crl are kept<br />database&nbsp; &nbsp; = $dir/index.txt&nbsp; &nbsp; # database index file.<br />#unique_subject&nbsp; &nbsp; = no&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Set to &#039;no&#039; to allow creation of<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # several certs with same subject.<br />new_certs_dir&nbsp; &nbsp; = $dir/newcerts&nbsp; &nbsp; &nbsp; &nbsp; # default place for new certs.</p><p>certificate&nbsp; &nbsp; = $dir/cacert.pem&nbsp; &nbsp; &nbsp;# The CA certificate<br />serial&nbsp; &nbsp; &nbsp; &nbsp; = $dir/serial&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# The current serial number<br />crlnumber&nbsp; &nbsp; = $dir/crlnumber&nbsp; &nbsp; # the current crl number<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # must be commented out to leave a V1 CRL<br />crl&nbsp; &nbsp; &nbsp; &nbsp; = $dir/crl.pem&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;# The current CRL<br />private_key&nbsp; &nbsp; = $dir/private/cakey.pem# The private key</p><p>x509_extensions&nbsp; &nbsp; = usr_cert&nbsp; &nbsp; &nbsp; &nbsp; # The extensions to add to the cert</p><p># Comment out the following two lines for the &quot;traditional&quot;<br /># (and highly broken) format.<br />name_opt&nbsp; &nbsp; &nbsp;= ca_default&nbsp; &nbsp; &nbsp; &nbsp; # Subject Name options<br />cert_opt&nbsp; &nbsp; &nbsp;= ca_default&nbsp; &nbsp; &nbsp; &nbsp; # Certificate field options</p><p># Extension copying option: use with caution.<br /># copy_extensions = copy</p><p># Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs<br /># so this is commented out by default to leave a V1 CRL.<br /># crlnumber must also be commented out to leave a V1 CRL.<br /># crl_extensions&nbsp; &nbsp; = crl_ext</p><p>default_days&nbsp; &nbsp; = 365&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # how long to certify for<br />default_crl_days= 30&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # how long before next CRL<br />default_md&nbsp; &nbsp; = default&nbsp; &nbsp; &nbsp; &nbsp; # use public key default MD<br />preserve&nbsp; &nbsp; = no&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # keep passed DN ordering</p><p># A few difference way of specifying how similar the request should look<br /># For type CA, the listed attributes must be the same, and the optional<br /># and supplied fields are just that :-)<br />policy&nbsp; &nbsp; &nbsp; &nbsp; = policy_match</p><p># For the CA policy<br />[ policy_match ]<br />countryName&nbsp; &nbsp; &nbsp; &nbsp; = match<br />stateOrProvinceName&nbsp; &nbsp; = match<br />organizationName&nbsp; &nbsp; = match<br />organizationalUnitName&nbsp; &nbsp; = optional<br />commonName&nbsp; &nbsp; &nbsp; &nbsp; = supplied<br />emailAddress&nbsp; &nbsp; &nbsp; &nbsp; = optional</p><p># For the &#039;anything&#039; policy<br /># At this point in time, you must list all acceptable &#039;object&#039;<br /># types.<br />[ policy_anything ]<br />countryName&nbsp; &nbsp; &nbsp; &nbsp; = optional<br />stateOrProvinceName&nbsp; &nbsp; = optional<br />localityName&nbsp; &nbsp; &nbsp; &nbsp; = optional<br />organizationName&nbsp; &nbsp; = optional<br />organizationalUnitName&nbsp; &nbsp; = optional<br />commonName&nbsp; &nbsp; &nbsp; &nbsp; = supplied<br />emailAddress&nbsp; &nbsp; &nbsp; &nbsp; = optional</p><p>####################################################################<br />[ req ]<br />default_bits&nbsp; &nbsp; &nbsp; &nbsp; = 2048<br />default_keyfile&nbsp; &nbsp; &nbsp;= privkey.pem<br />distinguished_name&nbsp; &nbsp; = req_distinguished_name<br />attributes&nbsp; &nbsp; &nbsp; &nbsp; = req_attributes<br />x509_extensions&nbsp; &nbsp; = v3_ca&nbsp; &nbsp; # The extensions to add to the self signed cert</p><p># Passwords for private keys if not present they will be prompted for<br /># input_password = secret<br /># output_password = secret</p><p># This sets a mask for permitted string types. There are several options.<br /># default: PrintableString, T61String, BMPString.<br /># pkix&nbsp; &nbsp; &nbsp;: PrintableString, BMPString (PKIX recommendation before 2004)<br /># utf8only: only UTF8Strings (PKIX recommendation after 2004).<br /># nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).<br /># MASK:XXXX a literal mask value.<br /># WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.<br />string_mask = utf8only</p><p># req_extensions = v3_req # The extensions to add to a certificate request</p><p>[ req_distinguished_name ]<br />countryName&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = Country Name (2 letter code)<br />countryName_default&nbsp; &nbsp; &nbsp; &nbsp; = AU<br />countryName_min&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = 2<br />countryName_max&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = 2</p><p>stateOrProvinceName&nbsp; &nbsp; &nbsp; &nbsp; = State or Province Name (full name)<br />stateOrProvinceName_default&nbsp; &nbsp; = Some-State</p><p>localityName&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = Locality Name (eg, city)</p><p>0.organizationName&nbsp; &nbsp; &nbsp; &nbsp; = Organization Name (eg, company)<br />0.organizationName_default&nbsp; &nbsp; = Internet Widgits Pty Ltd</p><p># we can do this but it is not needed normally :-)<br />#1.organizationName&nbsp; &nbsp; &nbsp; &nbsp; = Second Organization Name (eg, company)<br />#1.organizationName_default&nbsp; &nbsp; = World Wide Web Pty Ltd</p><p>organizationalUnitName&nbsp; &nbsp; &nbsp; &nbsp; = Organizational Unit Name (eg, section)<br />#organizationalUnitName_default&nbsp; &nbsp; =</p><p>commonName&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = Common Name (e.g. server FQDN or YOUR name)<br />commonName_max&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = 64</p><p>emailAddress&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = Email Address<br />emailAddress_max&nbsp; &nbsp; &nbsp; &nbsp; = 64</p><p># SET-ex3&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = SET extension number 3</p><p>[ req_attributes ]<br />challengePassword&nbsp; &nbsp; &nbsp; &nbsp; = A challenge password<br />challengePassword_min&nbsp; &nbsp; &nbsp; &nbsp; = 4<br />challengePassword_max&nbsp; &nbsp; &nbsp; &nbsp; = 20</p><p>unstructuredName&nbsp; &nbsp; &nbsp; &nbsp; = An optional company name</p><p>[ usr_cert ]</p><p># These extensions are added when &#039;ca&#039; signs a request.</p><p># This goes against PKIX guidelines but some CAs do it and some software<br /># requires this to avoid interpreting an end user certificate as a CA.</p><p>basicConstraints=CA:FALSE</p><p># Here are some examples of the usage of nsCertType. If it is omitted<br /># the certificate can be used for anything *except* object signing.</p><p># This is OK for an SSL server.<br /># nsCertType&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = server</p><p># For an object signing certificate this would be used.<br /># nsCertType = objsign</p><p># For normal client use this is typical<br /># nsCertType = client, email</p><p># and for everything including object signing:<br /># nsCertType = client, email, objsign</p><p># This is typical in keyUsage for a client certificate.<br /># keyUsage = nonRepudiation, digitalSignature, keyEncipherment</p><p># This will be displayed in Netscape&#039;s comment listbox.<br />nsComment&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = &quot;OpenSSL Generated Certificate&quot;</p><p># PKIX recommendations harmless if included in all certificates.<br />subjectKeyIdentifier=hash<br />authorityKeyIdentifier=keyid,issuer</p><p># This stuff is for subjectAltName and issuerAltname.<br /># Import the email address.<br /># subjectAltName=email:copy<br /># An alternative to produce certificates that aren&#039;t<br /># deprecated according to PKIX.<br /># subjectAltName=email:move</p><p># Copy subject details<br /># issuerAltName=issuer:copy</p><p>#nsCaRevocationUrl&nbsp; &nbsp; &nbsp; &nbsp; = <a href="http://www.domain.dom/ca-crl.pem">http://www.domain.dom/ca-crl.pem</a><br />#nsBaseUrl<br />#nsRevocationUrl<br />#nsRenewalUrl<br />#nsCaPolicyUrl<br />#nsSslServerName</p><p># This is required for TSA certificates.<br /># extendedKeyUsage = critical,timeStamping</p><p>[ v3_req ]</p><p># Extensions to add to a certificate request</p><p>basicConstraints = CA:FALSE<br />keyUsage = nonRepudiation, digitalSignature, keyEncipherment</p><p>[ v3_ca ]</p><br /><p># Extensions for a typical CA</p><br /><p># PKIX recommendation.</p><p>subjectKeyIdentifier=hash</p><p>authorityKeyIdentifier=keyid:always,issuer</p><p>basicConstraints = critical,CA:true</p><p># Key usage: this is typical for a CA certificate. However since it will<br /># prevent it being used as an test self-signed certificate it is best<br /># left out by default.<br /># keyUsage = cRLSign, keyCertSign</p><p># Some might want this also<br /># nsCertType = sslCA, emailCA</p><p># Include email address in subject alt name: another PKIX recommendation<br /># subjectAltName=email:copy<br /># Copy issuer details<br /># issuerAltName=issuer:copy</p><p># DER hex encoding of an extension: beware experts only!<br /># obj=DER:02:03<br /># Where &#039;obj&#039; is a standard or added object<br /># You can even override a supported extension:<br /># basicConstraints= critical, DER:30:03:01:01:FF</p><p>[ crl_ext ]</p><p># CRL extensions.<br /># Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.</p><p># issuerAltName=issuer:copy<br />authorityKeyIdentifier=keyid:always</p><p>[ proxy_cert_ext ]<br /># These extensions should be added when creating a proxy certificate</p><p># This goes against PKIX guidelines but some CAs do it and some software<br /># requires this to avoid interpreting an end user certificate as a CA.</p><p>basicConstraints=CA:FALSE</p><p># Here are some examples of the usage of nsCertType. If it is omitted<br /># the certificate can be used for anything *except* object signing.</p><p># This is OK for an SSL server.<br /># nsCertType&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = server</p><p># For an object signing certificate this would be used.<br /># nsCertType = objsign</p><p># For normal client use this is typical<br /># nsCertType = client, email</p><p># and for everything including object signing:<br /># nsCertType = client, email, objsign</p><p># This is typical in keyUsage for a client certificate.<br /># keyUsage = nonRepudiation, digitalSignature, keyEncipherment</p><p># This will be displayed in Netscape&#039;s comment listbox.<br />nsComment&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = &quot;OpenSSL Generated Certificate&quot;</p><p># PKIX recommendations harmless if included in all certificates.<br />subjectKeyIdentifier=hash<br />authorityKeyIdentifier=keyid,issuer</p><p># This stuff is for subjectAltName and issuerAltname.<br /># Import the email address.<br /># subjectAltName=email:copy<br /># An alternative to produce certificates that aren&#039;t<br /># deprecated according to PKIX.<br /># subjectAltName=email:move</p><p># Copy subject details<br /># issuerAltName=issuer:copy</p><p>#nsCaRevocationUrl&nbsp; &nbsp; &nbsp; &nbsp; = <a href="http://www.domain.dom/ca-crl.pem">http://www.domain.dom/ca-crl.pem</a><br />#nsBaseUrl<br />#nsRevocationUrl<br />#nsRenewalUrl<br />#nsCaPolicyUrl<br />#nsSslServerName</p><p># This really needs to be in place for it to be a proxy certificate.<br />proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo</p><p>####################################################################<br />[ tsa ]</p><p>default_tsa = tsa_config1&nbsp; &nbsp; # the default TSA section</p><p>[ tsa_config1 ]</p><p># These are used by the TSA reply generation only.<br />dir&nbsp; &nbsp; &nbsp; &nbsp; = ./demoCA&nbsp; &nbsp; &nbsp; &nbsp; # TSA root directory<br />serial&nbsp; &nbsp; &nbsp; &nbsp; = $dir/tsaserial&nbsp; &nbsp; # The current serial number (mandatory)<br />crypto_device&nbsp; &nbsp; = builtin&nbsp; &nbsp; &nbsp; &nbsp; # OpenSSL engine to use for signing<br />signer_cert&nbsp; &nbsp; = $dir/tsacert.pem&nbsp; &nbsp; &nbsp;# The TSA signing certificate<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional)<br />certs&nbsp; &nbsp; &nbsp; &nbsp; = $dir/cacert.pem&nbsp; &nbsp; # Certificate chain to include in reply<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional)<br />signer_key&nbsp; &nbsp; = $dir/private/tsakey.pem # The TSA private key (optional)<br />signer_digest&nbsp; = sha256&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # Signing digest to use. (Optional)<br />default_policy&nbsp; &nbsp; = tsa_policy1&nbsp; &nbsp; &nbsp; &nbsp; # Policy if request did not specify it<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional)<br />other_policies&nbsp; &nbsp; = tsa_policy2, tsa_policy3&nbsp; &nbsp; # acceptable policies (optional)<br />digests&nbsp; &nbsp; &nbsp;= sha1, sha256, sha384, sha512&nbsp; # Acceptable message digests (mandatory)<br />accuracy&nbsp; &nbsp; = secs:1, millisecs:500, microsecs:100&nbsp; &nbsp; # (optional)<br />clock_precision_digits&nbsp; = 0&nbsp; &nbsp; # number of digits after dot. (optional)<br />ordering&nbsp; &nbsp; &nbsp; &nbsp; = yes&nbsp; &nbsp; # Is ordering defined for timestamps?<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional, default: no)<br />tsa_name&nbsp; &nbsp; &nbsp; &nbsp; = yes&nbsp; &nbsp; # Must the TSA name be included in the reply?<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional, default: no)<br />ess_cert_id_chain&nbsp; &nbsp; = no&nbsp; &nbsp; # Must the ESS cert id chain be included?<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # (optional, default: no)<br />ess_cert_id_alg&nbsp; &nbsp; &nbsp; &nbsp; = sha1&nbsp; &nbsp; # algorithm to compute certificate<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; # identifier (optional, default: sha1)<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br />[ openssl_def ]</p><p>engines = engine_section<br />[ engine_section ]<br />rtengine = gost_section<br />[ gost_section ]<br />dynamic_path = Users/kolyan_test/bin/sdk-rutoken/openssl/rtengine.dll<br />pkcs11_path = Users/kolyan_test/bin/sdk-rutoken/pkcs11/rtpkcs11ecp.dll</p><p>default_algorithms = CIPHERS, DIGEST, PKEY</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Thu, 15 Dec 2022 19:43:40 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19135/#p19135</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19133/#p19133</link>
			<description><![CDATA[<div class="quotebox"><cite>Аверченко Кирилл пишет:</cite><blockquote><p><strong>kolshik</strong>, библиотека rtpkcs11ecp.dll входит в состав Драйверов Рутокен и находится в папке C:\Windows\system32<br />Библиотека rtpkcs11ecp.so предназначена только для Linux.</p></blockquote></div><p>Понял. Правда это не помогло.<br />Всё ведь так:</p><p>[ openssl_def ]</p><p>engines = engine_section</p><p>[ engine_section ]</p><p>rtengine = gost_section</p><p>[ gost_section ]</p><p>dynamic_path = /Users/kol_n/bin/sdk-rutoken/openssl/rtengine.dll<br />pkcs11_path = /Users/kol_n/bin/sdk-rutoken/pkcs11/tpkcs11ecp.dll<br />#RAND_TOKEN = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP<br />default_algorithms = CIPHERS, DIGEST, PKEY</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Thu, 15 Dec 2022 14:25:26 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19133/#p19133</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19131/#p19131</link>
			<description><![CDATA[<p><strong>kolshik</strong>, библиотека rtpkcs11ecp.dll входит в состав Драйверов Рутокен и находится в папке C:\Windows\system32<br />Библиотека rtpkcs11ecp.so предназначена только для Linux.</p>]]></description>
			<author><![CDATA[null@example.com (Аверченко Кирилл)]]></author>
			<pubDate>Thu, 15 Dec 2022 13:58:21 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19131/#p19131</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19130/#p19130</link>
			<description><![CDATA[<div class="quotebox"><cite>Аверченко Кирилл пишет:</cite><blockquote><p><strong>kolshik</strong>, замените в конфиге строку MODULE_PATH = &lt;путь к библиотеке&gt; rtpkcs11ecp.dll<br />на pkcs11_path = &lt;путь к библиотеке&gt; librtpkcs11ecp.dll<br />Либо закомментируйте строку RAND_TOKEN, поставив перед ней символ #, либо строка должна иметь вид:<br />RAND_TOKEN = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP;serial=35888394 где необходимо указать серийный номер вашего Рутокен ЭЦП.</p></blockquote></div><p>Извиняюсь, я видимо что-то пропустил, а где можно взять библиотеку&nbsp; librtpkcs11ecp.dll? У меня только&nbsp; librtpkcs11ecp.co</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Thu, 15 Dec 2022 13:25:07 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19130/#p19130</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19129/#p19129</link>
			<description><![CDATA[<p><strong>kolshik</strong>, замените в конфиге строку MODULE_PATH = &lt;путь к библиотеке&gt; rtpkcs11ecp.dll<br />на pkcs11_path = &lt;путь к библиотеке&gt; librtpkcs11ecp.dll<br />Либо закомментируйте строку RAND_TOKEN, поставив перед ней символ #, либо строка должна иметь вид:<br />RAND_TOKEN = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP;serial=35888394 где необходимо указать серийный номер вашего Рутокен ЭЦП.</p>]]></description>
			<author><![CDATA[null@example.com (Аверченко Кирилл)]]></author>
			<pubDate>Thu, 15 Dec 2022 12:21:46 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19129/#p19129</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19128/#p19128</link>
			<description><![CDATA[<div class="quotebox"><cite>Аверченко Кирилл пишет:</cite><blockquote><p><strong>kolshik</strong>, можете прислать ошибку, которая у вас возникает?</p></blockquote></div><p>Когда устанавливал openssl 1.1.1 то шибка была:<br />Algorithm gost2012_256 not found </p><p>Сейчас попробовал поставить 3-ю версию. Теперь ошибка:</p><p>C:\Program Files\OpenSSL-Win64&gt;openssl genpkey -algorithm gost2012_256 -pkeyopt paramset:A -out gost.example.ru.key<br />Error initializing gost2012_256 context<br />B80E0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:373:Global default library context, Algorithm (gost2012_256 : 0), Properties (&lt;null&gt;)</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Wed, 14 Dec 2022 21:18:13 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19128/#p19128</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19096/#p19096</link>
			<description><![CDATA[<p><strong>kolshik</strong>, можете прислать ошибку, которая у вас возникает?</p>]]></description>
			<author><![CDATA[null@example.com (Аверченко Кирилл)]]></author>
			<pubDate>Mon, 12 Dec 2022 07:39:11 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19096/#p19096</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/19090/#p19090</link>
			<description><![CDATA[<div class="quotebox"><cite>AnatoliyP пишет:</cite><blockquote><p>Все решилось следующим образом: <br /></p><div class="codebox"><pre><code>openssl_conf = openssl_def

#
# OpenSSL example configuration file.
# This is mostly being used for generation of certificate requests.
#

# Note that you can include other files from the main configuration
openssl_conf = openssl_def

# file using the .include directive.
#.include filename

# This definition stops the following lines choking if HOME isn&#039;t
# defined.
HOME            = .

# Extra OBJECT IDENTIFIER info:
#oid_file        = $ENV::HOME/.oid
oid_section        = new_oids

# To use this configuration file with the &quot;-extfile&quot; option of the
# &quot;openssl x509&quot; utility, name here the section containing the
# X.509v3 extensions to use:
# extensions        =
# (Alternatively, use a configuration file that has only
# X.509v3 extensions in its main [= default] section.)

[ new_oids ]

# We can add new OIDs in here for use by &#039;ca&#039;, &#039;req&#039; and &#039;ts&#039;.
# Add a simple OID like this:
# testoid1=1.2.3.4
# Or use config file substitution like this:
# testoid2=${testoid1}.5.6

# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7

####################################################################
[ ca ]
default_ca    = CA_default        # The default ca section

####################################################################
[ CA_default ]

dir        = ./demoCA        # Where everything is kept
certs        = $dir/certs        # Where the issued certs are kept
crl_dir        = $dir/crl        # Where the issued crl are kept
database    = $dir/index.txt    # database index file.
#unique_subject    = no            # Set to &#039;no&#039; to allow creation of
                    # several certs with same subject.
new_certs_dir    = $dir/newcerts        # default place for new certs.

certificate    = $dir/cacert.pem     # The CA certificate
serial        = $dir/serial         # The current serial number
crlnumber    = $dir/crlnumber    # the current crl number
                    # must be commented out to leave a V1 CRL
crl        = $dir/crl.pem         # The current CRL
private_key    = $dir/private/cakey.pem# The private key

x509_extensions    = usr_cert        # The extensions to add to the cert

# Comment out the following two lines for the &quot;traditional&quot;
# (and highly broken) format.
name_opt     = ca_default        # Subject Name options
cert_opt     = ca_default        # Certificate field options

# Extension copying option: use with caution.
# copy_extensions = copy

# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs
# so this is commented out by default to leave a V1 CRL.
# crlnumber must also be commented out to leave a V1 CRL.
# crl_extensions    = crl_ext

default_days    = 365            # how long to certify for
default_crl_days= 30            # how long before next CRL
default_md    = default        # use public key default MD
preserve    = no            # keep passed DN ordering

# A few difference way of specifying how similar the request should look
# For type CA, the listed attributes must be the same, and the optional
# and supplied fields are just that :-)
policy        = policy_match

# For the CA policy
[ policy_match ]
countryName        = match
stateOrProvinceName    = match
organizationName    = match
organizationalUnitName    = optional
commonName        = supplied
emailAddress        = optional

# For the &#039;anything&#039; policy
# At this point in time, you must list all acceptable &#039;object&#039;
# types.
[ policy_anything ]
countryName        = optional
stateOrProvinceName    = optional
localityName        = optional
organizationName    = optional
organizationalUnitName    = optional
commonName        = supplied
emailAddress        = optional

####################################################################
[ req ]
default_bits        = 2048
default_keyfile     = privkey.pem
distinguished_name    = req_distinguished_name
attributes        = req_attributes
x509_extensions    = v3_ca    # The extensions to add to the self signed cert

# Passwords for private keys if not present they will be prompted for
# input_password = secret
# output_password = secret

# This sets a mask for permitted string types. There are several options.
# default: PrintableString, T61String, BMPString.
# pkix     : PrintableString, BMPString (PKIX recommendation before 2004)
# utf8only: only UTF8Strings (PKIX recommendation after 2004).
# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).
# MASK:XXXX a literal mask value.
# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.
string_mask = utf8only

# req_extensions = v3_req # The extensions to add to a certificate request

[ req_distinguished_name ]
countryName            = Country Name (2 letter code)
countryName_default        = AU
countryName_min            = 2
countryName_max            = 2

stateOrProvinceName        = State or Province Name (full name)
stateOrProvinceName_default    = Some-State

localityName            = Locality Name (eg, city)

0.organizationName        = Organization Name (eg, company)
0.organizationName_default    = Internet Widgits Pty Ltd

# we can do this but it is not needed normally :-)
#1.organizationName        = Second Organization Name (eg, company)
#1.organizationName_default    = World Wide Web Pty Ltd

organizationalUnitName        = Organizational Unit Name (eg, section)
#organizationalUnitName_default    =

commonName            = Common Name (e.g. server FQDN or YOUR name)
commonName_max            = 64

emailAddress            = Email Address
emailAddress_max        = 64

# SET-ex3            = SET extension number 3

[ req_attributes ]
challengePassword        = A challenge password
challengePassword_min        = 4
challengePassword_max        = 20

unstructuredName        = An optional company name

[ usr_cert ]

# These extensions are added when &#039;ca&#039; signs a request.

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType            = server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape&#039;s comment listbox.
nsComment            = &quot;OpenSSL Generated Certificate&quot;

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren&#039;t
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl        = http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This is required for TSA certificates.
# extendedKeyUsage = critical,timeStamping

[ v3_req ]

# Extensions to add to a certificate request

basicConstraints = CA:FALSE
keyUsage = nonRepudiation, digitalSignature, keyEncipherment

[ v3_ca ]


# Extensions for a typical CA


# PKIX recommendation.

subjectKeyIdentifier=hash

authorityKeyIdentifier=keyid:always,issuer

basicConstraints = critical,CA:true

# Key usage: this is typical for a CA certificate. However since it will
# prevent it being used as an test self-signed certificate it is best
# left out by default.
# keyUsage = cRLSign, keyCertSign

# Some might want this also
# nsCertType = sslCA, emailCA

# Include email address in subject alt name: another PKIX recommendation
# subjectAltName=email:copy
# Copy issuer details
# issuerAltName=issuer:copy

# DER hex encoding of an extension: beware experts only!
# obj=DER:02:03
# Where &#039;obj&#039; is a standard or added object
# You can even override a supported extension:
# basicConstraints= critical, DER:30:03:01:01:FF

[ crl_ext ]

# CRL extensions.
# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.

# issuerAltName=issuer:copy
authorityKeyIdentifier=keyid:always

[ proxy_cert_ext ]
# These extensions should be added when creating a proxy certificate

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

basicConstraints=CA:FALSE

# Here are some examples of the usage of nsCertType. If it is omitted
# the certificate can be used for anything *except* object signing.

# This is OK for an SSL server.
# nsCertType            = server

# For an object signing certificate this would be used.
# nsCertType = objsign

# For normal client use this is typical
# nsCertType = client, email

# and for everything including object signing:
# nsCertType = client, email, objsign

# This is typical in keyUsage for a client certificate.
# keyUsage = nonRepudiation, digitalSignature, keyEncipherment

# This will be displayed in Netscape&#039;s comment listbox.
nsComment            = &quot;OpenSSL Generated Certificate&quot;

# PKIX recommendations harmless if included in all certificates.
subjectKeyIdentifier=hash
authorityKeyIdentifier=keyid,issuer

# This stuff is for subjectAltName and issuerAltname.
# Import the email address.
# subjectAltName=email:copy
# An alternative to produce certificates that aren&#039;t
# deprecated according to PKIX.
# subjectAltName=email:move

# Copy subject details
# issuerAltName=issuer:copy

#nsCaRevocationUrl        = http://www.domain.dom/ca-crl.pem
#nsBaseUrl
#nsRevocationUrl
#nsRenewalUrl
#nsCaPolicyUrl
#nsSslServerName

# This really needs to be in place for it to be a proxy certificate.
proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo

####################################################################
[ tsa ]

default_tsa = tsa_config1    # the default TSA section

[ tsa_config1 ]

# These are used by the TSA reply generation only.
dir        = ./demoCA        # TSA root directory
serial        = $dir/tsaserial    # The current serial number (mandatory)
crypto_device    = builtin        # OpenSSL engine to use for signing
signer_cert    = $dir/tsacert.pem     # The TSA signing certificate
                    # (optional)
certs        = $dir/cacert.pem    # Certificate chain to include in reply
                    # (optional)
signer_key    = $dir/private/tsakey.pem # The TSA private key (optional)
signer_digest  = sha256            # Signing digest to use. (Optional)
default_policy    = tsa_policy1        # Policy if request did not specify it
                    # (optional)
other_policies    = tsa_policy2, tsa_policy3    # acceptable policies (optional)
digests     = sha1, sha256, sha384, sha512  # Acceptable message digests (mandatory)
accuracy    = secs:1, millisecs:500, microsecs:100    # (optional)
clock_precision_digits  = 0    # number of digits after dot. (optional)
ordering        = yes    # Is ordering defined for timestamps?
                # (optional, default: no)
tsa_name        = yes    # Must the TSA name be included in the reply?
                # (optional, default: no)
ess_cert_id_chain    = no    # Must the ESS cert id chain be included?
                # (optional, default: no)
ess_cert_id_alg        = sha1    # algorithm to compute certificate
                # identifier (optional, default: sha1)
                
[ openssl_def ]

engines = engine_section

[ engine_section ]

rtengine = gost_section

[ gost_section ]

dynamic_path = /Users/aspostnov/bin/sdk-rutoken/openssl/rtengine/bin/windows-x86_64/lib/rtengine.dll
MODULE_PATH = /Users/aspostnov/bin/sdk-rutoken/pkcs11/lib/windows-x86_64/rtpkcs11ecp.dll
RAND_TOKEN = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP
default_algorithms = CIPHERS, DIGEST, PKEY, RAND</code></pre></div><p>Нужно было указать OPENSSL_CONF вручную, команда &quot;set OPENSSL_CONF=C:\path\to\openssl.cnf&quot; не сработала. В путях path достаточно только C:\Program Files\OpenSSL-Win64\bin</p></blockquote></div><p>Добрый день.<br />Проделал все тоже самое. Установил openssl Win64OpenSSL-1_1_1s. Взял за пример ваш файл конфигурации, поменял на свои папки в которые положил библиотеки, а openssl все равно не видит гост.<br />В чем может быть еще проблема?&nbsp; С C:\path\to\openssl.cnf не понял. Этот файл в итоге должен где-то быть или это идет речь про openssl.cfg?</p>]]></description>
			<author><![CDATA[null@example.com (kolshik)]]></author>
			<pubDate>Sat, 10 Dec 2022 10:02:53 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/19090/#p19090</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/14226/#p14226</link>
			<description><![CDATA[<p><strong>AnatoliyP</strong>, добрый день!</p><p>Большое спасибо за внимательное и вдумчивое чтение документации!</p><p>Блок-схема в конце раздела &quot;Регистрация на портале&quot; соответствует выполнению последних шагов из списка, указанного в начале раздела:<br /></p><ul><li><p>Получаем список подключенных к компьютеру устройств Рутокен ЭЦП 2.0</p></li><li><p>Генерируем ключевую пару по ГОСТ Р 34.10-2012 на выбранном Рутокен ЭЦП 2.0</p></li><li><p>Cоздаем запрос PKCS#10 на сертификат для сгенерированной ключевой пары</p></li><li><p>Отправляем запрос на сервер</p></li><li><p>На сервере создаем сертификат, привязываем к аккаунту (сам сертификат или его дескриптор). Следует отметить, что дескрипторы сертификатов, полученные при вызове функции enumerateCertificates, являются уникальными и неизменными</p></li><li><p>Отправляем сертификат на клиент</p></li><li><p>На клиенте визуализируем полученный сертификат</p></li><li><p>Импортируем полученный сертификат в Рутокен ЭЦП 2.0</p></li></ul><p>Выполнение вызова <strong>parseCertificateFromString</strong> соответствует шагу <strong>визуализируем полученный сертификат</strong>.</p><p>Для других пользователей, зашедших в данную тему, отмечу, что речь в теме, в основном, касается документации, посвященной <a href="https://dev.rutoken.ru/pages/viewpage.action?pageId=15269905">Встраиванию Рутокен ЭЦП 2.0 через Рутокен Плагин</a></p>]]></description>
			<author><![CDATA[null@example.com (Евгений Мироненко)]]></author>
			<pubDate>Tue, 26 May 2020 14:32:27 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/14226/#p14226</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/14222/#p14222</link>
			<description><![CDATA[<p>Еще вопрос по документации:<br />Там где &quot;Регистрация на портале&quot; заключительная картинка.<br />зачем там parseCertificateFromString? <br />Мы же сертификат на фронт передаем в формате .pem, а функция importCertificate принимает сертификат как раз в формате .pem. В общем у меня все сработало без этого дополнительного шага parseCertificateFromString, но он сильно вводит в заблуждение.</p><p>Спасибо!</p>]]></description>
			<author><![CDATA[null@example.com (AnatoliyP)]]></author>
			<pubDate>Tue, 26 May 2020 12:49:00 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/14222/#p14222</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/14221/#p14221</link>
			<description><![CDATA[<p>В общем проблема была в том, что у меня в системе windows7 openSSL установлен в пути:<br />C:\Program Files\OpenSSL-Win64<br />А openssl.cfg Находится <br />C:\Program Files\OpenSSL-Win64\bin\openssl.cfg<br />В настройках &quot;са&quot; внутри openssl.cfg основной путь, что был указан &quot;./demoCA&quot; не сработал.<br />под &quot;.&quot; подразумевалась текущая директория, где находится openssl.cfg т.е. <br />C:\Program Files\OpenSSL-Win64\bin<br />Я в этой директории создавал demoCA, но это не работало.<br />Все сработало, когда я переместил demoCA по адресу &quot;/Users/aspostnov/bin/openSSLca/demoCA&quot;<br />Также там необходимо создать все файлы, что прописаны в настройках для ca в openssl.cfg.</p><p>Почему не работает &quot;-outform PEM -batch&quot; команды &quot;openssl ca -keyfile ca.key -cert ca.crt -in user.csr -out user.crt -outform PEM -batch&quot; я так и не разобрался, в итоге просто удалил и все сработало без &quot;-outform PEM -batch&quot;.</p>]]></description>
			<author><![CDATA[null@example.com (AnatoliyP)]]></author>
			<pubDate>Tue, 26 May 2020 12:43:39 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/14221/#p14221</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/14220/#p14220</link>
			<description><![CDATA[<p><strong>AnatoliyP</strong>, <br /></p><div class="codebox"><pre><code>Правильно ли я понимаю, что после создания сертификата user.crt по подписи user.csr в поле сертификата &quot;Открытый ключ&quot; должен быть тот ключ, который был использован про создании запроса user.csr?</code></pre></div><p>В сертификате должен быть открытой ключ от ключей пары, что есть на токене. Этот же открытый ключ есть в запросе на сертификат.</p><br /><div class="quotebox"><blockquote><p>пробовал так:<br />openssl ca -keyfile ca.key -cert ca.crt -in user.csr -out user.crt<br />ошибка:<br />Using configuration from C:\Program Files\OpenSSL-Win64\bin\openssl.cfg<br />ca: ./demoCA/newcerts is not a directory<br />./demoCA/newcerts: No error</p></blockquote></div><p>Не хватает папки demoCA. Готовую можно взять например из <a href="https://www.rutoken.ru/support/download/get/sdk.html">Рутокен SDK</a>: &lt;sdk&gt;/openssl/rtengine/samples/tool/demoCA</p><div class="codebox"><pre><code>openssl x509 -req -days 365 -in user.csr -signkey ca.key -out user.crt</code></pre></div><p>Все верно, вы сделали. The x509 utility can be used to sign certificates and requests: it can thus behave like a &quot;mini CA&quot; (<a href="https://www.openssl.org/docs/man1.0.2/man1/x509.html">https://www.openssl.org/docs/man1.0.2/man1/x509.html</a>)</p>]]></description>
			<author><![CDATA[null@example.com (Павел Анфимов)]]></author>
			<pubDate>Tue, 26 May 2020 12:12:22 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/14220/#p14220</guid>
		</item>
		<item>
			<title><![CDATA[Re: Установка и настройка openSSL (windows7)]]></title>
			<link>https://forum.rutoken.ru/post/14219/#p14219</link>
			<description><![CDATA[<p>Добрый день!<br />Правильно ли я понимаю, что после создания сертификата user.crt по подписи user.csr в поле сертификата &quot;Открытый ключ&quot; должен быть тот ключ, который был использован про создании запроса user.csr?</p><p>Спасибо!</p>]]></description>
			<author><![CDATA[null@example.com (AnatoliyP)]]></author>
			<pubDate>Tue, 26 May 2020 10:57:44 +0000</pubDate>
			<guid>https://forum.rutoken.ru/post/14219/#p14219</guid>
		</item>
	</channel>
</rss>
