Might I suggest that if you submit a patch for this, you add just one function and check for a "file://" prefix to determine if the user want to work with a file or variable? This is the way certificates are handled at present, and I used this method for my patch to try and be consistent with it.
I'm a big fan of consistency, but I know others' views differ. I guess it's over to Wez for guidence, since it's his extension?
Richard.
From: Eric COLINET <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
CC: <[EMAIL PROTECTED]>
Subject: Re: [PHP-DEV] [PATCH] openssl_pkcs7_encrypt to/from variable or file
Date: Wed, 05 Nov 2003 12:57:20 +0100
Hi !
In the same series ..
I have no patch to provide but i've written two functions related to php_openssl:
openssl_pubkey_export
openssl_pubkey_export_to_file
That simply allow the export of public keys that seems to be not possible before.
I there is no special reason for that i can submit them (they are small modification of openssl_pkey_export & openssl_pkey_export_to_file)
Eric
_________________________________________________________________
Tired of 56k? Get a FREE BT Broadband connection http://www.msn.co.uk/specials/btbroadband
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
