Also - would it have prevented, say, heartbleed?
I believe Signal does this based on the papers I’ve read; I’m sure many private or lesser-known protocols do as well.
>would it have prevented, say, heart bleed?
Probably, because in a strictly versioned scheme with no options, the buggy DTLS keepalive mechanism would not even have been in the same library. OpenSSL’s position of “we’ve got nine of everything including the kitchen sink” was the true cause of Heartbleed. Simpler code is easier to get right, debug, and perhaps formally verify as correct.
2) How to encode/signal those primitives to the other endpoint or decrypting program.
3) How to manage keys
4) How to signal which keys should be used to the other endpoint/decryptor
5) how to serialize messages for the network or filesystem, and how to parse them without making catostrophic mistakes.
Yes, I know most of those are “not in Tink’s scope”. They are also unaddressed by libsodium. But it’s what the “average” application developer needs to use crypto securely.
How about standardizing (RFC I guess) a single primitive of each type, and a strongly versioned set of serialization formats (including key storage).
That’s something a developer can’t misuse. Standardizing serialization formats and parsers are critical for developers to use this stuff correctly.
We can’t get rid of PKCS, X.509, and PGP and all their “algorithm agility” nonsense and insecurity until _somebody_ with industry clout replaces them with something secure and much simpler.
Google could do this... but instead we get Tink, a “choose your own adventure” just like the monthly alphabet soup produced by the IETF.
If GOOG/MSFT/Mozilla/etc can build and standardize AV1 together they could do the same for crypto. It’s way easier.