Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72039
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAGa2bXZ8QSUD9+PxP+DsdnhC-u-tD1Kym6Kom2r2qLRnSGU72Q@mail.gmail.com>
References: <CAGa2bXZ8QSUD9+PxP+DsdnhC-u-tD1Kym6Kom2r2qLRnSGU72Q@mail.gmail.com>
Date: Mon, 3 Feb 2014 07:22:49 +0100
Message-ID: <CAEZPtU6eoEd5CD3WFGyC8-5sDLN2TgXoLH7HBzUE35AtuZRWXQ@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113522968cb9dc04f17a8d28
Subject: Re: [PHP-DEV] [RFC] Build OpenSSL Module by Default
From: pierre.php@gmail.com (Pierre Joye)

--001a113522968cb9dc04f17a8d28
Content-Type: text/plain; charset=UTF-8

hi Yasuo,


On Feb 3, 2014 6:16 AM, "Yasuo Ohgaki" <yohgaki@ohgaki.net> wrote:
> Build OpenSSL Module by Default
> https://wiki.php.net/rfc/build-openssl-by-default
>
> Internal developers and application developers' life could be a lot easier
> if OpenSSL can be used always. There are number of ways to work around w/o
> it (e.g. use `php_win32_get_random_bytes()` (Windows) or reading directly
> from `/dev/xrandom` for random bytes), but life could be easier with
> openssl. e.g. Hardware AES, etc.
>
> Any comments for building openssl by default?

I do not think enabling openssl by default is a good thing, as it states
now. We use not to ebable extension by default, if it is meant as must be
configured, if there are external dependencies. ext/openssl and openssl are
also not the state of the art from an APIs point of view (diplomatically
said), both in userland and internally. There are some on going work to
provide better interfaces in userland (I can't find it back, but it was
discussed here or on pecl-dev :).

Cheers,

Pierre

--001a113522968cb9dc04f17a8d28--