Computer Science · Grade 12

Active learning ideas

Digital Signatures and Certificates

Active learning helps students grasp abstract cryptographic concepts by making them concrete and hands-on. Working with digital signatures and certificates through analogies, tools, and role-plays turns what often feels like a ‘black box’ into something they can see, test, and question directly.

• Ontario Curriculum Expectations
• CS.N.8
• CS.S.3

• 35–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Document Mystery
• 35 min · Small Groups

Analogy Demo: Sealed Documents

Provide groups with paper messages, wax seals, and replica keys. Students 'sign' by hashing (summarizing) content on paper, sealing with wax, then 'verify' by breaking seals and matching summaries. Discuss parallels to digital hashes and keys. Extend to certificate 'issuance' using class 'CA' stamps.

Explain how a digital signature verifies the authenticity and integrity of a message.

Facilitation Tip

During the Sealed Documents activity, have students physically write and seal messages to model how hashing and signing separate integrity checks from content privacy.

What to look for

Provide students with a scenario: 'Alice sends Bob a document. She digitally signs it using her private key. Bob receives the document and the signature. What are the two main things Bob can verify using Alice's public key and the signature, and why is this process important for trust?'

• Analyze
• Evaluate
• Self-Management
• Decision-Making

Activity 02

• Document Mystery
• 40 min · Pairs

Browser Lab: Certificate Inspection

Direct students to visit secure sites, right-click locks to view certificates. In pairs, note issuer, validity dates, and public key details using browser dev tools. Compare chain of trust to root CAs. Record findings in a shared class chart.

Analyze the role of Certificate Authorities (CAs) in establishing trust online.

Facilitation Tip

In the Certificate Inspection lab, pause students after each step to ask them to explain what the browser shows and why that piece matters.

What to look for

Ask students to individually write down the steps involved in creating a digital signature, starting from the original message. Then, have them write the steps for verifying that signature. Collect these for a quick review of understanding the process.

• Analyze
• Evaluate
• Self-Management
• Decision-Making

Activity 03

• Document Mystery
• 50 min · Small Groups

Role-Play: Compromised CA Scenario

Assign roles: users, signer, rogue CA, verifier. Simulate certificate issuance, then 'compromise' with fake certs. Groups act out verification failures and debate revocation processes. Debrief on real-world implications like Heartbleed.

Critique the security implications of a compromised digital certificate.

Facilitation Tip

Before the Compromised CA scenario, assign roles clearly and set a 5-minute timer for each phase so the simulation stays focused and dramatic.

What to look for

Pose this question to small groups: 'Imagine a Certificate Authority's root certificate is compromised. What are the potential consequences for online security, and what measures could be taken to mitigate these risks?' Facilitate a brief class discussion based on group responses.

• Analyze
• Evaluate
• Self-Management
• Decision-Making

Activity 04

• Document Mystery
• 45 min · Pairs

Tool Practice: Generate Signatures

Use online tools or OpenSSL in lab: create key pairs, sign sample files, alter files, and verify. Students document success/failure cases. Pairs troubleshoot common errors and present one secure workflow.

Explain how a digital signature verifies the authenticity and integrity of a message.

Facilitation Tip

While students generate signatures in the Tool Practice activity, circulate to check that they understand why the private key stays local and the public key is shared.

What to look for

Provide students with a scenario: 'Alice sends Bob a document. She digitally signs it using her private key. Bob receives the document and the signature. What are the two main things Bob can verify using Alice's public key and the signature, and why is this process important for trust?'

• Analyze
• Evaluate
• Self-Management
• Decision-Making

A few notes on teaching this unit

Start with analogies to build intuition, then immediately move to tool-based exploration so students see real certificates in action. Avoid rushing through the math behind hashing or RSA; instead, focus on the workflow and trust implications. Research shows that guided discovery with immediate feedback leads to better retention than lectures alone.

Students will confidently describe how digital signatures and certificates work, including the roles of private and public keys, hashing, and verification. They will also identify real-world trust issues and explain why secure key management and revocation matter.

---

Watch Out for These Misconceptions

• During the Sealed Documents activity, watch for students who think the envelope itself protects the message contents from being read.

  Use the sealed envelope to emphasize that the seal only proves authenticity and integrity, not privacy. After sealing, have students open the envelope to show the message is still visible, then compare this to a digital signature’s role in verifying content without hiding it.

• During the Compromised CA scenario, watch for students who assume that revoking a certificate immediately fixes all trust issues.

  In the role-play, give teams 2 minutes to list all systems and users still trusting the compromised CA before revocation kicks in. This highlights the gap between revocation and real-world propagation delays.

• During the Certificate Inspection lab, watch for students who believe all certificates are equally trustworthy.

  In the browser lab, ask students to compare the certificate chains of two different websites and identify which one has more intermediate CAs. This leads to a discussion about the chain of trust and why length matters.

---

Methods used in this brief

• Document Mystery