A digital signature is a cryptographic mechanism that allows the recipient of a message to verify the authenticity and integrity of the message. The sender uses their private key to create the signature, and the recipient uses the sender's public key to verify it. This process relies on asymmetric (public-key) cryptography.

The sender generates a hash of the original message, then encrypts that hash using their own private key — this encrypted hash becomes the digital signature. The recipient receives the message along with the signature. To verify, the recipient decrypts the signature using the sender's public key to retrieve the hash, then independently hashes the received message and compares both hash values. If they match, the message is authentic and unaltered.

Digital signatures provide three critical security properties: authentication (confirms who sent the message), integrity (proves the message was not modified in transit), and non-repudiation (the sender cannot deny having sent the message). These properties are essential in secure communications, legal documents, software distribution, and financial transactions.

When you download software from a vendor's website, the installer is often digitally signed. Your operating system verifies the signature using the vendor's public key (embedded in a certificate) before allowing installation. If someone tampered with the file during download, the signature verification would fail and the OS would warn you — protecting your system from malicious modifications.

Always remember: Sign with private key → Verify with public key. The private key must remain secret with the signer, while the public key is shared with anyone who needs to verify the signature. This is the foundational principle of digital signature operations in asymmetric cryptography.