=pod =head1 NAME openssl - OpenSSL command line program =head1 SYNOPSIS B I [ I ... ] [ I ... ] B BI [ I ] B B<-help> | B<-version> =head1 DESCRIPTION OpenSSL is a cryptography toolkit implementing the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) network protocols and related cryptography standards required by them. The B program is a command line program for using the various cryptography functions of OpenSSL's B library from the shell. It can be used for o Creation and management of private keys, public keys and parameters o Public key cryptographic operations o Creation of X.509 certificates, CSRs and CRLs o Calculation of Message Digests and Message Authentication Codes o Encryption and Decryption with Ciphers o SSL/TLS Client and Server Tests o Handling of S/MIME signed or encrypted mail o Timestamp requests, generation and verification =head1 COMMAND SUMMARY The B program provides a rich variety of commands (I in the L above). Each command can have many options and argument parameters, shown above as I and I. Detailed documentation and use cases for most standard subcommands are available (e.g., L). The subcommand L may be used to list subcommands. The command BI tests whether a command of the specified name is available. If no command named I exists, it returns 0 (success) and prints BI; otherwise it returns 1 and prints I. In both cases, the output goes to B and nothing is printed to B. Additional command line arguments are always ignored. Since for each cipher there is a command of the same name, this provides an easy way for shell scripts to test for the availability of ciphers in the B program. (BI is not able to detect pseudo-commands such as B, B, or BI itself.) =head2 Configuration Option Many commands use an external configuration file for some or all of their arguments and have a B<-config> option to specify that file. The default name of the file is F in the default certificate storage area, which can be determined from the L command using the B<-d> or B<-a> option. The environment variable B can be used to specify a different file location or to disable loading a configuration (using the empty string). Among others, the configuration file can be used to load modules and to specify parameters for generating certificates and random numbers. See L for details. =head2 Standard Commands =over 4 =item B Parse an ASN.1 sequence. =item B Certificate Authority (CA) Management. =item B Cipher Suite Description Determination. =item B CMS (Cryptographic Message Syntax) command. =item B Certificate Revocation List (CRL) Management. =item B CRL to PKCS#7 Conversion. =item B Message Digest calculation. MAC calculations are superseded by L. =item B Generation and Management of Diffie-Hellman Parameters. Superseded by L and L. =item B DSA Data Management. =item B DSA Parameter Generation and Management. Superseded by L and L. =item B EC (Elliptic curve) key processing. =item B EC parameter manipulation and generation. =item B Encryption, decryption, and encoding. =item B Engine (loadable module) information and manipulation. =item B Error Number to Error String Conversion. =item B FIPS configuration installation. =item B Generation of DSA Private Key from Parameters. Superseded by L and L. =item B Generation of Private Key or Parameters. =item B Generation of RSA Private Key. Superseded by L. =item B Display information about a command's options. =item B Display diverse information built into the OpenSSL libraries. =item B Key Derivation Functions. =item B List algorithms and features. =item B Message Authentication Code Calculation. =item B Create or examine a Netscape certificate sequence. =item B Online Certificate Status Protocol command. =item B Generation of hashed passwords. =item B PKCS#12 Data Management. =item B PKCS#7 Data Management. =item B PKCS#8 format private key conversion command. =item B Public and private key management. =item B Public key algorithm parameter management. =item B Public key algorithm cryptographic operation command. =item B Compute prime numbers. =item B Generate pseudo-random bytes. =item B Create symbolic links to certificate and CRL files named by the hash values. =item B PKCS#10 X.509 Certificate Signing Request (CSR) Management. =item B RSA key management. =item B RSA command for signing, verification, encryption, and decryption. Superseded by L. =item B This implements a generic SSL/TLS client which can establish a transparent connection to a remote server speaking SSL/TLS. It's intended for testing purposes only and provides only rudimentary interface functionality but internally uses mostly all functionality of the OpenSSL B library. =item B This implements a generic SSL/TLS server which accepts connections from remote clients speaking SSL/TLS. It's intended for testing purposes only and provides only rudimentary interface functionality but internally uses mostly all functionality of the OpenSSL B library. It provides both an own command line oriented protocol for testing SSL functions and a simple HTTP response facility to emulate an SSL/TLS-aware webserver. =item B SSL Connection Timer. =item B SSL Session Data Management. =item B S/MIME mail processing. =item B Algorithm Speed Measurement. =item B SPKAC printing and generating command. =item B Maintain SRP password file. This command is deprecated. =item B Command to list and display certificates, keys, CRLs, etc. =item B Time Stamping Authority command. =item B X.509 Certificate Verification. See also the L manual page. =item B OpenSSL Version Information. =item B X.509 Certificate Data Management. =back =head2 Message Digest Commands =over 4 =item B BLAKE2b-512 Digest =item B BLAKE2s-256 Digest =item B MD2 Digest =item B MD4 Digest =item B MD5 Digest =item B MDC2 Digest =item B RMD-160 Digest =item B SHA-1 Digest =item B SHA-2 224 Digest =item B SHA-2 256 Digest =item B SHA-2 384 Digest =item B SHA-2 512 Digest =item B SHA-3 224 Digest =item B SHA-3 256 Digest =item B SHA-3 384 Digest =item B SHA-3 512 Digest =item B KECCAK 224 Digest =item B KECCAK 256 Digest =item B KECCAK 384 Digest =item B KECCAK 512 Digest =item B SHA-3 SHAKE128 Digest =item B SHA-3 SHAKE256 Digest =item B SM3 Digest =back =head2 Encryption, Decryption, and Encoding Commands The following aliases provide convenient access to the most used encodings and ciphers. Depending on how OpenSSL was configured and built, not all ciphers listed here may be present. See L for more information. =over 4 =item B, B, B, B, B, B AES-128 Cipher =item B, B, B, B, B, B AES-192 Cipher =item B, B, B, B, B, B AES-256 Cipher =item B, B, B, B, B, B Aria-128 Cipher =item B, B, B, B, B, B Aria-192 Cipher =item B, B, B, B, B, B Aria-256 Cipher =item B Base64 Encoding =item B, B, B, B, B Blowfish Cipher =item B, B, B, B, B, B Camellia-128 Cipher =item B, B, B, B, B, B Camellia-192 Cipher =item B, B, B, B, B, B Camellia-256 Cipher =item B, B CAST Cipher =item B, B, B, B CAST5 Cipher =item B Chacha20 Cipher =item B, B, B, B, B, B, B, B, B DES Cipher =item B, B, B, B, B, B Triple-DES Cipher =item B, B, B, B, B IDEA Cipher =item B, B, B, B, B RC2 Cipher =item B RC4 Cipher =item B, B, B, B, B RC5 Cipher =item B, B, B, B, B SEED Cipher =item B, B, B, B, B, B SM4 Cipher =back =head1 OPTIONS Details of which options are available depend on the specific command. This section describes some common options with common behavior. =head2 Program Options These options can be specified without a command specified to get help or version information. =over 4 =item B<-help> Provides a terse summary of all options. For more detailed information, each command supports a B<-help> option. Accepts B<--help> as well. =item B<-version> Provides a terse summary of the B program version. For more detailed information see L. Accepts B<--version> as well. =back =head2 Common Options =over 4 =item B<-help> If an option takes an argument, the "type" of argument is also given. =item B<--> This terminates the list of options. It is mostly useful if any filename parameters start with a minus sign: openssl verify [flags...] -- -cert1.pem... =back =head2 Format Options See L for manual page. =head2 Pass Phrase Options See the L manual page. =head2 Random State Options Prior to OpenSSL 1.1.1, it was common for applications to store information about the state of the random-number generator in a file that was loaded at startup and rewritten upon exit. On modern operating systems, this is generally no longer necessary as OpenSSL will seed itself from a trusted entropy source provided by the operating system. These flags are still supported for special platforms or circumstances that might require them. It is generally an error to use the same seed file more than once and every use of B<-rand> should be paired with B<-writerand>. =over 4 =item B<-rand> I A file or files containing random data used to seed the random number generator. Multiple files can be specified separated by an OS-dependent character. The separator is C<;> for MS-Windows, C<,> for OpenVMS, and C<:> for all others. Another way to specify multiple files is to repeat this flag with different filenames. =item B<-writerand> I Writes the seed data to the specified I upon exit. This file can be used in a subsequent command invocation. =back =head2 Certificate Verification Options See the L manual page. =head2 Name Format Options See the L manual page. =head2 TLS Version Options Several commands use SSL, TLS, or DTLS. By default, the commands use TLS and clients will offer the lowest and highest protocol version they support, and servers will pick the highest version that the client offers that is also supported by the server. The options below can be used to limit which protocol versions are used, and whether TCP (SSL and TLS) or UDP (DTLS) is used. Note that not all protocols and flags may be available, depending on how OpenSSL was built. =over 4 =item B<-ssl3>, B<-tls1>, B<-tls1_1>, B<-tls1_2>, B<-tls1_3>, B<-no_ssl3>, B<-no_tls1>, B<-no_tls1_1>, B<-no_tls1_2>, B<-no_tls1_3> These options require or disable the use of the specified SSL or TLS protocols. When a specific TLS version is required, only that version will be offered or accepted. Only one specific protocol can be given and it cannot be combined with any of the B options. The B options do not work with B and B commands but work with B and B commands. =item B<-dtls>, B<-dtls1>, B<-dtls1_2> These options specify to use DTLS instead of TLS. With B<-dtls>, clients will negotiate any supported DTLS protocol version. Use the B<-dtls1> or B<-dtls1_2> options to support only DTLS1.0 or DTLS1.2, respectively. =back =head2 Engine Options =over 4 =item B<-engine> I Load the engine identified by I and use all the methods it implements (algorithms, key storage, etc.), unless specified otherwise in the command-specific documentation or it is configured to do so, as described in L. The engine will be used for key ids specified with B<-key> and similar options when an option like B<-keyform engine> is given. A special case is the C engine, which is meant just for internal OpenSSL testing purposes and supports loading keys, parameters, certificates, and CRLs from files. When this engine is used, files with such credentials are read via this engine. Using the C schema is optional; a plain file (path) name will do. =back Options specifying keys, like B<-key> and similar, can use the generic OpenSSL engine key loading URI scheme C to retrieve private keys and public keys. The URI syntax is as follows, in simplified form: org.openssl.engine:{engineid}:{keyid} Where C<{engineid}> is the identity/name of the engine, and C<{keyid}> is a key identifier that's acceptable by that engine. For example, when using an engine that interfaces against a PKCS#11 implementation, the generic key URI would be something like this (this happens to be an example for the PKCS#11 engine that's part of OpenSC): -key org.openssl.engine:pkcs11:label_some-private-key As a third possibility, for engines and providers that have implemented their own L, C should not be necessary. For a PKCS#11 implementation that has implemented such a loader, the PKCS#11 URI as defined in RFC 7512 should be possible to use directly: -key pkcs11:object=some-private-key;pin-value=1234 =head2 Provider Options =over 4 =item B<-provider> I Load and initialize the provider identified by I. The I can be also a path to the provider module. In that case the provider name will be the specified path and not just the provider module name. Interpretation of relative paths is platform specific. The configured "MODULESDIR" path, B environment variable, or the path specified by B<-provider-path> is prepended to relative paths. See L for a more detailed description. =item B<-provider-path> I Specifies the search path that is to be used for looking for providers. Equivalently, the B environment variable may be set. =item B<-propquery> I Specifies the I to be used when fetching algorithms from the loaded providers. See L for a more detailed description. =back =head1 ENVIRONMENT The OpenSSL libraries can take some configuration parameters from the environment. For information about all environment variables used by the OpenSSL libraries, such as B, B, and B, see L. For information about the use of environment variables in configuration, see L. For information about specific commands, see L, L, and L. For information about querying or specifying CPU architecture flags, see L, L and L. =head1 SEE ALSO L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L, L. L, L =head1 HISTORY The B -IB<-algorithms> options were added in OpenSSL 1.0.0; For notes on the availability of other commands, see their individual manual pages. The B<-issuer_checks> option is deprecated as of OpenSSL 1.1.0 and is silently ignored. The B<-xcertform> and B<-xkeyform> options are obsolete since OpenSSL 3.0 and have no effect. The interactive mode, which could be invoked by running C with no further arguments, was removed in OpenSSL 3.0, and running that program with no arguments is now equivalent to C. =head1 COPYRIGHT Copyright 2000-2024 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. =cut