Re: An SSL question that has been bugging me for years!

[Bradley Stone <bvstone@xxxxxxxxx>]

I wonder if this is something I should bring up with my IBM "rep" that asks
me every 6 months if I have any technical questions they can help with, and
to update my listings in the Global Solutions Directory.  :)

Last time I tried that (I think it was a question regarding AFPDS) I got a
big fat "we dunno", but that was after 2 months and I had forgotten I had
asked them a question.

Brad
www.bvstools.com

On Mon, Jun 29, 2015 at 10:43 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

> 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