Rick Mark
Rick Mark
As someone who has spent some time researching this, this should be a priority. Installing Rosetta 2 effectively opens up substantive surface area on M1 macs and therefore they do...
“Polyfill” patch is in progress to ensure that we can call get affine for either coordinate space Get Outlook for iOS ________________________________ From: Kazuki Yamaguchi ***@***.***> Sent: Wednesday, April 14,...
Doh - maybe its best to have it be "odd" as the boolean. Since 0 == false == even and 1 == true == odd?
> I got the feeling that the Ruby interface also should take the integer 0 or 1, but I'm no expert. I'd like to avoid `Integer` here - because using...
> I can't merge this now because it depends on the ECDSA_sign_ex() deprecated in OpenSSL 3.0, which will likely be released this year. Is there a reason not to ship...
Crud: just found out that `EC_POINT_get_affine_coordinates` doesn't exist for all of the supported setups (2.3)
Because this API should support deterministic K values, placing work on this as dependent on resolving #426 first
The simple implementation might be to parse the ASN1 and return the two BN values as a helper method as this is a stable OpenSSL API surface. Will implement as...
Upon thought perhaps this should be a few different calls: `OpenSSL::PKey::EC::Group#method => Symbol` where symbol is in `[ :GFp_simple, :GFp_mont, :GFp_nist, :GF2m_simple ]` `OpenSSL::PKey::EC::Group#field_type => Symbol` where symbol in `[...
> Should it simply return the text representation of the NID (in other words, "prime-field" or "characteristic-two-field" - as returned by `OBJ_nid2ln()`)? I did it this way to match `Group#initialize`...