> I'm positing an audience of people who know little about elliptic curves; > they have no idea about what a cofactor or a Sophie-Germain prime is. All > they're interested in is trying to implement this protocol in a secure > manner, and want to dig into the mathematical details as little as possible.
Why not keeping the main document general and giving details for registered groups in an appendix? > The reason I put the group numbers in the titles is to make it easier for an > implementer to decide, for a specific group, which section is appropriate. > Perhaps another approach for achieving that goal would be better. The mapping between the registered groups and the individual subsections should be given in the appendix. >> hQ != point-at-infinity > > This is a cheap check (if h=2, I believe that's just a check that a > coordinate != 0, and as you say below, it's even cheaper if h=1). However, > is there a specific attack that is possible if you don't do the check? If > you're worried about someone modifying the DH public value with this value, > IKE already has protections against that in place. If you're worried about > someone learning the value of (e mod h) (where e is the private ECDH > multiplier), this check doesn't prevent that. You are right, this is exactly what Daniel has pointed out. Unfortunately, in case of a non-trivial cofactor, the check n*P != 0 necessary to prevent an attacker from learning (e mod h) is not cheap at all. In that case, the suggestion of Hugo applies as well, i.e. it is better to recommend not to reuse DH keys for EC groups with non-trivial cofactor. -- Johannes _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
