<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Форум Рутокен &mdash; Подписать файл из командной строки]]></title>
	<link rel="self" href="https://forum.rutoken.ru/feed/atom/topic/4052/" />
	<updated>2023-10-10T12:20:59Z</updated>
	<generator>PunBB</generator>
	<id>https://forum.rutoken.ru/topic/4052/</id>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21714/#p21714" />
			<content type="html"><![CDATA[<p><strong>golovastix</strong>, рады слышать, что все получилось. <br />Хотим обратить ваше внимание, что engine-pkcs11 (из состава OpenSC) и rtengine используют различные конфигурационные настройки.</p>]]></content>
			<author>
				<name><![CDATA[Павел Анфимов]]></name>
				<uri>https://forum.rutoken.ru/user/7338/</uri>
			</author>
			<updated>2023-10-10T12:20:59Z</updated>
			<id>https://forum.rutoken.ru/post/21714/#p21714</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21688/#p21688" />
			<content type="html"><![CDATA[<p>Спасибо за ответ,<br />Мануал вот этот: <a href="https://dev.rutoken.ru/pages/viewpage.action?pageId=113279016">https://dev.rutoken.ru/pages/viewpage.a … =113279016</a></p><p>Действительно pkc11_path, но в мануале по-другому. Кроме того, dll-ка, которая ы WOW64 не подходит, нужна та, которая в System32, хотя opnssl 64-битный.</p><p>Спасибо</p>]]></content>
			<author>
				<name><![CDATA[golovastix]]></name>
				<uri>https://forum.rutoken.ru/user/14133/</uri>
			</author>
			<updated>2023-10-09T21:59:25Z</updated>
			<id>https://forum.rutoken.ru/post/21688/#p21688</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21683/#p21683" />
			<content type="html"><![CDATA[<p><strong>golovastix</strong>, добрый день!</p><div class="quotebox"><cite>golovastix пишет:</cite><blockquote><p>В мануале по поводу OpenSSL 3.0 написано:</p></blockquote></div><p>Пожалуйста, поясните, о каком мануале идет речь?</p><p>При использовании rtengine настойчиво рекомендуется использовать мануал по пути <a href="https://download.rutoken.ru/Rutoken/SDK/rutoken-sdk-latest.zip?action=get&amp;path=sdk%2Fopenssl%2Fsamples%2Ftool%2FREADME.md">sdk/openssl/samples/tool/README.md</a> <a href="https://www.rutoken.ru/developers/sdk/">Рутокен SDK</a>.</p><p>Хинт: задание пути к библиотеке rtpkcs11ecp для rtengine задается не параметром &quot;MODULE_PATH&quot;, а параметром &quot;pkcs11_path&quot;</p>]]></content>
			<author>
				<name><![CDATA[Евгений Мироненко]]></name>
				<uri>https://forum.rutoken.ru/user/8673/</uri>
			</author>
			<updated>2023-10-09T08:57:45Z</updated>
			<id>https://forum.rutoken.ru/post/21683/#p21683</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21677/#p21677" />
			<content type="html"><![CDATA[<p><strong>golovastix</strong>, добрый день!</p><p>1. Убедитесь, пожалуйста, что используете rtengine для OpenSSL 3.0: <a href="https://www.rutoken.ru/support/download/openssl/">https://www.rutoken.ru/support/download/openssl/</a></p><p>2. Закомментируйте строки <br /></p><div class="codebox"><pre><code>rand_token = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP
enable_rand = yes</code></pre></div><p>и проверьте работу.</p><p>3. Для Рутокен ЭЦП на всех платформах необходимо использовать библиотеку rtpkcs11ecp.</p>]]></content>
			<author>
				<name><![CDATA[Павел Анфимов]]></name>
				<uri>https://forum.rutoken.ru/user/7338/</uri>
			</author>
			<updated>2023-10-09T07:06:48Z</updated>
			<id>https://forum.rutoken.ru/post/21677/#p21677</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21675/#p21675" />
			<content type="html"><![CDATA[<p>Похоже была ошибка в пути к файлам. Сейчас вот так:</p><div class="codebox"><pre><code>PS C:\Users\Golovastik\bin&gt; openssl engine
FATAL: Startup failure (dev note: apps_startup()) for C:\Program Files\OpenSSL-Win64\bin\openssl.exe
682F0000:error:13000089:engine routines:int_ctrl_helper:invalid cmd name:crypto\engine\eng_ctrl.c:90:
682F0000:error:13000089:engine routines:ENGINE_ctrl_cmd_string:invalid cmd name:crypto\engine\eng_ctrl.c:258:
682F0000:error:13000066:engine routines:int_engine_configure:engine configuration error:crypto\engine\eng_cnf.c:139:section=pkcs11_section, name=MODULE_PATH, value=C:\Users\Golovastik\bin\rtpksc11ecp.dll
682F0000:error:0700006D:configuration file routines:module_run:module initialization error:crypto\conf\conf_mod.c:276:module=engines, value=engine_section retcode=-1</code></pre></div><p>кусок конфигурации:<br /></p><div class="codebox"><pre><code>[openssl_init]
engines = engine_section
providers = provider_sect

[engine_section]
rtengine = pkcs11_section
 
[pkcs11_section]
engine_id = rtengine
dynamic_path = C:\\Users\\Golovastik\\bin\\rtengine.dll
MODULE_PATH = C:\\Users\\Golovastik\\bin\\rtpksc11ecp.dll
rand_token = pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP
enable_rand = yes
default_algorithms = ALL</code></pre></div>]]></content>
			<author>
				<name><![CDATA[golovastix]]></name>
				<uri>https://forum.rutoken.ru/user/14133/</uri>
			</author>
			<updated>2023-10-06T16:19:26Z</updated>
			<id>https://forum.rutoken.ru/post/21675/#p21675</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21674/#p21674" />
			<content type="html"><![CDATA[<p>Здравствуйте,<br />1.<br /><span class="postimg"><a class="fancybox fancybox.image" rel="group" href="https://forum.rutoken.ru/uploads/images/2023/10/d5efce80d63de544d31fa8dd5636b470.png"><img class="fb_img" src="https://forum.rutoken.ru/uploads/previews/2023/10/d5efce80d63de544d31fa8dd5636b470.png" alt="" /></a></span> </p><p>2. Rutoken ECP 2.0 (2100)</p><p>Мне кажется, что проблема из-за того, что я использую OpenSSL 3.1.3 19. Может rtengine с ней не совместим<br />В мануале по поводу OpenSSL 3.0 написано:<br /></p><div class="codebox"><pre><code>dynamic_path = /path/to/engine_pkcs11.so //например, /usr/lib/x86_64-linux-gnu/engines-3/pkcs11.so</code></pre></div><p>Но я не понимаю где в винде найти pkcs11.dll. Я использую rtengine.dll, пробовал opensc_pkcs11.dll.<br />Результат тот же</p>]]></content>
			<author>
				<name><![CDATA[golovastix]]></name>
				<uri>https://forum.rutoken.ru/user/14133/</uri>
			</author>
			<updated>2023-10-06T16:12:21Z</updated>
			<id>https://forum.rutoken.ru/post/21674/#p21674</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21667/#p21667" />
			<content type="html"><![CDATA[<p><strong>golovastix</strong>, добрый день!</p><p>Расскажите, пожалуйста:</p><p>1) какого <a href="https://dev.rutoken.ru/pages/viewpage.action?pageId=98937400#id-%D0%9E%D0%B2%D0%B8%D0%B4%D0%B0%D1%85%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%B2%D1%8B%D1%85%D0%BD%D0%BE%D1%81%D0%B8%D1%82%D0%B5%D0%BB%D0%B5%D0%B9%D0%B8%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%82%D0%B0%D1%85%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%B9%D1%8D%D0%BB%D0%B5%D0%BA%D1%82%D1%80%D0%BE%D0%BD%D0%BD%D0%BE%D0%B9%D0%BF%D0%BE%D0%B4%D0%BF%D0%B8%D1%81%D0%B8%D0%BF%D1%80%D0%BE%D1%81%D1%82%D1%8B%D0%BC%D0%B8%D1%81%D0%BB%D0%BE%D0%B2%D0%B0%D0%BC%D0%B8-%D0%A0%D0%B0%D0%B7%D0%BD%D0%BE%D0%B2%D0%B8%D0%B4%D0%BD%D0%BE%D1%81%D1%82%D1%8C%D0%BA%D0%BB%D1%8E%D1%87%D0%B5%D0%B9%D1%8D%D0%BB%D0%B5%D0%BA%D1%82%D1%80%D0%BE%D0%BD%D0%BD%D0%BE%D0%B9%D0%BF%D0%BE%D0%B4%D0%BF%D0%B8%D1%81%D0%B8">формата у вас ключевой контейнер</a> на Рутокене.</p><p>Для этого, пришлите, пожалуйста, скриншот &quot;Панели управления Рутокен&quot; на вкладке Сертификаты</p><p>2) Уточните, пожалуйста, какой модели Рутокен вы используете? Узнать модель Рутокен можно по <a href="http://kb.rutoken.ru/display/KB/RU1001">инструкции</a>.</p>]]></content>
			<author>
				<name><![CDATA[Павел Анфимов]]></name>
				<uri>https://forum.rutoken.ru/user/7338/</uri>
			</author>
			<updated>2023-10-06T08:12:24Z</updated>
			<id>https://forum.rutoken.ru/post/21667/#p21667</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21665/#p21665" />
			<content type="html"><![CDATA[<p>Похоже добился прогресса:<br /></p><div class="codebox"><pre><code>PS C:\Users\Golovastik\bin&gt; openssl dgst -keyform engine -sign &quot;pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP;serial=4108752d&quot; -engine pkcs11 -out signature &quot;data_to_sig&quot;
Invalid engine &quot;pkcs11&quot;
58420000:error:12800067:DSO support routines:win32_load:could not load the shared library:crypto\dso\dso_win32.c:108:filename(C:\Program Files\OpenSSL\lib\engines-3\pkcs11.dll)
58420000:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto\dso\dso_lib.c:152:
58420000:error:13000084:engine routines:dynamic_load:dso not found:crypto\engine\eng_dyn.c:442:
58420000:error:13000074:engine routines:ENGINE_by_id:no such engine:crypto\engine\eng_list.c:433:id=pkcs11
58420000:error:12800067:DSO support routines:win32_load:could not load the shared library:crypto\dso\dso_win32.c:108:filename(pkcs11.dll)
58420000:error:12800067:DSO support routines:DSO_load:could not load the shared library:crypto\dso\dso_lib.c:152:
58420000:error:13000084:engine routines:dynamic_load:dso not found:crypto\engine\eng_dyn.c:442:
No engine specified for loading private key
No filename or uri specified for loading
 private key</code></pre></div><p>Я понимаю, что что-то не в порядке с uri. Но возникает вопрос -- она хочит загрузить privat key из токена? Он вроде неизвлекаемый.</p>]]></content>
			<author>
				<name><![CDATA[golovastix]]></name>
				<uri>https://forum.rutoken.ru/user/14133/</uri>
			</author>
			<updated>2023-10-06T02:39:49Z</updated>
			<id>https://forum.rutoken.ru/post/21665/#p21665</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Подписать файл из командной строки]]></title>
			<link rel="alternate" href="https://forum.rutoken.ru/post/21663/#p21663" />
			<content type="html"><![CDATA[<p>Здравствуйте,</p><p>У меня есть ИП-шный токен.<br />Хочется сделать скрипт для подписания файлов, которые бы верифицировались на госуслугах. Чтобы не пользоватся КриптоПро. Я до конца так и не понял возможно ли это в принципе.<br />Я попытался настроить Openssl как написано в мануалах, но у меня ничего не вышло. Такое впечатление, что не находит engine.</p><p>openssl.cnf:</p><div class="codebox"><pre><code>#
# OpenSSL example configuration file.
# See doc/man5/config.pod for more info.
#
# This is mostly being used for generation of certificate requests,
# but may be used for auto loading of providers

# Note that you can include other files from the main configuration
# file using the .include directive.
#.include filename

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

# Use this in order to automatically load providers.
openssl_conf = openssl_init


# Comment out the next line to ignore configuration errors
config_diagnostics = 1

# 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

# For FIPS
# Optionally include a file that is generated by the OpenSSL fipsinstall
# application. This file contains configuration data required by the OpenSSL
# fips provider. It contains a named section e.g. [fips_sect] which is
# referenced from the [provider_sect] below.
# Refer to the OpenSSL security policy for more information.
# .include fipsmodule.cnf

[openssl_init]
engines = engine_section
providers = provider_sect

[engine_section]
pkcs11 = pkcs11_section
 
[pkcs11_section]
engine_id = pkcs11
dynamic_path = C:\\Users\\Golovastik\\bin\\rtengine.dll
MODULE_PATH = C:\\Users\\Golovastik\\bin\\rtpkcs11ecp.dll
default_algorithms = ALL
 





# List of providers to load
[provider_sect]
default = default_sect
# The fips section name should match the section name inside the
# included fipsmodule.cnf.
# fips = fips_sect

# If no providers are activated explicitly, the default one is activated implicitly.
# See man 7 OSSL_PROVIDER-default for more details.
#
# If you add a section explicitly activating any other provider(s), you most
# probably need to explicitly activate the default provider, otherwise it
# becomes unavailable in openssl.  As a consequence applications depending on
# OpenSSL may not work correctly which could lead to significant system
# problems including inability to remotely access the system.
[default_sect]
# activate = 1


####################################################################
[ 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

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

# 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

# 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

# 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

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

# 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

# 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)

[insta] # CMP using Insta Demo CA
# Message transfer
server = pki.certificate.fi:8700
# proxy = # set this as far as needed, e.g., http://192.168.1.1:8080
# tls_use = 0
path = pkix/

# Server authentication
recipient = &quot;/C=FI/O=Insta Demo/CN=Insta Demo CA&quot; # or set srvcert or issuer
ignore_keyusage = 1 # potentially needed quirk
unprotected_errors = 1 # potentially needed quirk
extracertsout = insta.extracerts.pem

# Client authentication
ref = 3078 # user identification
secret = pass:insta # can be used for both client and server side

# Generic message options
cmd = ir # default operation, can be overridden on cmd line with, e.g., kur

# Certificate enrollment
subject = &quot;/CN=openssl-cmp-test&quot;
newkey = insta.priv.pem
out_trusted = apps/insta.ca.crt # does not include keyUsage digitalSignature
certout = insta.cert.pem

[pbm] # Password-based protection for Insta CA
# Server and client authentication
ref = $insta::ref # 3078
secret = $insta::secret # pass:insta

[signature] # Signature-based protection for Insta CA
# Server authentication
trusted = $insta::out_trusted # apps/insta.ca.crt

# Client authentication
secret = # disable PBM
key = $insta::newkey # insta.priv.pem
cert = $insta::certout # insta.cert.pem

[ir]
cmd = ir

[cr]
cmd = cr

[kur]
# Certificate update
cmd = kur
oldcert = $insta::certout # insta.cert.pem

[rr]
# Certificate revocation
cmd = rr
oldcert = $insta::certout # insta.cert.pem

  </code></pre></div><p>И вот что получается в результате:<br /></p><div class="codebox"><pre><code> C:\Users\Golovastik\bin&gt;openssl dgst -keyform engine -sign &quot;pkcs11:manufacturer=Aktiv%20Co.;model=Rutoken%20ECP;serial=4108752d&quot; -engine rtengine -out signature &quot;data_to_sign&quot;
FATAL: Startup failure (dev note: apps_startup()) for openssl
A01E0000:error:13000089:engine routines:int_ctrl_helper:invalid cmd name:crypto\engine\eng_ctrl.c:90:
A01E0000:error:13000089:engine routines:ENGINE_ctrl_cmd_string:invalid cmd name:crypto\engine\eng_ctrl.c:258:
A01E0000:error:13000066:engine routines:int_engine_configure:engine configuration error:crypto\engine\eng_cnf.c:139:section=pkcs11_section, name=MODULE_PATH, value=C:\Users\Golovastik\bin\rtpkcs11ecp.dll
A01E0000:error:0700006D:configuration file routines:module_run:module initialization error:crypto\conf\conf_mod.c:276:module=engines, value=engine_section retcode=-1 </code></pre></div>]]></content>
			<author>
				<name><![CDATA[golovastix]]></name>
				<uri>https://forum.rutoken.ru/user/14133/</uri>
			</author>
			<updated>2023-10-05T22:55:06Z</updated>
			<id>https://forum.rutoken.ru/post/21663/#p21663</id>
		</entry>
</feed>
