News for hackers. Stuff that matters.
Re:Introducing the Tink cryptographic software library by emmelaich on Thursday August 30, 2018 @11:20PM (#17882663)
If you don't bend like a willow, you'll break like an oak.
Re:Introducing the Tink cryptographic software library by tatersolid on Friday August 31, 2018 @06:51AM (#17884467)
No, you simply version the format if required, picking a new (disjoint) primitive set. Algorithm agility has caused many of the security defects in TLS, PGP, and SSH. It has remedied exactly zero flaws that a simpler versioned scheme would not also have addressed.
Re:Introducing the Tink cryptographic software library by emmelaich on Friday August 31, 2018 @09:48PM (#17889685)
Disjoint versions would be good. Has it ever been tried?

Also - would it have prevented, say, heartbleed?

Re:Introducing the Tink cryptographic software library by tatersolid on Sunday September 02, 2018 @11:14AM (#17897258)
> Disjoint versions would be good. Has it ever been tried?

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.