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.
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.
midrange.com
