Errors accessing FAA's Pilotweb

"Robert M. Gary" wrote in message
...
On Jan 30, 4:22 pm, Mxsmanic wrote:
Is anyone else getting SSL security errors when trying to access the FAA
Web
site's Pilotweb pages? I tried to look up TFRs today and got an error
message
saying the certificate issuer was unknown. One URL that does this is:

https://pilotweb.nas.faa.gov/center.html

I'm sorry, but that is just **too** funny!!! Why are you interested
in TFRs?

-Robert

It's called insanity. Don't try to explain it.

Viperdoc writes:

Why would anyone actually give a **** about this?

A pilot trying to get information on TFRs and NOTAMs would certainly care
about it.

A pilot trying to get information on TFRs and NOTAMs would certainly care
about it.

A real pilot or any other normal rational individual could care less about
you and your computer, since you are not a pilot and have no need to know
about TFRs.

writes:

If you were to have looked at the certificate, you would have found
that it was issued by USNS by the organizational unit NAIMES.

I did, and that was the name on the certificate.

USNS is the United States NOTAM System.

NAIMES is the National Airspace System Aeronautic Information Management
Enterprise System.

To put it simply, the certificate is self-signed by the FAA.

Actually, you don't know who created the certificate. Anyone can create a
certificate with any name. That's why you need to get the certificate from a
trusted source.

However, since these sites are not critical for me, I just added the
certificate, even though it wasn't possible to verify its origin.

No one cares what you look up, since you don't fly.

Robert M. Gary writes:

I'm sorry, but that is just **too** funny!!! Why are you interested
in TFRs?

I check them before flights, but in this case I wanted to see if there was a
TFR for that volcano in Alaska (and there is).

I check them before flights, but in this case I wanted to see if there was
a
TFR for that volcano in Alaska (and there is).

There could be ice, thunderstorms, and volcanic ash from the surface to the
flight levels, but it doesn't matter, since your flights are all imaginary
and don't mean anything to anyone in the entire world except you and the
people you annoy by wasting bandwith.

You need to start thinking about being mentally green and stop polluting
this and other NG's.

Mxsmanic wrote:
writes:

If you were to have looked at the certificate, you would have found
that it was issued by USNS by the organizational unit NAIMES.

I did, and that was the name on the certificate.

USNS is the United States NOTAM System.

NAIMES is the National Airspace System Aeronautic Information Management
Enterprise System.

To put it simply, the certificate is self-signed by the FAA.

Actually, you don't know who created the certificate. Anyone can create a
certificate with any name. That's why you need to get the certificate from a
trusted source.

You mean like the FAA?

However, since these sites are not critical for me, I just added the
certificate, even though it wasn't possible to verify its origin.

What has "not critical for me" to do with the issue and if you want
to know how to verify its origin you need to hire a computer professional.


--
Jim Pennino

Remove .spam.sux to reply.

Viperdoc writes:

A real pilot or any other normal rational individual could care less about
you and your computer, since you are not a pilot and have no need to know
about TFRs.

My computer is not the one he needs to access to learn about TFRs and NOTAMs.
The one he needs to access is the one with the problem.

writes:

You mean like the FAA?

Yes, but I couldn't find a source for the certificate on the FAA site.

What has "not critical for me" to do with the issue ...

I explained why I made an exception for this certificate, something that
normally isn't a good idea.

... and if you want to know how to verify its origin you need
to hire a computer professional.

Not at all. You can do that without anyone's help.