Minal:
Hmm. First, I'd check the validity of the two algorithms.
So I'd have the old Windows API MD5 something, and compare that
hash with the output of the new Perl MD5. The result should be
exact, of course. After that, I'd do the same for the RSA key:
sign the same file with the two systems and compare the outputs.
I'm hopeful that this is just an EOL marker or something.
-Scott
On Tue, 4 Feb 2003, Minal Amle wrote:
> Hello Scott,
>
> While testing the Partnership file and Registration file compatibility with
>kaboodle, I am facing some problem with the signature verfication of the files.
> I am trying to find out the reason, why is it failing at the time of verification,
>though we have used the similar algorithms (i.e. RSA for signing-verification and MD5
>for hashing ) at both the ends. Previously we were using similar windows crypto API
>at both the ends (kaboodle and website). And now we have perl crypto module at
>website end and windows crypto API at kaboodle end. But this should not make any
>difference.
> Any suggestions?
>
> Regadrs,
> Minal Amle
> Software Engineer
> OAS Information Systems Pvt. Ltd.
> #2, Symphony-C, Range Hills Road,
> Pune 411020
> Tel: +91 20 5520311
> Fax: +91 20 5520312
> Email: [EMAIL PROTECTED]
> http://www.oas.co.in
>
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
