Re: [secdir] [Curdle] 答复: Secdir review of draft-ietf-curdle-cms-eddsa-signatures-06

[Russ Housley <[e-mail]>]

Dacheng:

Trimming the parts where we have reached agreement...

>> 2. In the 4th paragraph of security considerations, ' the same private key SHOULD NOT be used with more than one EdDSA set of parameters.' -> ' the same private key MUST NOT be used with more than one EdDSA set of parameters.' Since we already know that the same private key used for multiple algorithms will cause potential risks, we should use a stronger word here.
> 
> I do not think that there is a problem with using the same private key with PureEdDSA and HashEdDSA.  The prudent advice is to avoid mixing the same private key with different parameter, thus the SHOULD NOT.  I point out that RFC 8032 goes even further:
> 
>   ... Thus, one can use the same
>   key pair for Ed25519, Ed25519ctx, and Ed25519ph and correspondingly
>   with Ed448 and Ed448ph.
> 
> Dacheng: Ok, I see your point. Then, I think it will be good to make some clarification here since the first sentence of this paragraph strongly argues that ' Using the same private key for different algorithms has the potential of allowing an attacker to get extra information about the private key.' Maybe we can change the second sentence to something like ' For this reason, the same private key SHOULD NOT be used with more than one EdDSA set of parameters, although people believe that no security issue will be caused when using the same private key with PureEdDSA and HashEdDSA [RFC8032]. '

How about:

Using the same private key with different algorithms has the potential
to leak extra information about the private key to an attacker.  For
this reason, the same private key SHOULD NOT be used with more than one
set of EdDSA parameters, although people believe that there are no
security concerns when using the same private key with PureEdDSA and
HashEdDSA [EDDSA].

Russ