On 15.05.2013 21:17, Johannes Bauer wrote: > Only sect/secp are included curiously although my openssl client > does internally also know, for example, about the wap-wsg and X9.62 > curves. But those are not included in the Client Hello request. > > And there's definitely no "unnamed generic type" included in the > request. Is there any way I can make openssl include that?
Interesting. I've done some poking around in the source code and RFC4492. It appears that in that NamedCurve enumeration the only named curves are indeed secp and it's twisted sister curves (apart from the "generic" type). So that explains why they're the only ones that appear in the enumeration. However, in the source code I couldn't find any reference to the arbitrary explicit type; searched in the nid_list in ssl/t1_lib.c and also for the constant 0xff01 (hex and decimal) and found no occurences. Does this mean that communication with TLS1.2 with curves other than the SEC-curves has actually never worked with OpenSSL (because it couldn't have worked as this would require the explicit curve type why doesn't appear to be implemented as of now)? Or is there some workaround through which I could get it to run? Thank you very much for the pointer in the right direction, Best regards, Johannes ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
