<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Thanks! This provided more progress. I was able to compile a working example from the examples directory and change DES to AES in that same example file. That worked when using the locally compiled installation.
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div class="">After a lot of experimentation and working back and forth with the system default installation as well as the locally compiled one, I was finally able to narrow it down to just one of the options suggested by the example compile which also ended
up making the RPM version also work. I also found and noted that the recommended options are listed in the file</div>
<div class="">/usr/lib64/xmlsec1Conf.sh</div>
<div class=""><br class="">
</div>
<div class="">Given the particular type of bad behavior I was experiencing, this option does make sense. The option was:</div>
<div class="">-DXMLSEC_NO_SIZE_T</div>
<div class=""><br class="">
</div>
<div class="">It is unclear to me why that option is needed because there is a size_t type in the system. But the xmlsec code and configure script looks like it wants this specifically to be sizeof = 4 but size_t has a sizeof = 8.</div>
<div class=""><br class="">
</div>
<div class="">So obviously it would be bad if the libraries were compiled with xmlSecSize = 4 but my code tried to compile with xmlSecSize = 8. That would easily cause a mismatch in the location of the result fields in the encCtx structure.</div>
<div class=""><br class="">
</div>
<div class="">I guess there is a dependency on 4 byte size which makes it not possible to just use size_t directly on whatever architecture you’re on?</div>
<div class=""><br class="">
</div>
<div class="">Thanks again for pointing me in the right directions!</div>
<div class="">Regards,</div>
<div class="">Russ.</div>
<div class=""><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">On Jun 8, 2017, at 7:15 PM, Aleksey Sanin <<a href="mailto:aleksey@aleksey.com" class="">aleksey@aleksey.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">
<div class="">Great, this tells us that this is compiler or linker issue: xmlsec tool compiles with exactly the same flags as the library itself.</div>
<div class=""><br class="">
</div>
<div class="">Can you try to compile the examples/ folder? Do the examples work as expected? If yes then can you try to compile your program with the same gcc flags? Another option is to try pkg-config (if you have it installed).<br class="">
<br class="">
Aleksey</div>
<div class=""><br class="">
On Jun 8, 2017, at 7:11 PM, Russell Beall <<a href="mailto:beall@usc.edu" class="">beall@usc.edu</a>> wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">Well, I guess I’m doing something wrong or my environment is messing things up. Your command worked just fine:
<div class=""><br class="">
</div>
<div class="">$ xmlsec1 --decrypt --aeskey ~iamadmin/dev_common/goldenpr/.sorkeys/symkey_GDS encrypted_data.xml<br class="">
<?xml version="1.0"?><br class="">
<Ping/></div>
<div class=""><br class="">
</div>
<div class="">Russ.<br class="">
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jun 8, 2017, at 6:43 PM, Aleksey Sanin <<a href="mailto:aleksey@aleksey.com" class="">aleksey@aleksey.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
Can you try to reproduce this issue with xmlsec1 command line utility?<br class="">
<br class="">
<div class=""><br class="">
</div>
-- Aleksey
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<br class="">
On Jun 8, 2017, at 6:34 PM, Russell Beall <<a href="mailto:beall@usc.edu" class="">beall@usc.edu</a>> wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">
<div class="">I must admit I don’t have a lot of practice with C debuggers, so I haven’t examined the structure yet, but I did try upgrading to the latest 1.2.24 as well as downgrading back to 1.2.16. Both of those versions also exhibit this behavior. (I
deleted entirely the previous version before compiling and linking with the replacement, so I know it was using the expected version).
<div class=""><br class="">
</div>
<div class="">Then, the next step I took was to boil it down to the most basic possible example. I downloaded your code from this link:</div>
<div class=""><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.aleksey.com_xmlsec_api_xmlsec-2Ddecrypt-2Dwith-2Dkeys-2Dmngr.html-23xmlsec-2Dexample-2Ddecrypt2&d=DwMFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=SR9eFKXsUSQlRXnWYTbZk9hc8HcVeC3gT6Q-9kIWBsE&s=5bcrqz6R-4tkR1Ye02H5nFqfGE97CkzVmv_AfxcsMhI&e=" class="">https://www.aleksey.com/xmlsec/api/xmlsec-decrypt-with-keys-mngr.html#xmlsec-example-decrypt2</a></div>
<div class=""><br class="">
</div>
<div class="">changed only the use of DES keys to AES keys. Dropped my encrypted xml packet in a file and then ran the code with the file and key. The same exact behavior occurred. Very odd. This should now be a vanilla install and Centos7 VM with a vanilla
example.</div>
<div class=""><br class="">
</div>
<div class="">I compiled with this</div>
<div class="">
<div class="">$ /usr/bin/gcc -I/usr -I/usr/include/libxml2 -I/usr/local/iamadmin/xmlsec/include/xmlsec1 -L/usr/lib64 -L/usr/local/iamadmin/xmlsec/lib -lxmlsec1 -lxmlsec1-openssl -lxslt -lxml2 -lcrypto -DXMLSEC_CRYPTO_OPENSSL decryptstd.c</div>
<div class=""><br class="">
</div>
<div class="">and ran with this.</div>
<div class="">$ export LD_LIBRARY_PATH=/usr/local/iamadmin/xmlsec/lib</div>
<div class="">$ a.out encrypted_data.xml ~iamadmin/dev_common/goldenpr/.sorkeys/symkey_GDS</div>
<div class="">Error: decryption failed</div>
<div class="">Decrypted XML data:</div>
<div class=""><?xml version="1.0"?></div>
<div class=""><Ping/></div>
</div>
<div class=""><br class="">
</div>
<div class="">I also added one print statement within the failure block to print the document anyway despite the failure, and it shows the document was decrypted even though encCtx_>result is null.</div>
<div class=""><br class="">
</div>
<div class="">I have a coworker who I hear also had this problem with a similar system and hacked around it by just taking the buffer contents from the xmlSecEncCtxDecryptToBuffer function if it isn't null and scanning the original document for the key name.
I’d rather not resort to that if I can use the API as designed. But he is also more experienced with C debuggers and we could take a look at the encCtx structure when he gets back next week.</div>
<div class=""><br class="">
</div>
<div class="">Sorry if I’m taking up too much bandwidth on the list. I hope I’m onto something that will end up being a potentially useful bugfix rather than just missing something stupid.</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Russ.</div>
<div class=""><br class="">
<div class="">
<div class="" style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="">
<div class="" style="orphans: 2; widows: 2; margin: 0px;">=========================</div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;"><b class="">Russell Beall | </b>Systems Programmer IV </div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;">Enterprise Identity Management | University of Southern California </div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;">(213) 740-7221 | <a href="mailto:beall@usc.edu" class="">beall@usc.edu</a></div>
<div class="" style="orphans: 2; widows: 2;"><br class="">
</div>
</div>
<div class="" style="orphans: 2; widows: 2;"><br class="">
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jun 8, 2017, at 3:53 PM, Russell Beall <<a href="mailto:beall@usc.edu" class="">beall@usc.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Ok, thanks. I’ll try those ideas.
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Russ.</div>
<div class=""><br class="">
<div class="">
<div class="" style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div class="">
<div class="" style="orphans: 2; widows: 2; margin: 0px;">=========================</div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;"><b class="">Russell Beall | </b>Systems Programmer IV </div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;">Enterprise Identity Management | University of Southern California </div>
<div class="" style="orphans: 2; widows: 2; margin: 0px;">(213) 740-7221 | <a href="mailto:beall@usc.edu" class="">beall@usc.edu</a></div>
<div class="" style="orphans: 2; widows: 2;"><br class="">
</div>
</div>
<div class="" style="orphans: 2; widows: 2;"><br class="">
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jun 8, 2017, at 3:51 PM, Aleksey Sanin <<a href="mailto:aleksey@aleksey.com" class="">aleksey@aleksey.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">Hm...
next idea is that some compilation flags are different. Basically</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">what
you describe looks like your code is looking at the wrong places</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">in
encCtx struct because it looks different. I would go into debugger</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">and
examine the memory block for encCtx to see how it looks like.</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">Another
approach is to recompile (the lastest) xmlsec version and see</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">if
it solves the problem.</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">Aleksey</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<span class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">On
6/8/17 3:47 PM, Russell Beall wrote:</span><br class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<blockquote type="cite" class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
Yes, the includes point to /usr/include/xmlsec1 and there is only one<br class="">
installation of xmlsec on the box installed via yum.<br class="">
<br class="">
$ yum info xmlsec1<br class="">
Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks, verify<br class="">
Loading mirror speeds from cached hostfile<br class="">
Installed Packages<br class="">
Name : xmlsec1<br class="">
Arch : x86_64<br class="">
Version : 1.2.20<br class="">
Release : 5.el7<br class="">
Size : 555 k<br class="">
Repo : installed<br class="">
From repo : base<br class="">
Summary : Library providing support for "XML Signature" and "XML<br class="">
Encryption" standards<br class="">
URL :<span class="Apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_xmlsec_&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=wlYaqIJM27mvlCJIVYuW4l0Odsgx_qawVLtTbdu2h8I&s=sG2W-Vo4Ho-WqcECYXdPwIh9LaFoEqaKoJjAclYIOQ4&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_xmlsec_&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=wlYaqIJM27mvlCJIVYuW4l0Odsgx_qawVLtTbdu2h8I&s=sG2W-Vo4Ho-WqcECYXdPwIh9LaFoEqaKoJjAclYIOQ4&e=</a><span class="Apple-converted-space"> </span><br class="">
License : MIT<br class="">
Description : XML Security Library is a C library based on LibXML2 and<br class="">
OpenSSL.<br class="">
: The library was created with a goal to support major XML<br class="">
security<br class="">
: standards "XML Digital Signature" and "XML Encryption”.<br class="">
<br class="">
<br class="">
There may be a potential conflict with gsoap where the python and soap<br class="">
libraries seem to be clashing on defines. These may be affecting the<br class="">
internals:<br class="">
/usr/include/python2.7/pyconfig-64.h:1188:0: warning: "_POSIX_C_SOURCE"<br class="">
redefined [enabled by default]<br class="">
#define _POSIX_C_SOURCE 200112L<br class="">
<br class="">
/usr/include/features.h:168:0: note: this is the location of the<br class="">
previous definition<br class="">
# define _POSIX_C_SOURCE 200809L<br class="">
<br class="">
This is a python plugin that receives encrypted XML packets via gsoap.<br class="">
<br class="">
Regards,<br class="">
Russ.<br class="">
<br class="">
<br class="">
<blockquote type="cite" class="">On Jun 8, 2017, at 2:25 PM, Aleksey Sanin <<a href="mailto:aleksey@aleksey.com" class="">aleksey@aleksey.com</a><br class="">
<<a href="mailto:aleksey@aleksey.com" class="">mailto:aleksey@aleksey.com</a>>> wrote:<br class="">
<br class="">
Hm... Can you make sure the library you are using matches<br class="">
the header files you are compiling with?<br class="">
<br class="">
Aleksey<br class="">
<br class="">
On 6/8/17 1:55 PM, Russell Beall wrote:<br class="">
<blockquote type="cite" class="">Hello,<br class="">
<br class="">
First, thank you for all the help I’ve seen flowing through this list<br class="">
over the years. I haven’t had many questions since our code has just<br class="">
been sitting there working most of the time, but it has been nice to see<br class="">
an active community on this product.<br class="">
<br class="">
I’m working on upgrading to xmlsec 1.2.20 on CentOS 7. I’m porting a<br class="">
functioning usage of xmlsec from Solaris using xmlsec 1.2.16. The<br class="">
ported code is practically identical to the online tutorial examples,<br class="">
but for some reason on this updated system, the decryption engine is not<br class="">
producing the data in the encCtx object, even though it is successfully<br class="">
decrypting the XML packet.<br class="">
<br class="">
The output of the document shows this before the decryption:<br class="">
<?xml version="1.0"?><br class="">
<EncryptedData<br class="">
xmlns="<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=-Xwog9L_-70gnLriXpRfsfcT53My74h4l9nz4LDiav4&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=-Xwog9L_-70gnLriXpRfsfcT53My74h4l9nz4LDiav4&e=</a><span class="Apple-converted-space"> </span>"<br class="">
Type="<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23Element&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=n7wOqJl6BkmU1WHOR5aNtn18_k1ceTxMSUW1AicxD00&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23Element&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=n7wOqJl6BkmU1WHOR5aNtn18_k1ceTxMSUW1AicxD00&e=</a><span class="Apple-converted-space"> </span>"><br class="">
<EncryptionMethod<br class="">
Algorithm="<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23aes128-2Dcbc&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=dd-dzD0_VFSpcwn_SGNp3aAR9UweqZXV2m2nUcdGaFA&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2001_04_xmlenc-23aes128-2Dcbc&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=dd-dzD0_VFSpcwn_SGNp3aAR9UweqZXV2m2nUcdGaFA&e=</a><span class="Apple-converted-space"> </span>"/><br class="">
<KeyInfo<br class="">
xmlns="<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2000_09_xmldsig-23&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=nT1UEj-K2M3303ZeBQ8PwTKCzd1dFIQyikCF39ybEqs&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.w3.org_2000_09_xmldsig-23&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=nT1UEj-K2M3303ZeBQ8PwTKCzd1dFIQyikCF39ybEqs&e=</a><span class="Apple-converted-space"> </span>"><br class="">
<KeyName>symkey_GDS</KeyName><br class="">
</KeyInfo><br class="">
<CipherData><br class="">
<CipherValue>N6BDPUv1BIz88n1IL64aTkiShimUMWnZ+c5bVHDMxEs=</CipherValue><br class="">
</CipherData><br class="">
</EncryptedData><br class="">
<br class="">
And shows this after the decryption:<br class="">
<?xml version="1.0"?><br class="">
<Ping/><br class="">
<br class="">
But leaves this data in the encCtx object suggesting that the decryption<br class="">
process did not work:<br class="">
encCtx->result: 0<br class="">
encCtx->encKey: 0<br class="">
encCtx->resultReplaced: 0<br class="">
<br class="">
Besides needing to see the a non-null result status, I also need a<br class="">
non-null encKey object so I can pull the name of the key for use later<br class="">
in encrypting the response packet.<br class="">
<br class="">
Is there something I’m missing about this? Or maybe something peculiar<br class="">
to CentOS 7? Doesn’t seem like much would have changed between xmlsec<br class="">
1.2.16 and 1.2.20.<br class="">
<br class="">
Thanks for any help!<br class="">
Regards,<br class="">
Russ.<br class="">
<br class="">
=========================<br class="">
*Russell Beall | *Systems Programmer IV<span class="Apple-converted-space"> </span><br class="">
Enterprise Identity Management | University of Southern California<span class="Apple-converted-space"> </span><br class="">
(213) 740-7221 | <a href="mailto:beall@usc.edu" class="">beall@usc.edu</a><br class="">
<<a href="mailto:beall@usc.edu" class="">mailto:beall@usc.edu</a>> <<a href="mailto:beall@usc.edu" class="">mailto:beall@usc.edu</a>><br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
xmlsec mailing list<br class="">
<a href="mailto:xmlsec@aleksey.com" class="">xmlsec@aleksey.com</a><span class="Apple-converted-space"> </span><<a href="mailto:xmlsec@aleksey.com" class="">mailto:xmlsec@aleksey.com</a>><br class="">
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_mailman_listinfo_xmlsec&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=5ignWrNrPf6_n_D9cghpaTcszAnGOqzkesdtRUVGv1E&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_mailman_listinfo_xmlsec&d=DwIDaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=1AGkTwrp5nWha7lyn0bYHX4bM0IttToIxnlHQGKlbKE&s=5ignWrNrPf6_n_D9cghpaTcszAnGOqzkesdtRUVGv1E&e=</a></blockquote>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br class="">
xmlsec mailing list<br class="">
<a href="mailto:xmlsec@aleksey.com" class="">xmlsec@aleksey.com</a><br class="">
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_mailman_listinfo_xmlsec&d=DwIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=yjzCQdXNzdU8z7n2-FMBCbA5QAGxAtBULB4oD560OoI&s=w9IMkmVCZwki3XkcR0LXk0cALiRv9LLBudmXSXfM_eE&e=" class="">https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_mailman_listinfo_xmlsec&d=DwIGaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=yjzCQdXNzdU8z7n2-FMBCbA5QAGxAtBULB4oD560OoI&s=w9IMkmVCZwki3XkcR0LXk0cALiRv9LLBudmXSXfM_eE&e=</a><span class="Apple-converted-space"> </span><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">
<div class=""><span class="">_______________________________________________</span><br class="">
<span class="">xmlsec mailing list</span><br class="">
<span class=""><a href="mailto:xmlsec@aleksey.com" class="">xmlsec@aleksey.com</a></span><br class="">
<span class=""><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.aleksey.com_mailman_listinfo_xmlsec&d=DwMFaQ&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=GZq8AbZkmDZnHhY_emMoUA&m=SR9eFKXsUSQlRXnWYTbZk9hc8HcVeC3gT6Q-9kIWBsE&s=hrBUiJ7jBvn1hXwP7td6bOoBkVaWnEGTYZ176W5F_G8&e=" class="">http://www.aleksey.com/mailman/listinfo/xmlsec</a></span></div>
</blockquote>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>