[+santiago] Sounds like a good idea. Santiago also needed to update another web page last time, and send an official notice to the US government about the change. I think this submit requires the same work.
http://www.apache.org/dev/crypto.html Cheers, Brian On Tue, May 6, 2008 at 10:50 AM, Chris Chabot <[EMAIL PROTECTED]> wrote: > Below is the important part of a mail i send to the list last week. I got no > replies to it at the time, probably due to holidays and everything, but > since it might be important for doing things correctly and in the apache > way, I'm reposting it: > > On May 2, 2008, at 2:52 AM, Chris Chabot wrote: > > > > Ps i remember we had went thru some song and dance to be able to include > crypto in shindig (somewhere mid/end of march). The result was that we added > a notice in our NOTICE file about the crypto functions: > > > > > http://svn.apache.org/viewvc/incubator/shindig/trunk/NOTICE?revision=639568&view=markup > > > > In this notice it lists which cryptography actions are present in shindig > it seems: > > The following provides more details on the included cryptographic > software: > > Apache Shindig interfaces with the Java JCE APIs to provide digital > signing and encryption of messages using the AES, SHA1, and HMAC-SHA1 > standards. > > Apache Shindig interfaces with the OAuth library > <http://http://code.google.com/p/oauth/> to provide digital signing of > messages according to the OAuth standard. > > So should i add a bit like: "Apache Shindig's PHP code interfaces with > PHPs mcrypt API's to provide encryption of messages using the AES and > HMAC-SHA1 standards, and uses PHPs sha1function to provide digital signing" > ? > > > >
