-
Notifications
You must be signed in to change notification settings - Fork 552
v144 #1992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
v144 #1992
Conversation
it added as inactive in 140 due to bugs not fixed in time - seems stable now
these comments seems to be inconsistent |
this is FPP: any platform can return 4 or 8 depending on the real number of processors they have: so a binary outcome = entropy
this is RFP: so all mac are 8 and all windows, linux, android is 4 = equivalency of platform, no entropy edit: it was added in FF144 but backported to 143 beta which I did update in the FPP info and also in both checks in TZP see lines78 and also 91 - but I missed updating the RFP info in the user.js |
user.js
Outdated
| // user_pref("network.http.microsoft-entra-sso.enabled", false); // [DEFAULT: false] | ||
| /* 0910: enforce no direct attestation in passkeys [FF144+] | ||
| // [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1981587 ***/ | ||
| pref("security.webauthn.always_allow_direct_attestation", false); // [DEFAULT: false] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Thorin-Oakenpants wrong syntax. should be user_pref rather than pref.
user.js
Outdated
| [1] https://support.mozilla.org/en-US/kb/manage-enhanced-tracking-protection-exceptions | ||
| [2] https://etp-exceptions.mozilla.org/ ***/ | ||
| user_pref("privacy.trackingprotection.allow_list.baseline.enabled", true); // [DEFAULT: true] | ||
| user_pref("privacy.trackingprotection.allow_list.convenience.enabled", false); // DEFAULT: false when ETP Strict manually chosen] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Thorin-Oakenpants missing [ before when
| * This setting controls if the option "Display in Firefox" is available in the setting below | ||
| * and by effect controls whether PDFs are handled in-browser or externally ("Ask" or "Open With") | ||
| * [WHY] pdfjs is lightweight, open source, and secure: the last exploit was June 2015 [1] | ||
| * [WHY] pdfjs is lightweight, open source, and secure: In the last 10 years it has only had |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Thorin-Oakenpants why not mention the June 2015 one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not mention the other one from 2015? why not also mention the one from 2013? - rhetorical q's
I am providing a simple statement of risk over time. In the last 10 years there have been 2.
No description provided.