Re: assymetric encryption functions based on OpenSSL

I took a look at the two samples. It looks as if the whole business could be abstracted a bit more but I am no expert on OpenSSL so I'm not sure. Two issues which should probably be debated: a) Should we require the user to mess with fopen(), fclose() as part of the API. b) Do we need them to mess with the read_x509 part. c) How is the API handled if the x509 is not in a file but comes from a database as a string? I'm not saying the current API is wrong but I think it needs a review just to make sure that we can make it as easy as possible on the end user. The current examples aren't that simple (i.e. PHP simple). Comments? Andi At 09:03 PM 11/13/00 +0100, Stig Venaas wrote:

On Mon, Nov 13, 2000 at 07:13:53PM +0100, Sebastian Bergmann wrote: Sterling Hughes wrote:

Somebody else with windows experience usually adds the dsp files (at least for my extensions that's been the case :)

I will have a look at it and try to create the project file(s) for MS VisualC++. If my knowlegde does not suffice ... well, then it's up to Daniel :-) Great! Thanks guys. It would be nice if some people would test and comment on the interface. I think it's okay, but if anything needs to be changed, it would be good to do it before it's released. I will write manual entries soon, for pre- liminary documentation, see http://www.venaas.no/php/. I'm using SHA for signatures and RC4 for sealing, there should probably be an optional argument for specifying method. The interface also assumes you get all the data into one string, it's no good for streaming large volumes of data. AND btw, I take no responsibility for any harm my bugs may cause (: Stig -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

--- Andi Gutmans <andi@zend.com> http://www.zend.com/