Showing raw Markdown: the renderer could not load.
Every padlock in a browser, every stored password and every software update relies on a few cryptographic building blocks. You don't need the mathematics to use them well, but you do need to know what each one guarantees and what it doesn't. This module explains hashing, symmetric and asymmetric encryption, digital signatures and certificates, and lets you try each one with `openssl`. ## Learning objectives By the end of this module you will be able to: 1. Explain what a cryptographic hash guarantees and use one to check the integrity of a file. 2. Explain why passwords must be stored with a salt and a slow hash function, not with a plain hash or encryption. 3. Compare symmetric encryption (AES) and asymmetric encryption (RSA, elliptic curves), and explain how protocols such as TLS combine them. 4. Explain how a digital signature provides integrity and authenticity, and create and verify one. 5. Read an X.509 certificate and explain how a certificate chain lets a browser trust a website. ## Prerequisites - [04 — Security Fundamentals](../04-security-fundamentals/README.md). - For the lab: OpenSSL 3.0 or later (`openssl version`) on Linux, macOS or Windows with WSL2. Cost: free. ## Contents | Type | Duration | |---|---| | [Theory](lesson.md) | 50 min | | [Hands-on lab: hashing, encrypting and signing with OpenSSL](lab.md) | 45 min | | [Assessment (10 questions)](quiz.md) | 15 min | ## Further reading - [FIPS 180-4](https://csrc.nist.gov/pubs/fips/180-4/upd1/final) — Secure Hash Standard (SHS) - [FIPS 197](https://csrc.nist.gov/pubs/fips/197/final) — Advanced Encryption Standard (AES) - [RFC 5280](https://www.rfc-editor.org/rfc/rfc5280) — Internet X.509 Public Key Infrastructure Certificate and CRL Profile - [RFC 8446](https://www.rfc-editor.org/rfc/rfc8446) — The Transport Layer Security (TLS) Protocol Version 1.3