Re: Re: [RFC] XML_Encryption
| From: | Lorenzo Alberton | Date: | Wed, 08 Jan 2003 15:14:29 +0000 |
| Subject: | Re: Re: [RFC] XML_Encryption | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-12188@lists.php.net to get a copy of this message | ||
> > > > Just an idea, don´t know how feasible this is.
> > > Well. Loading an extension for AES or an Extension for loading C
> > > Code on the fly ... Where is the diffrence? In both cases you
> > > need an extension.
> > You´re right of course, I should remember to switch my brain on
> > before posting :-)
>
> Am I right, that you are planning operations execution in this order?
>
> 1. Native AES extension.
> 2. If [1] not present, fallback to load extension for loading C code.
> 3. If [2] not present, fallback to PHP code.
Nope. I was planning to use only PHP code because Mcrypt extension
is not compiled by default in common PHP distributions. If that is not
possible (for lack of those algorithms in PEAR), then I'll go for Mcrypt
extension, clearly stating that it is needed for this class to work.
Use of Inline_C would be a nice alternative, but, as George Schlossnagle
pointed out, it isn't a safe one...
Regards,
Lorenzo
PS: Christian... any news? Can I help you with algorithm porting?
---
[Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus]
[Quipo ISP - This E-mail was scanned for viruses by Declude Virus]