I've been there before, but am now getting a message stating that I am not authorized. Can someone else try? Why would this be?

Thanks,

R.

www.faa.gov - click on Year 2000 link

-- Roland (nottelling@nowhere.com), June 22, 1999

Answers

Hmmm - same here.
http://www.faa.gov

Mr. K

-- Mr. Kennedy (Mr.K@home.today), June 22, 1999.

I just tried at 1:59 CT to get through and was also asked for a password and denied access. Ya gotta wonder what's happening to freedom of information...

-- Gia (Laureltree7@hotmail.com), June 22, 1999.

They're definitely operating in defensive mode from here on in....

-- lisa (lisa@work.now), June 22, 1999.

The link actually tries to access a different site hosted under a different FFA domain:
http://www.faay2k.com
I do wonder, since it is PW protected now, why there is no link or place to "register" as a user. Is it because they don't want average John Q. Public looking in on reports anymore?
Mr. K

-- Mr. Kennedy (Mr.K@home.today), June 22, 1999.

I tried using this link...

http://www.faay2k.com/

...and got this message: "Please enter your authentication information". Should I believe what John Koskinen said in Frankfort, Kentucky on June 17th about the FAA being ready by June 30th?

-- Linkmeister (link@librarian.edu), June 22, 1999.

Yup! Me too... But we can ALL rest easy 'cause they're "completely compliant, and no Y2K testing is being conducted".

Password the site... Yeah, dat's da ticket!

-- Dennis (djolson@pressenter.com), June 22, 1999.

Well at least I'm in good company. I get the same message as Chuck, no password prompt.

Could it be that June 30 is sneaking up just a little too quickly? Are they doing a frantic "search and replace" on June 30 with September 30?

T.

-- Roland (nottelling@nowhere.com), June 22, 1999.

Roland, exactly. Search & replace.

-- lisa (lisa@work.now), June 22, 1999.

Food for thought...from Worldnet Daily today:

Defense's Y2K worries

------------------------------------------------------------------------

The U.S. Department of Defense is so concerned about the potential for problems associated with the Y2K millennium bug that it is considering unplugging itself from the Internet to defend against a simultaneous cyber assault.

That word comes from Marvin Langston, the deputy chief information officer for the Pentagon, who says the discussions about the plan are "as serious as a heart attack."

"We need to close down back doors around the year 2000 to prevent hacking during Y2K confusion," he said during a panel discussion at an Armed Forces Communications and Electronics Association conference last week.

In the event of a cyber attack, Defense would switch from the public Internet to the Nonclassified Internet Protocol Router Network, or NIPRNET, the military's own Internet with external connections. The military also maintains a Secret Internet Protocol Router Network of classified material without external connections.

Defense Secretary William Cohen, who uses many military websites as if they were his own personal public relations pages, has been cautioning for months that too much information about defense forces and capabilities is available publicly on the Internet.

"The rapid growth of the Internet has created the potential for vulnerabilities in DOD networks," says a Pentagon draft policy that mandates the termination of many unauthorized military Internet connections. "The Defense Science Board warned that networks might be susceptible to more frequent attacks as hackers attempt to masquerade their activities as Y2K bugs. A reinforced policy is needed to protect the security" of the NIPRNET from potential information warfare and Y2K consequences.

The Pentagon's Y2K Management Plan updated this month states that millennium bug remediation efforts can expose systems to information warfare attacks and that some groups or individuals may "take advantage of Y2K problems to implant backdoor software routines, viruses, etc. During Y2K fixes, some individuals may gain full access to systems previously protected from external attacks."

I guess we should be thankful that some people in the Defense Department are making plans to tighten security during an upcoming period of possible instability. But this information from the Pentagon raises a number of questions:

Is the Pentagon really using Y2K as an excuse to move more information readily available to the public into the semi-classified files, making the Defense Department even less open and less accountable to the people?

Is the Department of Defense truly concerned about threats from foreign powers, terrorists, rogue states and domestic enemies, or is this preventative measure more geared to insulating itself from legitimate criticism and the efforts of whistleblowers who monitor activities in government?

