←back to thread

1318 points xvector | 1 comments | | HN request time: 0.001s | source
Show context
rmbryan ◴[] No.19825581[source]
Update: We have rolled out a partial fix for this issue. We generated a new intermediate certificate with the same name/key but an updated validity window and pushed it out to users via Normandy (this should be most users). Users who have Normandy on should see their add-ons start working over the next few hours. We are continuing to work on packaging up the new certificate for users who have Normandy disabled.
replies(20): >>19825596 #>>19825603 #>>19825612 #>>19825623 #>>19825631 #>>19825665 #>>19825705 #>>19825721 #>>19825744 #>>19825813 #>>19825905 #>>19825998 #>>19826421 #>>19826769 #>>19826772 #>>19826878 #>>19827050 #>>19829585 #>>19831941 #>>19840386 #
brador ◴[] No.19825596[source]
What is Normandy?
replies(2): >>19825604 #>>19825613 #
megous ◴[] No.19825604[source]
https://wiki.mozilla.org/Firefox/Normandy/PreferenceRollout
replies(1): >>19825619 #
chinathrow ◴[] No.19825619[source]
So is that a backdoor into my prefs? How can I check if Normandy is active on my installation?
replies(2): >>19825625 #>>19825696 #
verdandi ◴[] No.19825625[source]
Type about:config in the address bar and search for 'app.normandy.enabled' flag.
replies(3): >>19825647 #>>19825659 #>>19826386 #
DoctorOetker ◴[] No.19825647{4}[source]
here the flag is true but the extensions are still unsupported
replies(1): >>19825801 #
1. Yoric ◴[] No.19825801{5}[source]
It may take a little time for the partial fix to be distributed.