×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I've been meaning to ask this for a long time because it happens few and
far between, but still doesn't make sense.
You have an application that uses the SSL APIs. It works fine. Then one
day, a self-signed certificate expires. Maybe you used it for FTP, Client
Access, whatever.
Your SSL application starts ending with RC(-24) expired certificate.
The certificate that expired has nothing to do with the client app.
There's no application name assigned and they're not linked in any way.
Why does this happen? I've also seen it with expired CAs in the *SYSTEM
store. These CAs have nothing to with the client application or it's
partner.
It's like IBM put some code like this in:
If (anyCAExpired) any (certExpired)
throwAnAError
endif
This makes no sense. When it happens trying to explain why almost makes me
feel like I'm the crazy one. :)
Id love to know the reason behind this.
Brad
www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
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
