relevant for waterfox? is there an eta for the fix?
https://www.mozilla.org/en-US/security/advisories/mfsa2020-11/
Classic: https://github.com/MrAlex94/Waterfox/commit/93a181e4ab88983dd98eb1ae3113ccbb68bd30bd
Current: https://github.com/MrAlex94/Waterfox/blob/cba439eb7050bc0b2c4f5c01f93cdea2a042fa05/docshell/base/nsDocShell.cpp#L419
– the lines below seem quite different, at a glance.
Classic: https://github.com/MrAlex94/Waterfox/commit/e2c2e3bb203af673fa40cc9211b441fb67b52b4d
Current: https://github.com/MrAlex94/Waterfox/blob/265e6721798a455604328ed5262f430cfcc37c2f/dom/cache/StreamList.cpp#L136
– I guess.
This is pretty serious...it's being actively exploited.
Firefox patched it and did an emergency release so surely someone can merge those changes? We probably will need fresh builds too @MrAlex94
I'm doing a test build of my fork right now...
https://github.com/ilikenwf/Waterfox/commits/current
I’m including the security patches from today, due either later or tomorrow. There’s one left to implement that’s been a bit of a pain.
after installing this version my waterfox classic still says 2020.03.1 (64-bit)
edit:
but signature date is 2020-04-08 14:35:00 according
https://www.virustotal.com/gui/file/c4ec589573e8590f958ead8aced3a16e0a6411bd475b5b91de3e99b99a107985/details~~
my fault, the new install resulted not in an update but a installation in a different directory Waterfox vs Waterfox Classic
Most helpful comment
I’m including the security patches from today, due either later or tomorrow. There’s one left to implement that’s been a bit of a pain.