You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In appendix 4 of the documentation (page 68 in the PDF), it mentions two sets of keys:
Digital Signatures
Authenticated message Encryption
The document goes on to explain how to use the digital signatures (used to seal an XML message of type PayloadMessage using the private key into a blob of bytes that can be unsealed by using the corresponding public key), but it does not explain when and how to use the authenticated message encryption.
I looked through the source code of the Shapeshifter implementation but could not find references to the message encryption.
What is the intended purpose of the authenticated message encryption, and where should I use it?
The text was updated successfully, but these errors were encountered:
@stan-janssen I don't know of an implementation that has implemented this; Good question, we can discuss this with the rest of the contributors to see what they think about it.
@tomwetjens@KoviaX Do you know of an implementation that uses this?
What do we want to do with this? Do we think we still need this?
The wording is indeed confusing and not really clear,
In appendix 4 of the documentation (page 68 in the PDF), it mentions two sets of keys:
The document goes on to explain how to use the digital signatures (used to seal an XML message of type
PayloadMessage
using the private key into a blob of bytes that can be unsealed by using the corresponding public key), but it does not explain when and how to use the authenticated message encryption.I looked through the source code of the Shapeshifter implementation but could not find references to the message encryption.
What is the intended purpose of the authenticated message encryption, and where should I use it?
The text was updated successfully, but these errors were encountered: