× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The web site say entered hex value, so, I'm thinking ASCII/EBCID does not
apply in this case. I would expect Qc3DecryptData also dealing all the data
in hex (bit).
"Rory Hewitt" <rory.hewitt@xxxxxxxxx> wrote in message
news:mailman.33110.1276704721.2580.rpg400-l@xxxxxxxxxxxxxxx
ASCII vs. EBCID, perhaps - do you need to use iconv() either after or
before
the data conversion?

On Wed, Jun 16, 2010 at 8:51 AM, hockchai Lim
<lim.hock-chai@xxxxxxxxxxxxxxx
wrote:

I used the Input Data: 59a10915306238b011ba322354c608e6 and AES key
:8181818181818181818181818181818181818181818181818181818181818181.

On the
http://www.unsw.adfa.edu.au/~lpb/src/AEScalc/AEScalc.html<http://www.unsw.adfa.edu.au/%7Elpb/src/AEScalc/AEScalc.html>site
I get the result of (which is what I expected):
e3c5e2e3404040404040404040404040

But with Qc3DecryptData, I get the result of :
343581ED077DA7C156FB59CC1075D7C0B79BD2778372388ECDF908D54124870E


Any idea where or how I can figure out where I did wrong?




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.