How do we use proof of a verifiable credential when establishing a peer DID relationship? I was wondering, if a regular proof request/presentation exchange (eg. the one used in the Aries demo) can be used in this case, but it may open up avenues for data leak.
1. Let us assume the attacker DID A is interested in knowing only certain information, say the date of birth or the SSN Social Security Number, of DID B and nothing more. He sends an invitation to B for a peer connection. Once the invitation is accepted by B, A will request for a proof presentation from DID B (with the DOB or SSN as attributes) to continue the relationship. Let us assume that the information requested is such that predicates cannot be used.
2. In return, the honest DID B can ask for the same from DID A. DID A can provide a fabricated claim about itself since it is not interested whether the claim’s verification is successful or not. So proofs of both parties are exchanged.
3. By the time DID B knows that A's claim fails, A would have already obtained the required attributes it is looking for from B. B breaks down the peer connection, but A does not care since it has already got the required information.
It is a typical phishing case where DID A forces DID B to reveal some information about itself using a verifiable claim in the initial stages of setting up a peer relationship.
Is my understanding correct?
Is there a standard/method that specifies what claims can be used for establishing a peer relationship or something that prohibits arbitrary requests of attributes?