| Being compatible with someone elses encryption, is not usually as easy at sounds. Every encryption, like crypt and rijndael (AES) have many options that make the result completely different. SALT, how the key is generated, what hashing is used on key, size of the key, etc. And some libs use a variation of a standard, that is very difficult to dupe on another programming environment. I have done this before, and what I found that helped.... Use OpenSSL as test bed. Get a sample of unencrypted data and encrypted data from your client. Find out what library they are using to create, and the options they are using. You may even try to get the code snippet from them, they use to create in there app. Look up there app or lib on the net, and get docs on those options, and figure out how that translates to openssl. Then play with openSSL command line, try to duplicate the options for the encryption method. Do it until you can decrypt the encrypted data, and it matches the unencrypted data. Then you can write a script to call openssl on with witango server, or use my witango_cmd to call it. You can try <@cipher> but it doesn't support the type of encryption you mentioned. Here is some info on doing it in perl, and how it is compatible with openssl. You could also call a perl script from witango. http://cpan.uwinnipeg.ca/htdocs/Crypt-CBC/Crypt/CBC.html
-- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Nov 15, 2005, at 9:47 PM, David Shelley wrote:
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
