Re:Screenshot URL tracking and niki-bot
by aroch on Wednesday August 13, 2014 @09:19AM
(#8172707)
Disabling media.peerconnect does nothing to improve your anonymity. peerconnect (and, well, all websockets datachannels) requires user action to be enabled
[ Parent
| on HN ]
One word: webrtc
Can have security issues if not done correctly.
http://techpageone.dell.com/technology/open-source-webrtc-cr...
Uh, that entire article is FUD and bullshit.
Care to elaborate on your claim? It's one thing to claim it's FUD, but yet another to refute it.
The entire premise is that somehow hole punching is dangerous and unstoppable with webrtc. Enterprise grade NAT environments can easily deal with both STUN and TURN hole punching.
If leaking internal IP's from your network is a security risk, you need to reevaluate what you're calling "security".
None of the article's concerns are concerns to any competent sysamin
E: replaced 'exposing' to 'leaking' to avoid confusion
To clarify (because I misunderstood the meaning of the comment before clicking the link), the parent is referring to leaking the IP addresses themselves, not 'exposing' access to them.