Re: Leadtools 15 - Windows XP SP2 - contact VeriSign.com

I am also getting this same problem with a VB.NET 2.0 application using your V15 components.  I have never had this happen before with anybody elses components.

Have you managed to put together a help sheet on how we can go about fixing this or at least stopping the revocation check from happening?

Regards,

Michael

Hello,

We contacted verisign and got the following information from them:

That would be something that needed to be brought up within your own network admin. Unfortunately, we don't have any information or control when it comes to corporate company's restriction within their firewall. The only thing that I can think of is the Certificate Revocation List (CRL). But normally that is accessible through a web site address. Unless their firewall is restricting that URL address from Verisign.

Thanks,
Maen Badwan
LEADTOOLS Technical Support

Actually, there is a workaround for this. It has been posted as a KB article here: http://support.microsoft.com/kb/936707

So, all you need to do is add the following tags under the <configuration> section to the web.config or app.config file of your project:

  <runtime>
    <generatePublisherEvidence enabled="false"/>
  </runtime>

That's it. CRL Revocation check will not be performed at runtime from now on. However, I have noticed that the check still continues to be done at Design time while you are developing in Visual Studio!

Regards,
kraghavk

Kraghavk you ROCK.
I just ran into this in a big way.  I am writing code for an application which will be deemed unacceptable by my customers if it goes along and opens web connections without explicit approval through all sorts of security minded folks with official titles.  Having an assembly open any port by default is a bad design practice.  We should LOUDLY assert this to all providers of .Net assemblies.  Answers like those posted early in this article are clearly not helpful and serve to tacitly approve bad practices.
Forums FTW!

owned