I'll second sgifford's suggestion: First round-trip the encryption in one language. Then write the encryptor (or decryptor) in the other language and debug until you get the same output for the same input with both versions. Once you've debugged that, then you can encrypt the other half of the pair in the other language.
One additional thing I'll suggest: If you look up papers on the web for the encryption scheme you're interested in, you'll often find examples of plaintext, key and encrypted text. Using those examples you can (a) find your bugs more easily, and (b) ensure that you don't accidentally "debug" the wrong side of things. (I've done that before: My "debugged" version would encrypt and decrypt, but there was a bug that seriously compromised the integrity of the encoding scheme. Had I bothered to compare my encrypted text to the version in the paper, I'd've found the bug much sooner. Then maybe the junk version wouldn't have made it into production..... Blecch!)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||