[cabfpub] Updated Agenda for F2F Meeting 33

[Håvard Molland]

On 15. sep. 2014 11:15, Erwann Abalea wrote:
> It would be hard to discuss about SM2/SM3 at CABForum level when 
> there's so few analysis and publications of these algorithms.
>
> SM2 seems to be a set of asymetric cryptographic primitives working on 
> ECC, providing signature, key exchange, and encipherment functions; 
> respectively similar to ECDSA, ECDH, and maybe ECIES?. There's also a 
> new 256bits prime curve.
> SM3 is a hash function, MD design, similar to SHA256 with a few 
> modifications.
>
> What could be discussed at CABF level:
>  - adoption of the new curve, can it be used with ECDSA to sign 
> certificates/CRLs/OCSP? (then we should also talk about Brainpool 
> family, ANSSI FRP256v1, Curve25519, and others)
>  - adoption of SM3 in signatures, with ECDSA? That's a more difficult 
> question, we don't already agree on what to do with SHA1, there's 
> little to no analysis of SM3. The team behind SM3 include some people 
> involved in the end of MD4/MD5/RIPEMD in 2004/2005, I guess they know 
> what they're doing, but the algo still needs to be challenged. If we 
> talk about SM3, we might as well talk about GOST R34.11-94, GOST 
> R34.11-2012, and maybe a lot of others...
>  - adoption of SM2 in signature mode (SM2 part 2)? On which curve, 
> with which hash algorithm? An even more difficult question; there's 
> more info about EC-Schnorr or EdDSA than there's about SM2. Again, 
> other algorithms such as GOST R34.10-2001 or GOST R34.10-2012 might as 
> well be discussed, and maybe ECKCDSA (Korean) or ECGDSA (German)

Any new algorithm should offer improvements on the existing algorithms, 
such as improved security, new security features or speed. I'm not sure 
we should add new algorithms simply for the sake of being alternatives.

Håvard


>
> Before their eventual adoptions, all these algorithms need to 
> described in english, challenged, correctly parameterized (unlike the 
> GOST-* things), and identified (OIDs). Adoption is far away in this 
> process.
>
> Looking for OIDs led me to 
> http://wenku.baidu.com/view/12cb9bc608a1284ac8504318.html
> Do really someone in China use 1.2.156.197.1.310 for RSA, or 
> 1.2.156.197.1.411 for SHA256?
>
> -- 
> Erwann ABALEA
>
> Le 12/09/2014 11:41, Richard at WoSign a écrit :
>> Yes, this is my topic that SM2 is a China standard algorithm and plan to adapt
>> in China. It is  kind of asymmetric cryptographic algorithm which is based on
>> elliptic curves cryptography (ECC).
>>
>> I sent email to Ben that maybe we need to cancel this topic since I can't find
>> a SM2 specialist to make the speech in the meeting in English. If someone
>> still have interesting, I can talk some, a little.
>>
>> And I wish Firefox can support this algorithm that we can do the coding work
>> for NSS, we can talk about this privately.
>>
>>
>> Best Regards,
>>
>> Richard
>>
>> -----Original Message-----
>> From:public-bounces at cabforum.org  [mailto:public-bounces at cabforum.org] On
>> Behalf Of Gervase Markham
>> Sent: Friday, September 12, 2014 5:33 PM
>> To: Ben Wilson; CABFPub
>> Subject: Re: [cabfpub] Updated Agenda for F2F Meeting 33
>>
>> On 11/09/14 20:41, Ben Wilson wrote:
>>> Here is the updated agenda.  Please let me know if you have any
>>> corrections that need to be made.
>> Can someone explain the "Discussion of SM2 Algorithm" item? What are we
>> discussing about it? Its technical features and security properties?
>> When and if browsers and other clients are going to support it? Or something
>> else?
>>
>> Gerv
>>
>> _______________________________________________
>> Public mailing list
>> Public at cabforum.org
>> https://cabforum.org/mailman/listinfo/public
>>
>>
>> _______________________________________________
>> Public mailing list
>> Public at cabforum.org
>> https://cabforum.org/mailman/listinfo/public
>
>
>
> _______________________________________________
> Public mailing list
> Public at cabforum.org
> https://cabforum.org/mailman/listinfo/public


-- 
---
Opera Software

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/public/attachments/20140915/c63486b1/attachment-0001.html