shibd 2.5.3 + windows 2k8r2 + Tivoli IdP odd crash in xsec 1.7

[Cantor, Scott]

On 8/18/15, 2:29 PM, "users on behalf of Jerry B. Altzman" <users-bounces at shibboleth.net on behalf of jbaltz at gmail.com> wrote:

>I get that, it's just this this issue didn't crop up before I added the Tivoli IdP.

Well, the point is, either you're generally signing (which means this should have been happening before) or it's only signing because the IdP is asking it to. If that's the case, it both confirms where the crash is, and provides a workaround by modifying the metadata.

>When I'm told right away to upgrade, the wonder is if this is a known issue (that I could have found by only searching a little more) fixed, or something else. "Just upgrade" on a pre-deployment system is a very different issue that "just upgrade" on a fleet in production.

No, it's because nothing but the latest 2.x version is ever supported and I don't spend any time researching crashes on anything but the supported version. And yes, the xmlsec version was out of date, and included bugs that in some cases caused crashes. I didn't do any thinking about whether they were applicable bugs or not, I don't even remember what they all were.

>No; but...just checked, and found that something stomped on my keyfile (0 bytes? Hello?) which is not something I would have expected. Now I see other issues, but not this one. Thanks! So the upgrade uncovered the real reason. Winning all around!

So a 0 byte key crashed it? While you're digging around, can you file that? Against the SP if you want, there is a Jira over at Apache for xmlsec, but I can move the issue there once I know what's going on. I wouldn't have expected a 0 byte file to make it that far.

-- Scott