Qc3DecryptData API vs OPENSSL för AES128 Decryption -- RPG400-L

× 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.

Hi,

As my email to this forum was rejected by admin due to message size issue
so i än afraid whether my läst email was delivered or not to the AS400
experts or not so this is regarding my previous email's query which i had
posted like considering my encodedexchange token values inside those
sample type of XMLs should i conclude that as per my XMLs and
encodedexchange token values which we have decrypted with OPENSSL that can
not be decrypted with this 'Qc3DecryptData API' until i have sufficient
information how that value of encoded exchange token inside sthat sample
XML is coming.
Because OPENSSL did not bother these details and simply decrypted that
data(encodedexchangetoken data) using AES128 Algorithm.
Also could you please specific allt let me know what exact details we need
to decrypt that encodedexchange token data using this Qc3DecryptData API in
case still it could be decrypted using this Qc3DecryptData API.

I believe safer way should be to use Qc3DecryptData API to decrypt such
data provided we have all those minimum data which is Requied to decrypt it
using Qc3DecryptData API.
Please correct me if my understanding is wrong.

Thanks much.....

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.