Are there any drawbacks to disabling Webrtc and plugin scanning?

[FriedGenera]

I had an old user.js that included both media.peerconnection.enabled and plugin.scan.plid.all set to false, do these still work or are they unnecessary? I read a long time ago that Webrtc can leak your IP and the second setting prevents sites from knowing what extensions you have, so I was wondering if I can just add them directly to the overrides section.

[yokoffing]

plugin.scan.plid.all is no longer a pref, AFAIK.

For WebRTC, you can read on the prefs but I wouldn't recommend changing them for practical purposes. If you never use video conferencing in Firefox, then you might be okay.

Betterfox/Securefox.js

Lines 1050 to 1078 in 429abb6

	/******************************************************************************
	* SECTION: WEBRTC *
	******************************************************************************/
	// PREF: disable WebRTC (Web Real-Time Communication)
	// Firefox desktop uses mDNS hostname obfuscation and the private IP is never exposed until
	// required in TRUSTED scenarios; i.e. after you grant device (microphone or camera) access.
	// [TEST] https://browserleaks.com/webrtc
	// [1] https://groups.google.com/g/discuss-webrtc/c/6stQXi72BEU/m/2FwZd24UAQAJ
	// [2] https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-mdns-ice-candidates#section-3.1.1
	//user_pref("media.peerconnection.enabled", false);
	// PREF: enable WebRTC Global Mute Toggles [NIGHTLY]
	//user_pref("privacy.webrtc.globalMuteToggles", true);
	// PREF: force WebRTC inside the proxy [FF70+]
	//user_pref("media.peerconnection.ice.proxy_only_if_behind_proxy", true);
	// PREF: force a single network interface for ICE candidates generation [FF42+]
	// When using a system-wide proxy, it uses the proxy interface.
	// [1] https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidate
	// [2] https://wiki.mozilla.org/Media/WebRTC/Privacy
	// [3] https://github.com/zen-browser/desktop/issues/972
	//user_pref("media.peerconnection.ice.default_address_only", true);
	// PREF: force exclusion of private IPs from ICE candidates [FF51+]
	// [SETUP-HARDEN] This will protect your private IP even in TRUSTED scenarios after you
	// grant device access, but often results in breakage on video-conferencing platforms.
	//user_pref("media.peerconnection.ice.no_host", true);

[FriedGenera]

plugin.scan.plid.all is no longer a pref, AFAIK.

For WebRTC, you can read on the prefs but I wouldn't recommend changing them for practical purposes. If you never use video conferencing in Firefox, then you might be okay.

Betterfox/Securefox.js

Lines 1050 to 1078 in 429abb6

	/******************************************************************************
	* SECTION: WEBRTC *
	******************************************************************************/
	// PREF: disable WebRTC (Web Real-Time Communication)
	// Firefox desktop uses mDNS hostname obfuscation and the private IP is never exposed until
	// required in TRUSTED scenarios; i.e. after you grant device (microphone or camera) access.
	// [TEST] https://browserleaks.com/webrtc
	// [1] https://groups.google.com/g/discuss-webrtc/c/6stQXi72BEU/m/2FwZd24UAQAJ
	// [2] https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-mdns-ice-candidates#section-3.1.1
	//user_pref("media.peerconnection.enabled", false);
	// PREF: enable WebRTC Global Mute Toggles [NIGHTLY]
	//user_pref("privacy.webrtc.globalMuteToggles", true);
	// PREF: force WebRTC inside the proxy [FF70+]
	//user_pref("media.peerconnection.ice.proxy_only_if_behind_proxy", true);
	// PREF: force a single network interface for ICE candidates generation [FF42+]
	// When using a system-wide proxy, it uses the proxy interface.
	// [1] https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidate
	// [2] https://wiki.mozilla.org/Media/WebRTC/Privacy
	// [3] https://github.com/zen-browser/desktop/issues/972
	//user_pref("media.peerconnection.ice.default_address_only", true);
	// PREF: force exclusion of private IPs from ICE candidates [FF51+]
	// [SETUP-HARDEN] This will protect your private IP even in TRUSTED scenarios after you
	// grant device access, but often results in breakage on video-conferencing platforms.
	//user_pref("media.peerconnection.ice.no_host", true);

Oh ok, is there a way to prevent websites from scanning your extensions then?