Arrange the recipient’s signature-verification workflow in the correct order.

### Why this is right Verification begins with the signed data, uses the signer’s public key to check the signature, and then relies on the hash comparison to detect changes. Acceptance follows only if the checks succeed. ### The concept The signer’s private key creates the signature, while the corresponding public key supports verification. The document’s hash acts as a fingerprint: changing the document changes the calculated hash. A successful check supports the signer’s authenticity and the document’s integrity, but it does not conceal the document or prove that the communication is fresh. ### The order 1. **The recipient obtains the document and signature.** There can be no verification until both are available. 2. **The recipient uses the signer’s public key to verify the signature.** The public key corresponds to the private key used to sign. 3. **The recipient checks whether the document’s contents correspond to the signed hash.** This detects changes to the document. 4. **The recipient accepts the signature as evidence of authenticity and integrity if verification succeeds.** The conclusion follows from the verification checks. ### Terms - **Hash**: A fingerprint calculated from the document’s contents. - **Authenticity**: Evidence that data came from the claimed signer. - **Integrity**: Evidence that data has not been improperly changed. ### Remember Verify the signature and data correspondence before relying on a signed document.