Thanks for the help. I installed the FF plugin. That way, I could easily undo it since that plugin defeats the security stuff that both FF and Chrome have created specifically to protect the end users against badly configured servers. I see in the ALPA Scheduling Committee brief that UAL knows something is wrong. Hopefully it gets fixed shortly so this workaround isn't needed.

Thanks again!

 

The best way to put the company on notice is to have the MEC demand an extension to the bidding window another 10 days! They'll fix it quick.

 

Might consider resetting those to "true" when you're done on the UAL site.

 

Rick:

What are the repercussions if you don't?

 

With it set to FALSE Firefox will still warn you that you are connecting to a dangerous or weak server (UAL) and ask if you wish to continue at your own risk. With it set to TRUE, it forbids you from connecting to such server - it makes the decision for you.

The danger of having it set to FALSE is that you could potentially try connecting to a phishing server unintentionally (a server pretending to be your bank and try to steal you login credentials), and even after being warned by Firefox, agree to continue putting your identity and computer at risk.

If you choose to have it set to FALSE just be sure that you never ignore the server security warning and only agree to continue if you are certain that you are connecting to your intended server (connecting via CCS link or such.)

I use Firefox only for company business (CCS & Skynet); Apple Safari with high security restrictions for all Banking; and Chrome for general goofing around the web - that way even if some malicious tracker sneaks by Chrome, it will remain isolated from my work or banking.