Arrange the recipient-side digital signature verification workflow in the correct chronological order.

### The order 1. **Obtain the sender's public key**: verification requires the public key corresponding to the sender’s signing key. 2. **Receive or access the signed document and its signature file**: the verification command needs both the document and the signature being checked. 3. **Run the OpenSSL (Open Secure Sockets Layer) verification command with the public key, signature file, and document**: the command compares the signature with the supplied content using the public key. 4. **Check the command's verification result**: the result tells the recipient whether that signature verifies for that document under the supplied key. ### The concept The verification process needs three relevant inputs: the public key, the signature file, and the document. The public key checks a signature made with the corresponding private key. The document matters because verification is about the content that was signed; checking a signature without the intended document would not establish that the supplied document matches it. The output should be interpreted as a signature check, not as proof that the document is secret or that the message has never been reused. ### Terms - **OpenSSL**: software that includes the command-line cryptographic tools used in the example. - **Public key**: the key used to verify a signature made with its paired private key. - **Signature file**: the file containing the signature to be checked. - **Verification**: checking whether the signature is valid for the supplied document and public key. - **Private key**: the paired key used by the sender to create the signature. ### Remember Before verification, have the public key, the signature file, and the exact document that is being checked.