openssl dgst

message digests 

openssl command


SYNOPSIS

openssl dgst [-md5|-md4|-md2|-sha1|-sha|-sha224|-sha256|-sha384|-sha512|-whirlpool|-mdc2|-ripemd160|-dss1] [-c] [-d] [-hex] [-binary] [-out filename] [-sign filename] [-verify filename] [-prverify filename] [-signature filename] [file...]

openssl [md5|md4|md2|sha1|sha|sha224|sha256|sha384|sha512|whirlpool|mdc2|ripemd160] [-c] [-d] [file...]


DESCRIPTION

The digest functions output the message digest of a supplied file or files in hexadecimal form. They can also be used for digital signing and verification.

Options

-c 

prints out the digest in two digit groups separated by colons, only relevant if hex format output is used.

-d 

prints out BIO debugging information.

-hex 

outputs digest as a hex dump. This is the default case for a "normal" digest as opposed to a digital signature.

-binary 

outputs the digest or signature in binary form.

-out filename 

specifies the file name to output to, or standard output by default.

-sign filename 

digitally signs the digest using the private key in filename.

-verify filename 

verifies the signature using the the public key in filename. The output is either Verification OK or Verification Failure.

-prverify filename 

verifies the signature using the the private key in filename.

-signature filename 

specifies the actual signature to verify.

-rand file(s) 

specifies a file or files containing random data used to seed the random number generator, or an EGD socket. Multiple files can be specified separated by a OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others.

file... 

specifies the file or files to digest. If no files are specified then standard input is used.


NOTES

New or agile applications should use probably use SHA-256. Other digests, particularly SHA-1 and MD5, are still widely used for interoperating with existing formats and protocols.

If you wish to sign or verify data using the DSA algorithm then the dss1 digest must be used.

When signing a file, dgst will automatically determine the algorithm (RSA, ECC, etc) to use for signing based on the private key's ASN.1 info. When verifying signatures, it only handles the RSA, DSA, or ECDSA signature itself, not the related data to identify the signer and algorithm used in formats such as x.509, CMS, and S/MIME.

A source of random numbers is required for certain signing algorithms, in particular ECDSA and DSA.

The signing and verify options should only be used if a single file is being signed or verified.


AVAILABILITY

PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition


PTC MKS Toolkit 10.2 Documentation Build 28.