Re: [Cryptography-dev] accessing elliptic curve domain parameters (a/b/p/etc)

2016-01-27 Thread Paul Kehrer
Hi Matt, There are multiple issue/pull requests for this but unfortunately GitHub is down at the moment so I can't look them up... Once GitHub is back up and running take a look at https://github.com/pyca/cryptography/pull/2476 (that PR might have been split into other PRs that we've been discu

[Cryptography-dev] accessing elliptic curve domain parameters (a/b/p/etc)

2016-01-27 Thread Matt Bullock
For a project I am working on, I have a need to encode/decode elliptic curve points using point compression[1]. As this is not yet supported natively by the cryptography library, I have started implementing it myself but have hit a snag. Unlike the uncompressed point encoding, in order to decode

Re: [Cryptography-dev] accessing elliptic curve domain parameters (a/b/p/etc)

2016-01-27 Thread Matt Bullock
Nice, thanks, I'll take a look at that once GitHub is back up. --Matt On Wed, Jan 27, 2016 at 8:39 PM Paul Kehrer wrote: > Hi Matt, > > There are multiple issue/pull requests for this but unfortunately GitHub > is down at the moment so I can't look them up... Once GitHub is back up and > run

Re: [Cryptography-dev] accessing elliptic curve domain parameters (a/b/p/etc)

2016-01-27 Thread Matt Bullock
Yup, that looks like that would cover exposing the values I need. I was originally thinking pulling them from the backend, but I guess this way it's independent of the backend implementation (and it's not like the values will change). I'll keep an eye on those pull requests and plan that part of