Dear Dev,
My english problem again... If I wrote the third paragraph above as follows, it would be better understood:
"Now, to prevent security breaches caused by WebRTC, enabling only the second option below in the "Settings > Privacy and security" section does not work; we also need to enable the first option, which is not recommended below (For example, if you test the new Cent Browser on the site given by "Schanzation" above, you can see that the ip addresses are being leaked by WebRTC)
- "Disable WebRTC [NOT RECOMMENDED]"
- "Prevent my local IP addresses from leaking by WebRTC""
[I mean, it's not enough to just activate the original (2th) option for the problem in the new version (3.4.3.39). We also need to enable the other (1th) option that is not recommended; Whereas, there was no need to do this in the old stable version (3.2.4.23)]
I'm new to this site (https://whoer.net), but it's certainly far more successful than the site you're talking about in catching WebRTC's leak.
In other browsers the situation is as follows:
Chromium: There is no WebRTC leak in Chromium (If it is created as a WebRTC leak-free browser);
Vivaldi : " " " " " " Vivaldi (WebRTC is not allowed by default);
Opera : You should select the [i]Disable non-proxied UDP" option in the "Settings > Privacy & security > WebRTC" section;
Slimjet : The "Enable WebRTC" option should not be selected in the "Settings > Advanced > Privacy & security" section;
Kinza : You need to install an extension that prevents WebRTC's leak;
Yandex : " " " " " " " " " " .[/i]
My english problem again... If I wrote the third paragraph above as follows, it would be better understood:
"Now, to prevent security breaches caused by WebRTC, enabling only the second option below in the "Settings > Privacy and security" section does not work; we also need to enable the first option, which is not recommended below (For example, if you test the new Cent Browser on the site given by "Schanzation" above, you can see that the ip addresses are being leaked by WebRTC)
- "Disable WebRTC [NOT RECOMMENDED]"
- "Prevent my local IP addresses from leaking by WebRTC""
[I mean, it's not enough to just activate the original (2th) option for the problem in the new version (3.4.3.39). We also need to enable the other (1th) option that is not recommended; Whereas, there was no need to do this in the old stable version (3.2.4.23)]
I'm new to this site (https://whoer.net), but it's certainly far more successful than the site you're talking about in catching WebRTC's leak.
In other browsers the situation is as follows:
Chromium: There is no WebRTC leak in Chromium (If it is created as a WebRTC leak-free browser);
Vivaldi : " " " " " " Vivaldi (WebRTC is not allowed by default);
Opera : You should select the [i]Disable non-proxied UDP" option in the "Settings > Privacy & security > WebRTC" section;
Slimjet : The "Enable WebRTC" option should not be selected in the "Settings > Advanced > Privacy & security" section;
Kinza : You need to install an extension that prevents WebRTC's leak;
Yandex : " " " " " " " " " " .[/i]