Closed gmulhearn closed 4 months ago
Related to signed did_rotate attachments: https://github.com/hyperledger/aries-vcx/issues/1228
Part 2 is fixed in #1232 . I'm still questioning the importance of part 1, as other agents (acapy, credo) don't seem to do this AFAIK
I don't know that (1) is required as the signatures are not serving any real purpose as I understand it, also (as mentioned here), for instance.
yea agreed. ok i'm going to descope it from this issue
Closed by #1232
I'm finding that currently, the
DIDExchange
requester and responder impls are not checking some cryptographic parts of the DIDExchange flow. Particularly:DidExchangeResponder::<ResponseSent>::receive_request
), then it should check that the wire-level sender of the request is from a key that matches a key of the DIDDoc inside the request. The spec says to do this:~~I don't believe that ACAPy does this~
EDIT: descoping this, as the community does not seem to find this case necessary: https://github.com/hyperledger/aries-rfcs/issues/717#issuecomment-1069768955
DidExchangeRequester::receive_response
), then it should check that DIDDoc or the DIDRotate attachment is signed JWS, and is signed with the original inviter key. The spec is clear on this:ACApy seems to do this