Digital signatures and certificates in Computer Networks - Step-by-Step Execution

Concept Flow - Digital signatures and certificates

Message Created

↓

Hash Function Applied

↓

Hash Value Created

↓

Hash Encrypted with Private Key

↓

Digital Signature Created

↓

Message + Signature Sent

↓

Receiver Gets Message + Signature

↓

Hash Function Applied to Message

↓

Decrypt Signature with Sender's Public Key

↓

Compare Hashes

This flow shows how a digital signature is created by hashing a message and encrypting the hash with a private key, then how the receiver verifies it by decrypting and comparing hashes.

Execution Sample

Computer Networks

message = "Hello"
hash_value = hash_function(message)
signature = encrypt(hash_value, private_key)
send(message, signature)
received_hash = hash_function(received_message)
verified_hash = decrypt(received_signature, public_key)
valid = (received_hash == verified_hash)

This code simulates creating a digital signature for a message and verifying it on the receiver's side.

Analysis Table

Step	Action	Value/Result	Explanation
1	Create message	"Hello"	Original message to send
2	Apply hash function	hash_value = 0x1a2b3c	Hash of message (fixed example)
3	Encrypt hash with private key	signature = encrypted_hash	Digital signature created
4	Send message and signature	message + signature	Data sent to receiver
5	Receiver applies hash to message	received_hash = 0x1a2b3c	Hash computed from received message
6	Receiver decrypts signature	verified_hash = 0x1a2b3c	Hash recovered from signature
7	Compare hashes	received_hash == verified_hash	True, signature is valid
8	Result	valid = True	Message authenticity confirmed

💡 Hashes match, so the digital signature is valid and message is authentic.

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 6	Final
message	None	"Hello"	"Hello"	"Hello"	"Hello"	"Hello"
hash_value	None	0x1a2b3c	0x1a2b3c	0x1a2b3c	0x1a2b3c	0x1a2b3c
signature	None	None	encrypted_hash	encrypted_hash	encrypted_hash	encrypted_hash
received_hash	None	None	None	0x1a2b3c	0x1a2b3c	0x1a2b3c
verified_hash	None	None	None	None	0x1a2b3c	0x1a2b3c
valid	None	None	None	None	None	True

Key Insights - 3 Insights

Why do we hash the message before encrypting it with the private key?

Hashing creates a fixed-size summary of the message, making encryption efficient and ensuring the signature uniquely represents the message content (see Step 2 and 3 in execution_table).

What happens if the hashes do not match during verification?

If hashes differ (Step 7), it means the message or signature was altered or forged, so the signature is invalid and the message is not trusted.

Why is the sender's private key used to create the signature and the public key used to verify it?

The private key is secret and used to sign, while the public key is shared and used to verify, ensuring only the sender could have created the signature (see Steps 3 and 6).

Visual Quiz - 3 Questions

Look at the execution_table at Step 3. What does the 'signature' represent?

A The original message encrypted

B The hash of the message encrypted with the private key

C The hash of the message encrypted with the public key

D The decrypted hash value

💡 Hint

Check Step 3 where the hash is encrypted with the private key to create the signature.

At which step does the receiver confirm the message authenticity?

A Step 5

B Step 6

C Step 7

D Step 4

💡 Hint

Look at Step 7 where the hashes are compared to validate the signature.

If the message changes during transmission, what will happen to 'valid' in the variable_tracker?

A It will become False

B It will remain True

C It will be None

D It will cause an error

💡 Hint

Refer to the comparison of hashes in Step 7 and the final 'valid' value.

Concept Snapshot

Digital signatures use a hash of the message encrypted with a private key.
The signature is sent with the message.
Receiver decrypts signature with sender's public key and hashes the message.
If hashes match, signature is valid and message is authentic.
Certificates link public keys to identities to build trust.

Full Transcript

Digital signatures work by creating a hash of the original message, which is a short fixed-size summary. This hash is then encrypted using the sender's private key to create the digital signature. The message and signature are sent together to the receiver. The receiver applies the same hash function to the received message and decrypts the signature using the sender's public key. If the two hashes match, the signature is valid, confirming the message's authenticity and integrity. Certificates are used to associate public keys with real-world identities, helping receivers trust the sender's public key.

Practice

1. What is the main purpose of a digital signature in online communication?

