[dead]
Re:All extensions disabled due to expiration of intermediate...
by tssva on Saturday May 04, 2019 @08:10AM
(#19825941)
Users shouldn't have to search and then be able to understand the code found for such a feature. When a remote capability such as this exists it is Mozilla's responsibility to document how the feature works and the exact capabilities it gives them. Instead of doing so they have produced a wiki entry which appears to falsely describe the capabilities of this remote feature by stating it is used to change default preference values.
Re:All extensions disabled due to expiration of intermediate...
by megous on Saturday May 04, 2019 @10:40AM
(#19826726)
Hacker News
I think people here can be expected to read some code if they are interested in how something works.
[dead]
[dead]
Re:All extensions disabled due to expiration of intermediate...
by dang on Sunday May 05, 2019 @12:16AM
(#19831123)
Please read and follow the site guidelines when commenting here.
Re:All extensions disabled due to expiration of intermediate...
by greendestiny_re on Saturday May 04, 2019 @09:07AM
(#19826178)
All code is available – as a tar.xzipped archive of Firefox source code containing over 150k files and measuring over 1GB in size when unpacked.
Re:All extensions disabled due to expiration of intermediate...
by megous on Saturday May 04, 2019 @10:43AM
(#19826748)
grep -iR normandy
I expect code related to normandy to be ~1k LOC in size and probably written in JS. I haven't checked though, because I don't really care today.
Re:All extensions disabled due to expiration of intermediate...
by devcpp on Saturday May 04, 2019 @02:38PM
(#19828332)
And you shouldn't have to care. No one should. The very fact that this exists and that we are expected to trust it is very disappointing.
Re:All extensions disabled due to expiration of intermediate...
by lordlimecat on Saturday May 04, 2019 @02:27PM
(#19828249)
Open source software can't have a backdoor because the code is available to review.
Got it.