In conversation yesterday, I got into being an "andragogue" (which comes for "andragogy" as distinct from "pedagogy"): one who teaches adults. One would think there'd be a partially overlapping toolkit with more kid-oriented techniques. Our topic: cryptography, cyphers.
The topic arose in connection with a certain TV show, set quite a while back. We started talking about Neal Stephenson, and the books by him we'd both read, including Snow Crash. In my case Cryptonomicon was influential in getting me to write more research-based code. I implemented Blowfish for example, and later RSA (public key).
So that's when I launched into the sea change significance of public key cryptographic techniques arise around the same time as the internet. They way I tell it, the NSA was leery of letting MIT publish RSA, but the algorithm was already out of the bag and individuals were already demanding secure peer-to-peer between any Bob and any Alice. The NSA knew the history: GCHQ had it first, but kept it under wraps. My account is not just my dreamed up account. I read some public sources, books you will find in the library.
Bob, Alice and Eve that is. Eve is the eavesdropper in this paradigm, whom we might imagine hiding in the eaves, the rafters, and listening in one what Bob and Alice presume (mistakenly) is a private conversation. This triangle, twixt Alice, Bob and Eve, is generic in the field of cryptography.
What public key cryptography (such as RSA) made possible was skipping the step of exchanging a decoder key before initiating secure communications. Bob and Alice each published their public numbers while holding a secret private number, derived mathematically, but in a way hard to reverse minus the two seed primes used to create the public number.
You're grabbing two gigantic prime numbers out of the blue and using them to make up a public-private pair. Then you throw those two primes away. Without them, Eve will not have a way to derive Bob's or Alice's decoder number. Only Bob can decode messages encrypted with Bob's unique number.
Ah, but is Bob's number really unique? Obviously there's more to get into here. Cryptography is all about deceiving and deception. My former employer, O'Reilly Media, put out a pretty good book on the topic, although I'm forgetting the title. The best way to protect against vulnerabilities is to see how the exploits work. You might have all the high end cryptography in the world, but how does that help if Bob and Alice also have "secret" meetings in the parking lot, not knowing Eve has a way of listening in?
I'm going into more detail here than I did with my friend, in her 80s, quite well read. My history on edu-sig, a Python special interest group for educators using Python, was all about using an object oriented language to model "math objects" such as vectors, polyhedrons, Bob and Alice.
I wasn't alone in having this focus. I found Phillips Academy was offering a "learn RSA through Python" course as one of their math department offerings. The better schools were already using executable mathematics languages, like Wolfram Language and/or Python and/or Haskell or one of those (Scheme, J, APL... maybe BQN today).

