In 2016 the WebRTC bug is still exposes user's private IP information
It is now 2016. Why isn't the WebRTC privacy bug fixed in Chrome? How long can VPN users expect for their private information to be accessible when using the Chrome browser using the STUN based attack? This fault in WebRTC exposes the private LAN IP information and actual IP address of users utilising a VPN service.