Sorry didn't mean to imply you wouldn't report it; just figured you
might still be recovering and diagnosing from the mess it created.
And nice blog post. You and I are in synch; "I doubted myself, because
that's usually the most reasonable approach to take." I tend to be that
way too.
Chuck
-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx]
On Behalf Of Lukas Beeler
Sent: Wednesday, October 14, 2009 10:27 AM
To: PC Technical Discussion for iSeries Users
Subject: Re: [PCTECH] Be aware of KB974571 (MS Crypto Security Update)
On Wed, Oct 14, 2009 at 16:01, Chuck Lewis
<chuck.lewis@xxxxxxxxxxxxxxxxx> wrote:
Wow that is interesting. Did you report this ?
Of course. Unfortunately, we only have NBD-Response on our Microsoft
support contract, and so far i've just received a boilerplate mail.
Luckily i was able to figure out what the issue is on my own.
Any idea why it would have done that ?
By my non-existing programming expertise, it looks like the licensing
mechanism employed by OCS relied on using "broken" ASN.1, which was
accepted before the security fix, and not after. This is mostly a
guess from the error messages i've seen when trying to fix the issue.
My blog post last night about this topic:
http://projectdream.org/wordpress/2009/10/13/kb974571-crypto-api-update-
may-break-office-communications-server-2007-r2-installations/
By now, it's more or less official, it's on several TechNet blogs.
midrange.com