easy

A. To encrypt the entire message content

B. To prove who sent a message and that it was not changed

C. To speed up the internet connection

D. To store passwords securely

Solution

1. Step 1: Understand the role of digital signatures

   Digital signatures are used to verify the sender's identity and ensure the message has not been altered.

2. Step 2: Compare options with this role

   Only To prove who sent a message and that it was not changed correctly describes this purpose; others describe unrelated functions.

3. Final Answer:

   To prove who sent a message and that it was not changed -> Option B

4. Quick Check:

   Digital signature = sender identity + message integrity [OK]

Hint: Digital signatures confirm sender and message unchanged [OK]

Common Mistakes:

• Confusing digital signatures with encryption
• Thinking digital signatures speed up connections
• Believing digital signatures store passwords

2. Which of the following is the correct way to describe a digital certificate?

easy

A. A tool to speed up file downloads

B. A method to hide messages from hackers

C. A document that proves the identity of websites or people online

D. A software to delete viruses

Solution

1. Step 1: Define digital certificate

   A digital certificate is used to prove the identity of websites or people online, ensuring trust.

2. Step 2: Match options to this definition

   A document that proves the identity of websites or people online matches this definition exactly; others describe unrelated tools or functions.

3. Final Answer:

   A document that proves the identity of websites or people online -> Option C

4. Quick Check:

   Digital certificate = identity proof online [OK]

Hint: Certificates prove identity of websites or people [OK]

Common Mistakes:

• Thinking certificates speed up downloads
• Confusing certificates with encryption methods
• Believing certificates remove viruses

3. Consider this scenario: A user receives a message with a digital signature. What does verifying the signature confirm?

medium

A. The message was sent by the claimed sender and was not altered

B. The message is encrypted and unreadable

C. The message is from a trusted website

D. The message contains no viruses

Solution

1. Step 1: Understand digital signature verification

   Verifying a digital signature confirms the sender's identity and that the message was not changed.

2. Step 2: Analyze options

   The message was sent by the claimed sender and was not altered correctly states this; The message is from a trusted website relates to certificates, not signatures; A and B are unrelated.

3. Final Answer:

   The message was sent by the claimed sender and was not altered -> Option A

4. Quick Check:

   Verify signature = confirm sender + message integrity [OK]

Hint: Signature verification confirms sender and message unchanged [OK]

Common Mistakes:

• Confusing signature verification with encryption
• Assuming verification means virus check
• Mixing up certificates and signatures

4. A website's digital certificate is expired, but the user ignores the warning and proceeds. What is the main risk?

medium

A. The website will block the user

B. The website will load faster

C. The user's computer will automatically update the certificate

D. The website's identity cannot be trusted, risking data theft

Solution

1. Step 1: Understand expired certificate implications

   An expired certificate means the website's identity is not verified, so it may be unsafe.

2. Step 2: Identify the risk of ignoring warnings

   Ignoring the warning risks trusting a fake or unsafe site, which can lead to data theft.

3. Final Answer:

   The website's identity cannot be trusted, risking data theft -> Option D

4. Quick Check:

   Expired certificate = identity risk and data theft [OK]

Hint: Expired certificates mean identity can't be trusted [OK]

Common Mistakes:

• Thinking expired certificates speed up loading
• Assuming automatic updates fix expired certificates
• Believing the website will block users ignoring warnings

5. A company wants to ensure both the identity of its website and the integrity of messages sent to clients. Which combination should it use?

hard

A. Digital certificate for website identity and digital signature for message integrity

B. Digital signature for website identity and digital certificate for message integrity

C. Only digital certificates for both identity and integrity

D. Only digital signatures for both identity and integrity

Solution

1. Step 1: Identify roles of certificates and signatures

   Digital certificates prove website or user identity; digital signatures prove message integrity and sender.

2. Step 2: Match roles to company needs

   The company needs certificates to prove website identity and signatures to ensure message integrity.

3. Final Answer:

   Digital certificate for website identity and digital signature for message integrity -> Option A

4. Quick Check:

   Certificate = identity, Signature = integrity [OK]

Hint: Use certificate for identity, signature for message integrity [OK]

Common Mistakes:

• Swapping roles of certificates and signatures
• Thinking one alone covers both identity and integrity
• Confusing message encryption with identity proof