Closed chris-wood closed 2 years ago
IIRC the security analysis does cover this case, though I would need to go back and double check. @ttaubert, do you recall off hand? If it does, we can safely close this without action.
The security analysis does explicitly not cover this case:
Ah, well, interesting!
From @cjpatton
Quote:
This may be problematic from the perspective of the security analysis, I suggest we go back to the Shoup paper and check. The problem is that RO queries for sessions with no identities might collide with queries for sessions with identities. For example, a password
pw
in one session may be equal tolen(pw2) || pw2 || len(A) || A || len(B) || B)
wherepw2
is the password in another session in whichA
andB
are the identities.Since this logic isn't excercised in the rest of the spec, I would just remove it and not treat this as a special case.