Firefox needs to be updated to at least v53.0.3 for login
 

A friend of mine was suddenly unable to log into Fastmail Classic today (June 10, 2017).

• Of course, Classic is disappearing at the end of June, but this was not his problem.
• Old versions of Firefox have a security certificate bug which shows up staring today (June 10). So you should be using FireFox v53.0.3 (released May 19). This update fixed the following bug:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1364240

Bill

LOL :mad: :rolleyes: :D :D :cool:
yeah, I check out the Change logs for all software I use, when I grab U.P.D.A.T.E.S. lol ;p

anyhow.. I hope too many of these issues don't happen again...
what I am referring too is when Mozilla finally goes ahead and SCRAPS ;_;
the XUL based extension system for Firefox....

WHICH IS Firefox's GREATEST FEATURE..!! :D:D:D :(:(:(
and replacing it with crappy and yet to be finished Web extensions API

ie when it happens I will be forced to FOREVER MORE use an outdated version of Firefox ;p

sry for the rant... loi ;p

That must be a very specific bug as even today, two days before the demise of Classic FM, I can still log in to Classic on any computer (Mac or PC) that I have with FF versions earlier than the bug fix version.

I think the issue only affected some Firefox users. Firefox normally forces an update to the latest version when you start it up. Be sure to keep yours updated, since as you probably heard in the news the ransomware attacks are back again, and the first line of defense is an updated browser with the latest security patches.

Bill

The Firefox ESR (Extended Support Release) branch had no issue, probably received the newer credentials. (Mozilla end-of-lifed my MacBook hardware after the April 17 2017 release of Firefox 45.9.0-ESR. Along with the loss of the Classic UI and the Member grade, that's 3 obituaries in my tech generation this year....)

My condolences ;_; :(:(:(

While I keep my Firefox up to date..
once FF v57 rolls out, scrapping XUL/XPCOM Extension system..
essential TOSSING every last FF user and extension developer
RIGHT UNDER THE BUSS.. in favor of the INFERIOR Web-extension system... which really isn't even done yet...

I will be forced to stick with FF v56 till my extension can be either updated or die of a broken heart! :rolleyes: :rolleyes: :p :p :p :p

I feel you. Note that you'd be good with FF out to June 2018 if you swtched to the the current ESR branch cycle, version 52.

ik but I just don't wanna get stuck that far behind... besides there are changes coming in FF v55 that alter the
- places.sqlite database.. which contains (bookmarks, history, fav. icons, etc)

they are stripping out the icons db table and giving it its own database file for some unknown reason.. called "favicons.sqlite"

I think you're right Bill. I didn't have this issue with Chrome but with FF.