News for hackers. Stuff that matters.
Re:Introducing the Tink cryptographic software library by tptacek on Thursday August 30, 2018 @06:03PM (#17881213)
Different notions of authenticity! Their hybrid encryption still uses an AEAD for the bulk encryption.
Re:Introducing the Tink cryptographic software library by CiPHPerCoder on Thursday August 30, 2018 @06:14PM (#17881278)
Also, this limitation is easily worked around.

1. Use a digital signature.

2. Encrypt your signed message using Hybrid Encryption.

After your recipient decrypts your message (which, as Thomas notes, has AEAD), they can then verify your signature.

Re:Introducing the Tink cryptographic software library by zokier on Friday August 31, 2018 @02:46AM (#17883450)
I would think you'd generally want to do it the other way around and sign the ciphertext instead.
Re:Introducing the Tink cryptographic software library by CiPHPerCoder on Friday August 31, 2018 @09:23AM (#17885330)
"Just sign this opaque blob"?

Digital signatures aren't in the scope of the cryptographic doom principle. Generally, if you're signing a document, you want it to be really clear that you signed what it says.

Re:Introducing the Tink cryptographic software library by zokier on Friday August 31, 2018 @11:50AM (#17886539)
Crypto is confusing.
Re:Introducing the Tink cryptographic software library by CiPHPerCoder on Friday August 31, 2018 @12:27PM (#17886846)
It is, indeed.
Re:Introducing the Tink cryptographic software library by zokier on Friday August 31, 2018 @02:42AM (#17883436)
Then I'm even more confused. What are the different authenticities here, what guarantees do I get and not get?
Re:Introducing the Tink cryptographic software library by tialaramex on Friday August 31, 2018 @04:36AM (#17883915)
Tink's provided Hybrid primitive allows Alice to send messages to Bob if Alice knows Bob's public key.

No third party can understand Alice's messages even if they intercept them, and if a third party tampers with the message Bob doesn't get that message at all, just an error. So in this sense the messages are promised to be authentic.

However, Bob is not provided with assurance that the messages really came from Alice - there's no authentication, and so Bob should treat all the messages as anonymous. If Alice wants to authenticate as Alice to Bob, the two will need to agree some mechanism they can layer on top of Tink's hybrid primitive.

This is not dissimilar to how HTTPS is used from web browsers. When you visit Hacker News your browser is able to completely ensure that it's really talking to Hacker News using cryptography, but when it comes to reassuring Hacker News that you're really "zokier" you end up using a simple username + password login form.

Re:Introducing the Tink cryptographic software library by zokier on Friday August 31, 2018 @11:50AM (#17886526)
Sounds like what we are getting could be better described as integrity rather than authenticity. Makes kinda sense