Data Transmission · 4 question types
Past paper frequency (2018 to 2024)
This topic accounts for approximately 4% of your exam marks.
Symmetric vs asymmetric encryption questions are growing as cybersecurity becomes more prominent.
Asymmetric encryption uses two related keys: a public key that anyone is allowed to know, and a private key that only the owner knows. Data encrypted with one of the keys can only be decrypted with the other.
Suppose Alice wants to send a private message to Bob.
The clever maths behind asymmetric encryption (RSA, ECC, etc.) is built so that knowing the public key is enough to encrypt but not enough to decrypt. Decryption requires the private key, which is held only by the recipient. Even though anyone can see the public key, no one can use it to reverse the encryption.
Asymmetric encryption solves the key-sharing problem. Bob can publish his public key to the whole world. Anyone (Alice, Charlie, total strangers) can use it to send him encrypted messages, and only Bob, with his private key, can read them. There is no need to pre-arrange a shared key.
Asymmetric encryption is much slower than symmetric encryption because the mathematics is more demanding. For this reason, real systems usually:
This is exactly what HTTPS does: a brief asymmetric handshake, then fast symmetric encryption for the bulk of the page load.
Modern asymmetric keys are large to resist guessing. A 100-bit key would give about 10³⁰ different possible values; a 2048-bit RSA key is the modern minimum. The number of possible combinations is so huge that a brute-force search is impossible with today's computers.