Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a glossary page on digital signatures #33507

Merged
merged 2 commits into from
May 22, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
29 changes: 29 additions & 0 deletions files/en-us/glossary/digital_signature/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
title: Digital signature
slug: Glossary/Digital_signature
page-type: glossary-definition
---

{{GlossarySidebar}}

A **digital signature** is an object that can be used to {{glossary("authentication", "authenticate")}} the author of a document or message.

Digital signatures are usually based on {{glossary("public-key cryptography")}}, in which a key is created as a pair of keys, with the property that if some input is encrypted with one key, it can only be decrypted with the other key, and vice versa.
wbamberg marked this conversation as resolved.
Show resolved Hide resolved

The creator of the key pair then makes one of the keys public and keeps the other one private. To sign a document, the key pair's owner creates a {{glossary("hash")}} of the document and encrypts it with the private key.
wbamberg marked this conversation as resolved.
Show resolved Hide resolved

They send the document and the signature to the verifier, who hashes the document, then retrieves the public key and decrypts the signature: if this matches the hash then the signature has been verified, and the verifier can be confident that the signature was created by an entity with access to the private key.
wbamberg marked this conversation as resolved.
Show resolved Hide resolved

The security of a digital signature system depends (among other things) on:

- The private key's owner keeping it safe: if other entities can access the private key, they can impersonate the owner.

- The public key used by the verifier being the genuine counterpart of the owner's private key: if an attacker could trick the verifier into trusting the wrong public key, they could impersonate the owner.

Verifiers often use {{glossary("digital certificate", "digital certificates")}} to check that public keys are genuine.

## See also

- {{glossary("Digital certificate")}}
- {{glossary("Hash")}}
- {{glossary("Public-key cryptography")}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These three are already in the document. This might be a good place to add links to the security docs you're writing instead, but it's ok to leave these here too.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fair. I never know whether to include relevant links that are already mentioned inline. But I will leave them here now, since they don't seem to be doing any harm.