dgst, md5, md4, md2, sha1, sha, mdc2, ripemd160 - Message digests
openssl dgst [-md5 | -md4 | -md2 |-sha1 | -sha | -mdc2 | -ripemd160 |
-dss1] [-c] [-d] [-hex] [-binary] [-out filename] [-sign filename]
[-verify filename] [-prverify filename] [-signature filename] [file..]
[-md5 | -md4 | -md2 | -sha1 | -sha | -mdc2 | -ripemd160] [-c] [-d]
Prints out the digest in two digit groups separated by colons, only
relevant if hex format output is used. Prints out BIO debugging infor‐
mation. Digest is to be output as a hex dump. This is the default case
for a typical digest as opposed to a digital signature. Outputs the
digest or signature in binary form. Filename to output to, or standard
output by default. Digitally signs the digest using the private key in
filename. Verifies the signature using the public key in filename. The
output is either Verification OK or Verification Failure. Verifies the
signature using the private key in filename. The actual signature to
verify. A file or files containing random data used to seed the random
number generator, or an EGD socket. (See RAND_egd(3).) Multiple files
can be specified separated by an OS-dependent character. The separator
is a semicolon (;) for MS-Windows, a comma (,) for OpenVMS, and a colon
(:) for all others. File or files to digest. If no files are specified
then standard input is used.
The digest functions output the message digest of a supplied file or
files in hexadecimal form. They can also be used for digital signing
The digest of choice for all new applications is SHA1. However, other
digests are still widely used.
If you wish to sign or verify data using the DSA algorithm then the
dss1 digest must be used.
A source of random numbers is required for certain signing algorithms,
in particular DSA.
The signing and verify options should only be used if a single file is
being signed or verified.