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.
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.