xmlsec command line question
"Myers, Kevin R (Mutual Funds Technology Svcs)" <[email protected]> Fri, 5 Jan 2018 03:55:23 +0000
| Newsgroups | gmane.text.xml.xmlsec |
|---|---|
| Message-ID | <[email protected]> |
--===============0883452950==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_993b2bac0540498589d5a081f236be5aad1hfdexc503ad1prod_"
--_000_993b2bac0540498589d5a081f236be5aad1hfdexc503ad1prod_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Sorry if the answer here is obvious, but was hoping someone could help me u=
nderstand the difference between these two messages from xmlsec while verif=
ying some SAML docs.
1. This first message I get when intentionally trying to verify a (kn=
own to be valid) SAML Metadata file with the wrong cert
func=3DxmlSecOpenSSLEvpSignatureVerify:file=3D..\src\openssl\signatures.c:l=
ine=3D346:obj=3Drsa-sha256:subj=3DEVP_VerifyFinal:error=3D18:data do not ma=
tch:signature do not match
2. However when trying to verify a SAML assertion with the (thought t=
o be) correct cert, or an incorrect cert, I get the following in both cases:
func=3DxmlSecOpenSSLEvpDigestVerify:file=3D..\src\openssl\digests.c:line=3D=
229:obj=3Dsha256:subj=3Dunknown:error=3D12:invalid data:data and digest do =
not match
I'm trying to debug an issue with an SAML assertion failing signature valid=
ation, and I would have expected that trying to verify the assertion with t=
he wrong cert would produce the same error from #1...but regardless of the =
cert, I get the message in #2
Thanks for any help,
Kevin..
************************************************************
This communication, including attachments, is for the exclusive use of addr=
essee and may contain proprietary, confidential and/or privileged informati=
on. If you are not the intended recipient, any use, copying, disclosure, d=
issemination or distribution is strictly prohibited. If you are not the in=
tended recipient, please notify the sender immediately by return e-mail, de=
lete this communication and destroy all copies.
************************************************************
--_000_993b2bac0540498589d5a081f236be5aad1hfdexc503ad1prod_
Content-Type: text/html; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:341976338;
mso-list-type:hybrid;
mso-list-template-ids:1497297520 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.25in;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:2.75in;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.25in;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Sorry if the answer here is obvious, but was hoping =
someone could help me understand the difference between these two messages =
from xmlsec while verifying some SAML docs.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt "Times New Roman"">
</span></span><![endif]>This first message I get when intentionally trying =
to verify a (known to be valid) SAML Metadata file with the wrong cert<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">func=3DxmlSecOpenSSLEvpSignatureVerify:file=3D..\src=
\openssl\signatures.c:line=3D346:obj=3Drsa-sha256:subj=3DEVP_VerifyFinal:er=
ror=3D18:data do not match:signature do not match<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.25in;text-indent:-.25in=
;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt "Times New Roman"">
</span></span><![endif]>However when trying to verify a SAML assertion with=
the (thought to be) correct cert, or an incorrect cert, I get the followin=
g in both cases:<o:p></o:p></p>
<p class=3D"MsoListParagraph"><o:p> </o:p></p>
<p class=3D"MsoNormal">func=3DxmlSecOpenSSLEvpDigestVerify:file=3D..\src\op=
enssl\digests.c:line=3D229:obj=3Dsha256:subj=3Dunknown:error=3D12:invalid d=
ata:data and digest do not match<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">I’m trying to debug an issue with an SAML asse=
rtion failing signature validation, and I would have expected that trying t=
o verify the assertion with the wrong cert would produce the same error fro=
m #1…but regardless of the cert, I get the
message in #2 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">Thanks for any help,<o:p></o:p></p>
<p class=3D"MsoNormal">Kevin..<o:p></o:p></p>
</div>
<p>************************************************************<br>
This communication, including attachments, is for the exclusive use of addr=
essee and may contain proprietary, confidential and/or privileged informati=
on. If you are not the intended recipient, any use, copying, disclosu=
re, dissemination or distribution is strictly prohibited. If you are =
not the intended recipient, please notify the sender immediately by return =
e-mail, delete this communication and destroy all copies.<br>
************************************************************</p></body>
</html>
--_000_993b2bac0540498589d5a081f236be5aad1hfdexc503ad1prod_--
--===============0883452950==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeG1sc2VjIG1h
aWxpbmcgbGlzdAp4bWxzZWNAYWxla3NleS5jb20KaHR0cDovL3d3dy5hbGVrc2V5LmNvbS9tYWls
bWFuL2xpc3RpbmZvL3htbHNlYwo=
--===============0883452950==--