Suggesting additional FF about:config privacy settings #525

New Issue

2018-09-30T09:06:42Z

gryzor2 commented

2018-09-30 09:06:42 +00:00

(Migrated from github.com)

Hi,

I believe firefox users would benefit from having these settings in about:config :

media.peerconnection.dtmf.enabled false
https://bugzilla.mozilla.org/show_bug.cgi?id=1313406

https://bugzilla.mozilla.org/show_bug.cgi?id=1430213
media.peerconnection.rtpsourcesapi.enabled false

media.peerconnection.simulcast false
https://wiki.mozilla.org/Media/WebRTC/ReleaseNotes/46#IMPORTANT:_Simulcast_landed_and_is_pref.27d_on

privacy.trackingprotection.storagerestriction.enabled true
https://bugzilla.mozilla.org/show_bug.cgi?id=1461921

Additionally, these three keys do not exist by default and must be created by users :

security.ssl.disable_session_identifiers boolean true
https://bugzilla.mozilla.org/show_bug.cgi?id=967977
(SSL session caches are abused by GAFAM, which use them as low level TCP cookies)

toolkit.telemetry.coverage.opt-out boolean true
https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firefox.html

extensions.fxmonitor.enabled boolean false
https://www.ghacks.net/2018/08/25/firefox-62-firefox-monitor-system-add-on-integration/

Cheers,

Hi, I believe firefox users would benefit from having these settings in about:config : media.peerconnection.dtmf.enabled false https://bugzilla.mozilla.org/show_bug.cgi?id=1313406 https://bugzilla.mozilla.org/show_bug.cgi?id=1430213 media.peerconnection.rtpsourcesapi.enabled false media.peerconnection.simulcast false https://wiki.mozilla.org/Media/WebRTC/ReleaseNotes/46#IMPORTANT:_Simulcast_landed_and_is_pref.27d_on privacy.trackingprotection.storagerestriction.enabled true https://bugzilla.mozilla.org/show_bug.cgi?id=1461921 Additionally, these three keys do not exist by default and must be created by users : --------------------------------------------------------------------------------------------------------- security.ssl.disable_session_identifiers boolean true https://bugzilla.mozilla.org/show_bug.cgi?id=967977 (SSL session caches are abused by GAFAM, which use them as low level TCP cookies) toolkit.telemetry.coverage.opt-out boolean true https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firefox.html extensions.fxmonitor.enabled boolean false https://www.ghacks.net/2018/08/25/firefox-62-firefox-monitor-system-add-on-integration/ Cheers,

👍 1

ghost commented

2018-09-30 09:30:46 +00:00

(Migrated from github.com)

@kewde

kewde commented

2018-09-30 15:51:08 +00:00

(Migrated from github.com)

I have a few Q's abot the following ones?

media.peerconnection.rtpsourcesapi.enabled
media.peerconnection.simulcast false

What's the reasoning for disabling these two?

I have a few Q's abot the following ones? ``` media.peerconnection.rtpsourcesapi.enabled media.peerconnection.simulcast false ``` What's the reasoning for disabling these two?

gryzor2 commented

2018-09-30 19:03:53 +00:00

(Migrated from github.com)

Hi kwede,

No big reasoning ; I tend to disable media.peerconnection.* generally.
I confess I have not looked deep.

Hi kwede, No big reasoning ; I tend to disable media.peerconnection.* generally. I confess I have not looked deep.

👍 1

ghost commented

2018-09-30 19:25:31 +00:00

(Migrated from github.com)

Yeah, let's not unnecessarily remove functionality. Though if anyone can suggest a good reason to disable those, we can recommend disabling them too.

Apart from those two, @kewde, do you approve?

Yeah, let's not unnecessarily remove functionality. Though if anyone can suggest a good reason to disable those, we can recommend disabling them too. Apart from those two, @kewde, do you approve?

ghost commented

2018-09-30 19:26:14 +00:00

(Migrated from github.com)

@beardog108 What do you think about these settings?

Atavic commented

2018-10-02 23:01:48 +00:00

(Migrated from github.com)

media.peerconnection.enabled is the master switch.
I'm not using any live streaming service, so I disable it.

rtpsourcesapi is used by WebRTC.

Simulcast in WebRTC allows sending multiple resolutions/framerates of the same source.

media.peerconnection.enabled is the master switch. I'm not using any live streaming service, so I disable it. *rtpsourcesapi* is used by WebRTC. > [Simulcast in WebRTC allows sending multiple resolutions/framerates of the same source](https://bugzilla.mozilla.org/show_bug.cgi?id=1288904#c30).

ghost commented

2018-10-03 10:41:52 +00:00

(Migrated from github.com)

rtpsourcesapi is used by WebRTC.

Though you can disable WebRTC without disabling rtpsourcesapi, right?

> rtpsourcesapi is used by WebRTC. Though you can disable WebRTC without disabling rtpsourcesapi, right?

Atavic commented

2018-10-03 22:53:04 +00:00

(Migrated from github.com)

It's an API used inside WebRTC, see here.

It's an API used inside WebRTC, see [here](https://github.com/w3c/webrtc-pc/issues?q=is%3Aissue+is%3Aopen+label%3ASimulcast).

kewde commented

2018-10-07 11:33:40 +00:00

(Migrated from github.com)

I've had some experience with simulcasting, essentially it will tailor the video resolution to your internet connection. Disabling WebRTC (read: PeerConnection) should take care of it as a whole.

This repo is archived. You cannot comment on issues.