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.