While that would be "nice", it technically has nothing to do with the VPN service. Choice of operating system and software is what it's all about. It's up to the user to understand how to deal with their own software settings. But yeah, it wouldn't hurt.
@doaks, it would be nice addition, if there was a webRTC leak protection embedded within the private Internet access software. Is that something you guys would consider implementing in the future?
@doaks, it would be nice addition, if there was a webRTC leak protection embedded within the private Internet access software. Is that something you guys would consider implementing in the future?
Honestly, webRTC leaks are so easy to fix that I highly doubt there is a need to have it embedded natively within the Private Internet Access Software. In fact, because webRTC needs to be configured for the specific browser, I don't think it's a good idea to have that embedded in the software. Because doing so would mean that Private Internet Access would need to actively configure FireFox and Chrome.
Users usually don't like other software to configure their browsers without them knowing exactly what it is doing. So I'd say that if a user wants to disable the webRTC function, they should do it themselves. I'm with Tachy.G that there should be prominent documentation for it, but it should not be programmed into the PIA app itself.
Until the documentation is written, you'll find that it is extremely easy to disable webRTC. You can read how to do so at the bottom of this webpage:
https://www.ipleak.net/
Honestly, webRTC leaks are so easy to fix that I highly doubt there is a need to have it embedded natively within the Private Internet Access Software. In fact, because webRTC needs to be configured for the specific browser, I don't think it's a good idea to have that embedded in the software. Because doing so would mean that Private Internet Access would need to actively configure FireFox and Chrome. Users usually don't like other software to configure their browsers without them knowing exactly what it is doing. So I'd say that if a user wants to disable the webRTC function, they should do it themselves. I'm with Tachy.G that there should be prominent documentation for it, but it should not be programmed into the PIA app itself. Until the documentation is written, you'll find that it is extremely easy to disable webRTC. You can read how to do so at the bottom of this webpage: https://www.ipleak.net/
The whole reason I was asking for WebRTC Leak protection to be embedded in the software was because not a lot of individuals are aware of this browser vulnerability and therefore do not know how to protect against it. You can't protect yourself against something you don't know even exists. Which is why I think it would be beneficial for Private Internet Access too add WebRTC leak protection to their service.
Ahoy! I totally get that PIA might have a reason NOT to block WebRTC in its application... but I'm a little confused. My WebRTC wasn't showing when PIA was enabled since I signed up. A few days ago, though, all of a sudden my WebRTC is leaking (albeit a Private Use Address).
Does this have anything to do with PIA? Or did Chrome just update something that's now leaking my WebRTC? (using IPLeak to monitor)
Comments
Does this have anything to do with PIA? Or did Chrome just update something that's now leaking my WebRTC? (using IPLeak to monitor)