DGST(1) OpenSSL DGST(1) NNAAMMEE dgst, sha, sha1, mdc2, ripemd160, sha224, sha256, sha384, sha512, md2, md4, md5, dss1 - message digests SSYYNNOOPPSSIISS ooppeennssssll ddggsstt [--sshhaa||--sshhaa11||--mmddcc22||--rriippeemmdd116600||--sshhaa222244||--sshhaa225566||--sshhaa338844||--sshhaa551122||--mmdd22||--mmdd44||--mmdd55||--ddssss11] [--cc] [--dd] [--hheexx] [--bbiinnaarryy] [--rr] [--nnoonn--ffiippss--aallllooww] [--oouutt ffiilleennaammee] [--ssiiggnn ffiilleennaammee] [--kkeeyyffoorrmm aarrgg] [--ppaassssiinn aarrgg] [--vveerriiffyy ffiilleennaammee] [--pprrvveerriiffyy ffiilleennaammee] [--ssiiggnnaattuurree ffiilleennaammee] [--hhmmaacc kkeeyy] [--nnoonn--ffiippss--aallllooww] [--ffiippss--ffiinnggeerrpprriinntt] [ffiillee......] ooppeennssssll [_d_i_g_e_s_t] [......] DDEESSCCRRIIPPTTIIOONN The digest functions output the message digest of a supplied file or files in hexadecimal. The digest functions also generate and verify digital signatures using message digests. OOPPTTIIOONNSS --cc print out the digest in two digit groups separated by colons, only relevant if hheexx format output is used. --dd print out BIO debugging information. --hheexx digest is to be output as a hex dump. This is the default case for a "normal" digest as opposed to a digital signature. See NOTES below for digital signatures using --hheexx. --bbiinnaarryy output the digest or signature in binary form. --rr output the digest in the "coreutils" format used by programs like sshhaa11ssuumm. --nnoonn--ffiippss--aallllooww Allow use of non FIPS digest when in FIPS mode. This has no effect when not in FIPS mode. --oouutt ffiilleennaammee filename to output to, or standard output by default. --ssiiggnn ffiilleennaammee digitally sign the digest using the private key in "filename". --kkeeyyffoorrmm aarrgg Specifies the key format to sign digest with. The DER, PEM, P12, and ENGINE formats are supported. --eennggiinnee iidd Use engine iidd for operations (including private key storage). This engine is not used as source for digest algorithms, unless it is also specified in the configuration file. --ssiiggoopptt nnmm::vv Pass options to the signature algorithm during sign or verify oper- ations. Names and values of these options are algorithm-specific. --ppaassssiinn aarrgg the private key password source. For more information about the format of aarrgg see the PPAASSSS PPHHRRAASSEE AARRGGUUMMEENNTTSS section in _o_p_e_n_s_s_l(1). --vveerriiffyy ffiilleennaammee verify the signature using the the public key in "filename". The output is either "Verification OK" or "Verification Failure". --pprrvveerriiffyy ffiilleennaammee verify the signature using the the private key in "filename". --ssiiggnnaattuurree ffiilleennaammee the actual signature to verify. --hhmmaacc kkeeyy create a hashed MAC using "key". --mmaacc aallgg create MAC (keyed Message Authentication Code). The most popular MAC algorithm is HMAC (hash-based MAC), but there are other MAC algorithms which are not based on hash, for instance ggoosstt--mmaacc algo- rithm, supported by ccccggoosstt engine. MAC keys and other options should be set via --mmaaccoopptt parameter. --mmaaccoopptt nnmm::vv Passes options to MAC algorithm, specified by --mmaacc key. Following options are supported by both by HHMMAACC and ggoosstt--mmaacc: kkeeyy::ssttrriinngg Specifies MAC key as alphnumeric string (use if key contain printable characters only). String length must conform to any restrictions of the MAC algorithm for example exactly 32 chars for gost-mac. hheexxkkeeyy::ssttrriinngg Specifies MAC key in hexadecimal form (two hex digits per byte). Key length must conform to any restrictions of the MAC algorithm for example exactly 32 chars for gost-mac. --rraanndd ffiillee((ss)) a file or files containing random data used to seed the random num- ber generator, or an EGD socket (see _R_A_N_D___e_g_d(3)). Multiple files can be specified separated by a OS-dependent character. The sepa- rator is ;; for MS-Windows, ,, for OpenVMS, and :: for all others. --nnoonn--ffiippss--aallllooww enable use of non-FIPS algorithms such as MD5 even in FIPS mode. --ffiippss--ffiinnggeerrpprriinntt compute HMAC using a specific key for certain OpenSSL-FIPS opera- tions. ffiillee...... file or files to digest. If no files are specified then standard input is used. EEXXAAMMPPLLEESS To create a hex-encoded message digest of a file: openssl dgst -md5 -hex file.txt To sign a file using SHA-256 with binary file output: openssl dgst -sha256 -sign privatekey.pem -out signature.sign file.txt To verify a signature: openssl dgst -sha256 -verify publickey.pem \ -signature signature.sign \ file.txt NNOOTTEESS The digest of choice for all new applications is SHA1. Other digests are however still widely used. When signing a file, ddggsstt 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. Hex signatures cannot be verified using ooppeennssssll. Instead, use "xxd -r" or similar program to transform the hex signature into a binary signa- ture prior to verification. 1.0.1u 2016-09-22 DGST(1)