0

Let´s say that Alice wants to send an encrypted message that only Bob can read, plus confirm that Alice is the person that wrote that message.

What is the procedure that will take place?

When I see digital signature workflow I always see that the message it´s transferred "clear" to the receiver (so Bob can hash the document in his side and compare it with the hash received by Alice), but the encrypted part (using Alice´s private key) is always the hash.

What happens when we want to encrypt also the message to a specific person? There will be a "second encryption" process, in which the message will be encrypted by Bob´s public key?

Just an example to confirm:

  • Alice produce digital signature: creates a hash of the document + encrypt it using her private key.

  • Alice encrypts the message itself: Takes the document and encrypt it using Bob´s public key (so only he can decrypt it, using his private key). (I guess that if the document is big can take a long time to finish the process, right?)

  • Is time a big concern here, or can we omit that part? – schroeder Mar 25 at 15:55
  • 1
    Small note: that's not exactly how digital signatures work. It's a common understanding, but it is not accurate. – schroeder Mar 25 at 15:55
  • Hello Schroeder. Can you share a link or post where is explained how digital signatures exactly work? – D. Rock Mar 25 at 15:57
  • 1
    This tries to explain the difference: security.stackexchange.com/questions/68822/… – schroeder Mar 25 at 16:02
  • 1
    The differences are that the "private key" is a special key used for signing (not encryption), it is not always necessary to hash the message, and if hashed, the hash is not encrypted with the signing key but rather the hash is used as an exponent. You do not simply hash the message and then encrypt the hash. – schroeder Mar 25 at 16:31
1

There's nothing that prevents you from either signing an encrypted message or encrypting a signed message. The latter is the way encrypted email works, see S/MIME with its CMS message format, or OpenPGP. The former is less common, but sometimes seen, for example in the specification of SCEP secure message objects.

A detailed discussion about the merits of these approaches and more can be found here.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.