Everything
php
Learn Community Releases The PHP Project
Home » Project » Newsgroups » php.internals » openssl extension maintainer? »

openssl extension maintainer?

php.internals

Brandon Fosdick

20 years ago
Is the OpenSSL extension still being maintained? I'm looking at adding some needed functionality and don't know who to talk to about it.

Hannes Magnusson

20 years ago
Hi Brandon On 4/23/06, Brandon Fosdick <bfoz@bfoz.net> wrote:
> Is the OpenSSL extension still being maintained? I'm looking at adding some needed functionality and don't know who to talk to about it. >
php-src/EXTENSIONS: EXTENSION: openssl PRIMARY MAINTAINER: Wez Furlong <wez@php.net> MAINTENANCE: Maintained STATUS: Experimental SINCE: 4.0.4 -Hannes

Brandon Fosdick

20 years ago
Hannes Magnusson wrote:
> Hi Brandon > > On 4/23/06, Brandon Fosdick <bfoz@bfoz.net> wrote: >> Is the OpenSSL extension still being maintained? I'm looking at adding some needed functionality and don't know who to talk to about it. >> > php-src/EXTENSIONS: > EXTENSION: openssl > PRIMARY MAINTAINER: Wez Furlong <wez@php.net> > MAINTENANCE: Maintained > STATUS: Experimental > SINCE: 4.0.4
I guess I missed that. Thanks.

Wez Furlong

20 years ago
You can reach me at this email address too. --Wez. On 4/23/06, Brandon Fosdick <bfoz@bfoz.net> wrote:

Brandon Fosdick

20 years ago
Wez Furlong wrote:
> You can reach me at this email address too.
Which address do you prefer? I need the PKCS12 functions and the ability to extract public keys, so I was thinking I'd add both, but I don't want to step on anybody's toes. I've never played around in the PHP internals before so I don't know how things work around here. Any advice?

Wez Furlong

20 years ago
On 4/24/06, Brandon Fosdick <bfoz@bfoz.net> wrote:
> Wez Furlong wrote: > > You can reach me at this email address too. > > Which address do you prefer?
This one for PHP stuff.
> I need the PKCS12 functions > and the ability to extract public keys
Like this: http://us2.php.net/manual/en/function.openssl-pkey-get-public.php or something else?
>, so I was thinking I'd add both, but I don't want to step on anybody's toes. > I've never played around in the PHP internals before so I don't know how > things work around here. Any advice?
Just have a go at making it work. If you get stuck, try to find some other code that does a similar thing to what you want. If that fails, try asking for help on IRC at #php.pecl on EFNet. If you don't do IRC, or no one is around, then you can also try asking for help on pecl-dev@lists.php.net. It's worth reading though Sara Golemon's extension writing articles on zend.com before you begin. There are also a number of conference presentation slides hanging around the 'net written by Wez Furlong and Marcus Boerger, among others. Once you're happy with the changes you've made, send a diff to the mailing list (and Cc: me) and we'll see about integrating it into CVS. There's a README.SUBMITTING-PATCH text file in the PHP source root that should describe this part of the process. Good luck! --Wez.

Brandon Fosdick

20 years ago
Wez Furlong wrote:
> Like this: > http://us2.php.net/manual/en/function.openssl-pkey-get-public.php > or something else?
Close, but I need them in PEM format.

Wez Furlong

20 years ago
Ah yes. http://us3.php.net/manual/en/function.openssl-pkey-export.php almost does what you want... but only works on private keys. I'd welcome a patch for that too. --Wez. On 4/25/06, Brandon Fosdick <bfoz@bfoz.net> wrote:

Brandon Fosdick

20 years ago
Wez Furlong wrote:
> Ah yes. > http://us3.php.net/manual/en/function.openssl-pkey-export.php almost > does what you want... but only works on private keys. > > I'd welcome a patch for that too.
Do you want separate patches for PKCS12 and PEM keys or should it be all one patch? Has anything changed that would require me to work from the CVS version or can I stick with the 5.1.2 release?

Wez Furlong

20 years ago
Just one patch will be fine. We usually accept patches for new features against HEAD of CVS only, but with the unicode development effort that is ongoing in HEAD, you might find it a little bit harder to do that. My suggestion is to make the patch for 5.1.2 and make sure it all works first, and then have a go at making it against HEAD. If you're lucky, the same patch will apply against both versions. If not, there will be a few minor differences for unicode. I'll be happy to see either or both patches and we can take it from there. --Wez. On 4/27/06, Brandon Fosdick <bfoz@bfoz.net> wrote: