Incompatible changes relative to csrp (motivated by security) * Padding in computation of M and H_AMK is not standardised in RFC 5054, RFC 2945 * It is bad security practice to hash concats of (more than one) var-sized fields * Security practices with var-size concats are padding, size-mention, separators * RFC 5054 and RFC 2945 do not permit size-mentioning or separators * So, to live up to common security practices, padding is needed * Note that RFC 2945 leaves this to the protocol designer (unwisely, IMHO) * Note that RFC 5054 and implementations like GnuTLS don't produce M or H_AMK
Incompatible changes relative to csrp (motivated by security)
* Padding in computation of M and H_AMK is not standardised in RFC 5054, RFC 2945
* It is bad security practice to hash concats of (more than one) var-sized fields
* Security practices with var-size concats are padding, size-mention, separators
* RFC 5054 and RFC 2945 do not permit size-mentioning or separators
* So, to live up to common security practices, padding is needed
* Note that RFC 2945 leaves this to the protocol designer (unwisely, IMHO)
* Note that RFC 5054 and implementations like GnuTLS don't produce M or H_AMK

arpa2/srp-pkcs11