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
{{ message }}
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
We should be signing the connection response. Specifically, the connection object needs to be replaced by connection-sig.
The reason for this is that the keys shared in the initial invitation to exchange will likely NOT be the keys present in the DID shared in the connection response:
The keys in the initial invitation to exchange will likely be ephemeral since they are sent in plaintext (by design) and because DIDComm uses keys as identifiers. Identifiers should not be revealed to outside parties.
The party has to prove that they own the DID that they are sharing and this is a mechanism to do so in a single message (as opposed to a later challenge-response protocol).
The text was updated successfully, but these errors were encountered:
We should be signing the connection response. Specifically, the
connection
object needs to be replaced byconnection-sig
.The reason for this is that the keys shared in the initial invitation to exchange will likely NOT be the keys present in the DID shared in the connection response:
The text was updated successfully, but these errors were encountered: