Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96562
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <CAESVnVqjJUF=SCua7DiTXZOyfQ9Ztb6o3aVfLywnwY8g=CRnLQ@mail.gmail.com>
References: <CAESVnVqjJUF=SCua7DiTXZOyfQ9Ztb6o3aVfLywnwY8g=CRnLQ@mail.gmail.com>
Date: Sun, 23 Oct 2016 19:20:50 +0100
Message-ID: <CAEKnhAGkcdw3+mzKpYRkoa0u0ZTLXWnKRRYVF_fkdUYbAGvDoA@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c190c54ce58a7053f8c55e8
Subject: Re: [PHP-DEV] [RFC] OpenSSL BigNum support
From: bukka@php.net (Jakub Zelenka)

--94eb2c190c54ce58a7053f8c55e8
Content-Type: text/plain; charset=UTF-8

On Tue, Oct 18, 2016 at 2:35 AM, Sara Golemon <pollita@php.net> wrote:

> As it says on the tin: Wrap the BN (BigNumber) library in OpenSSL.
>
> https://wiki.php.net/rfc/openssl.bignum
>
>
I don't see any reason why we should expose BN API if it's not integrated
with PKEY algorithms. This proposal doesn't really fit with the current
functions IMHO so in this case it doesn't make much sense to introduce it
unless you would also add classes like OpenSSL\RSA , OpenSSL\EC\Key and so
on. I think that having just BigNum in OpenSSL namespace is kind of strange
as BN is just a supporting API in for crypto operations in OpenSSL... If it
was a functional API, than it would probably fit better with current
functions and it would just need to be integrated with openssl_pkey_new
which is more achievable and would be a bit more consistent.

Cheers

Jakub

--94eb2c190c54ce58a7053f8c55e8--