Sumo/Unofficial FF 61 Support Report

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

UNOFFICIAL SUMO Firefox for Desktop 61 Support Report

• Release date was Tuesday June 26, 2018

Source Documents

• SUMO contributor support forum thread for firefox 61 for desktop
• Firefox 61 for Desktop Release Notes
• Joni's Firefox for 61 Desktop updated SUMO KB articles:
  • Access hidden tabs in Firefox
  • "Home" panel in preferences (bug 1467771)
    • change my home page - update
    • restore previous session - update
    • set the home page - update
    • Home page with pipe character opens extra tabs when Firefox starts - update
    • display or hide content new tab display - update
    • Firefox options, preferences and settings - update

tl;dr for stakeholders

• Anti-virus issues yet again, every 7 weeks (e.g.FF60 was Kaspersky, FF61 is Avast), painful and needless anti-virus issues IMHO AV vendors need to address this :-) <--- this affects Chrome as well as Firefox

Week 1 (June 26-July 2, 2018)

• 28June2018 bug 1468892#c60 <--- "As of now Avast does appear to have patched the problem. Running with Avast update 180628-08 both FF61.0 and FF62.0b3 are not experiencing any problems. Both are making TLS 1.3 connections with bleepingcomputer.com, www.theregister.co.uk, and tls13.crypto.mozilla.org. Sorry to cause you folks so much trouble... 1/2 ;-)" <--- so Avast fixed it?!? To Be Confirmed
• 27June2018 bug 1468892 - SSL_ERROR_RX_RECORD_TOO_LONG with Avast interpreting TLS 1.3 connections incorrectly ---> Avast (and probably AVG) has a TLS bug that is affecting Firefox <--- hooray a*ti virus, NOT :-)
  • bug 1471672 - Rollout a Normandy recipe that turns off (pref'able) TLS 1.3 until Avast rolls out a fix for bug 1468892
  • Avast / AVG workaround until Avast fixes their bug was documented by super fabulous SUMO volunteer, Philipp M:
    • Troubleshoot the "Secure Connection Failed" error message