By making such provisions, just how bad does the Defense Department anticipate the Y2K bug to be?

If the only threat posed by hackers is temporarily knocking some public information off its public Internet sites, does it really make sense to move all of that public information into non-public sites?

Is the military planning to use these non-public sites as a means of communicating information internally during a possible national Y2K emergency?

Does the Pentagon have any specific knowledge of efforts by groups or individuals planning to use the Y2K bug as cover for cyber terrorist attacks on U.S. sites and installations?

If Y2K terrorists are likely to target the Defense Department, what else can we look forward to them targeting?

Though we're only a little more than six months away from Y2K D-Day, no one in or out of government seems to be offering much reassurance to a public wholly unprepared for major disruptions or long-term inconvenience. Reports like this from the Pentagon only serve to raise more suspicion that government bureaucrats are taking care of themselves but not really doing much of anything to serve the people.

The American people are completely in the dark. Plans are being made -- some of them ominous plans -- around possible Y2K breakdowns. But they are not being readily shared and discussed with the people. That tells me the government doesn't trust the people. If that's the case, the people would be very wise not to put too much trust in the government.

-- Roland (nottelling@nowhere.com), June 22, 1999.

Thanks for posting that, Roland. I also read it this morning (when I was unable to get on THIS site). Worldnet Daily is rather Y2K pumped up today! Worth a look.

-- Will continue (farming@home.com), June 22, 1999.

Works fine for me at 3:42 EST I was just thinking, I don't trust those sites with disclaimers at the bottom. Why bother with any of the print. They're so afraid of the truth so they don't print it. So they print a pretty picture and include the disclaimer so you won't sue WTSHTF.

-- michelle (msj11wm@aol.com), June 22, 1999.

works fine for me here at 12:53 pst too...anyone able to compare and contrast the previous info and see what's changed?

Mike ===================================================================

-- Michael Taylor (mtdesign3@aol.com), June 22, 1999.

You can always sneek in the back door if you think there may be something hidden there Try ftp://ftp.faay2k.com/Default.html

John Ainsworth

-- John Ainsworth (ainsje@cstone.net), June 22, 1999.

Thanks, John.

Here's their FAQ page, which is still riddled with 06/30/1999, and here's the visual for that timeline.

-- lisa (lisa@work.now), June 22, 1999.

I got in just fine. Here is what is what I got:

"Aviation Safety will not be compromised on January 1, 2000 or any other day." - Jane Garvey, Administrator Federal Aviation Administration Click Here for Administrator Garvey's Message Download

Welcome to the Federal Aviation Administration's Year 2000 Web Site

This site is hosted by the FAA Year 2000 Program Office. The Program Office was chartered by FAA Administrator Jane Garvey to coordinate and oversee Year 2000 repair efforts on every system throughout the Agency. The FAA is working hard to ensure that the Agency is prepared for the arrival of the millennium. This site was designed to provide information on the FAA's Year 2000 repair efforts and outline the tools and plans we have developed to beat the Year 2000 challenge at the FAA.

---------------------------------------------------------------------- ----------

A text site is also available.

SITE DISCLAIMER

-- Carol (glear@usa.net), June 22, 1999.

3:45 p.m. Denver time. Got into the site with no problem. No authorization requested.

-- kalani & katiuska (kalani_hanohano@hotmail.com), June 22, 1999.

Got into FAA Y2k Website OK at NZ 10.25 am.

-- Bob Barbour (r.barbour@waikato.ac.nz), June 22, 1999.

Can'tget on to FAA y2k Site at 9:04 EDT - says server is down.

-- dakota (none @thistime.com), June 22, 1999.

hmmm, interesting. Now the password protect is gone.

-- Mr. Kennedy (Mr.K@home.today), June 22, 1999.

Got in at 4:32 am UCT, 23 June 1999.

-- Mad Monk (madmonk@hawaiian.net), June 23, 1999.