Keys Not Included: recovering the signing keys for US driver's license barcodes
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Keys Not Included: recovering the signing keys for US driver's license barcodes
Unofficial Hacker News client; not affiliated with Y Combinator.
bzmrgonz · · focus · HN ↗
morsch · · focus · HN ↗
It's not like non-technical people understand asymmetric cryptography. Or even technical people, for that matter.
Maybe we should refer to the public key as an address, and the private key is just a password again. You can send stuff, securely, to an address. And you can verify the sender when you have their address (ie check the signature).
fc417fc802 · · focus · HN ↗
The public counterpart is tricky to name but I think attaching "public" to it makes the intended usage plenty clear. There isn't really a physical counterpart unless you consider maybe those machines that check for counterfeit cash but even that's not a great fit because the pubkey is simultaneously analogous to a lock box.
TeMPOraL · · focus · HN ↗
yencabulator · · focus · HN ↗
TeMPOraL · · focus · HN ↗
yencabulator · · focus · HN ↗
fc417fc802 · · focus · HN ↗
For example a VPN connection lends itself to being described as a pipe. That already equates the encapsulating protocol with a physical barrier regardless of the presence of cryptography.
I think you're just being overly literal, something which will kill almost any decent analogy regardless of topic.
TeMPOraL · · focus · HN ↗
And it's because it does not fit. Locks and keys are distinct kinds of objects, and are external to the thing being protected, with lock itself being attached to the thing being protected. Only the key can be distributed separately and copied; you come into possession of the security mechanism and the protected object together, they're literally unseparable (that's the point - if you can separate the lock from the thing, you don't need the key anymore).
Encryption in contrast is (reversibly) destroying the thing being protected, the "locking mechanism" is public and same for everyone and therefore you already have a copy, and you can't "bypass" it because the very thing being protected has been destroyed (scrambled) and you cannot undo that without having the "key".
There's no 1:1 mapping of any concept from physical locks and keys to encryption. It's a fundamentally dumb analogy that people run away with, because at first look it seems to have some semantic similarities.
yencabulator · · focus · HN ↗