Re: [RFC] OpenSSL BigNum support
| From: | Sara Golemon | Date: | Mon, 24 Oct 2016 05:09:21 +0000 |
| Subject: | Re: [RFC] OpenSSL BigNum support | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96571@lists.php.net to get a copy of this message | ||
On Sun, Oct 23, 2016 at 5:06 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>> What are the specific reasons for choosing OpenSSL Bignums over GMP,
>> outside of extension availability (which is totally a path I don't want us
>> to go down -- see also recent attempts to duplicate ext/mbstring into
>> ext/standard)? Are there any particular properties of the openssl
>> implementation that are beneficial for certain applications?
>
> I'd say having it for free when you have OpenSSL is a factor. If it were
> separate extension, I'd say the right route is to just make PECL ext as
> usual, but since this kind of has the natural place in openssl, it may
> be a bit different.
>
> I do see a point though that somehow integrating with the rest of
> OpenSSL would be a good thing then. After all, if you have code that
> does some interesting stuff with data but you can't use openssl pkey
> functions to input/output the results, it turns into reimplementing the
> whole crypto system and that's usually not a good idea.
>
Is the feedback then that we should expose /more/ of the OpenSSL API?
I'm happy to expand this to encompass more of the crypto library
functions.
-Sara