Errors accessing FAA's Pilotweb

The only exception is that careful thinking about making the exception was
done by an idiot who doesn't fly, which assumes of course that one is
thinking carefully.

On Feb 1, 11:02*pm, "Viperdoc" wrote:
The only exception is that careful thinking about making the exception was
done by an idiot who doesn't fly, which assumes of course that one is
thinking carefully.

I prefer this interpretation: Notice the original reply used 'careful
thinking' twice w/in the same paragraph. The second reference attempts
to imply that only certain individuals have the ability. Guess into
which group he places himself? It's a thinly veiled attempt at self-
inflation.

In any event: It was not a hard requirement by any means. There are
those who are quite familiar with NAIMES and who already knew that the
site is trusted. This includes, but it not necessarily limited to,
pilots.

Again, much ado about nothing, made into something, by no one in
particular.

Jon writes:

In any event: It was not a hard requirement by any means. There are
those who are quite familiar with NAIMES and who already knew that the
site is trusted.

That's not what the SSL certificate is for.

On Feb 2, 3:23*pm, Mxsmanic wrote:
Jon writes:
In any event: It was not a hard requirement by any means. There are
those who are quite familiar with NAIMES and who already knew that the
site is trusted.

That's not what the SSL certificate is for.

So the certificate is self-signed. I trust NAIMES.


Sorry, gotta get back to work with the NAIMES folks.

Have fun in virtual land, simboy...

Jon writes:

So the certificate is self-signed.

No, it just isn't in the browser database.

I trust NAIMES.

The problem is with determining whether or not the certificate really came
from NAIMES.

It seems that our self proclaimed expert in everything from photography to
flying to breast feeding actually very little understanding of computers,
which is probably why he can't find gainful employment.

On Feb 3, 12:29*pm, Mxsmanic wrote:
Jon writes:
So the certificate is self-signed.

No, it just isn't in the browser database.

I trust NAIMES.

The problem is with determining whether or not the certificate really came
from NAIMES.

It did

Jon writes:

It did

How do you know?

Mxsmanic wrote:
Jon writes:

So the certificate is self-signed.

No, it just isn't in the browser database.

Yes, the certificate is self-signed.


--
Jim Pennino

Remove .spam.sux to reply.

writes:

Yes, the certificate is self-signed.

Top-level certificates are not signed. They have to be trusted.