# [RFC] Build OpenSSL Module by Default - Thread: https://externals.io/message/72037 - Original archive: https://news-web.php.net/php.internals/72037 - Started by Yasuo Ohgaki on 2014-02-03T05:15:48+00:00 - Messages: 7 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #72037 — Yasuo Ohgaki — 2014-02-03T05:15:48+00:00 URL: https://externals.io/message/72037#72037 Hi all, 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? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --- ## #72039 — Pierre Joye — 2014-02-03T06:22:49+00:00 URL: https://externals.io/message/72037#72039 · In reply to: #72037 hi Yasuo, > 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 --- ## #72041 — Yasuo Ohgaki — 2014-02-03T06:28:12+00:00 URL: https://externals.io/message/72037#72041 · In reply to: #72039 Hi Pierre, > 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 :). I agree that openssl is not the the art from an APIs point of view. I'll wait and see what will happen this year and next year :) For the time being, we may work round and/or load it when it is needed. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --- ## #72066 — Derick Rethans — 2014-02-03T10:01:29+00:00 URL: https://externals.io/message/72037#72066 · In reply to: #72037 > 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? Yes. It's an external library that, although most people will have, causes issues with distributing binaries. I would be in favour turning it on by default, but do I understand correctly that you want to make PHP hard-depend on it? cheers, Derick -- http://derickrethans.nl | http://xdebug.org Like Xdebug? Consider a donation: http://xdebug.org/donate.php twitter: @derickr and @xdebug Posted with an email client that doesn't mangle email: alpine --- ## #72067 — Yasuo Ohgaki — 2014-02-03T10:05:56+00:00 URL: https://externals.io/message/72037#72067 · In reply to: #72066 > Yes. It's an external library that, although most people will have, > causes issues with distributing binaries. I would be in favour turning > it on by default, but do I understand correctly that you want to make > PHP hard-depend on it? > No. Not at all. I wrote in the RFC OpenSSL should be able to disable manually. Module authors must use #if when it is not available. I don't want any module to be hard-depend on OpenSSL module :) Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --- ## #72077 — Jan Ehrhardt — 2014-02-03T10:57:00+00:00 URL: https://externals.io/message/72037#72077 · In reply to: #72039 Pierre Joye in php.internals (Mon, 3 Feb 2014 07:22:49 +0100): >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 :). http://pecl.php.net/package/crypto Jan --- ## #72177 — Yasuo Ohgaki — 2014-02-04T06:54:56+00:00 URL: https://externals.io/message/72037#72177 · In reply to: #72077 Hi Jan, > Pierre Joye in php.internals (Mon, 3 Feb 2014 07:22:49 +0100): > > […] > are > > […] > > http://pecl.php.net/package/crypto > Just read readme.md. I looks a lot nicer! I'll vote for this :) Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net