RFC 4210 states:
1631 Note: it is RECOMMENDED that the fields of PBMParameter remain
1632 constant throughout the messages of a single transaction (e.g.,
1633 ir/ip/certConf/pkiConf) in order to reduce the overhead associated
1634 with PasswordBasedMac computation).
It would bring a certain efficiency gain if the PBM basekey calculated during protection of a request (e.g. IR/KUR/CR) is stored in order to be used again for
- validating the server response, provided it uses the same PBM Parameters (might not be the case in practice)
- sending the certConf (or error) message in the same session
- future sessions (if the ctx/PBMP are re-used)
Similarly, if the server response uses different PBM Parameters, the PBM basekey calculated for the validation of the first response could be stored to validate the PKIconf message.
This would need some additonal logic, but wouldn't 't lower security as long as the basekey is handled analogous to the secret.
Log in to post a comment.
