News for hackers. Stuff that matters.
Re:Screenshot URL tracking and niki-bot by forca on Wednesday August 13, 2014 @11:48AM (#8173434)
One word: webrtc

Can have security issues if not done correctly.

http://techpageone.dell.com/technology/open-source-webrtc-cr...

Re:Screenshot URL tracking and niki-bot by aroch on Wednesday August 13, 2014 @12:52PM (#8173827)
Uh, that entire article is FUD and bullshit.
Re:Screenshot URL tracking and niki-bot by forca on Wednesday August 13, 2014 @01:02PM (#8173893)
Care to elaborate on your claim? It's one thing to claim it's FUD, but yet another to refute it.
Re:Screenshot URL tracking and niki-bot by aroch on Wednesday August 13, 2014 @02:14PM (#8174236)
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

Re:Screenshot URL tracking and niki-bot by comex on Wednesday August 13, 2014 @03:13PM (#8174522)
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.
Re:Screenshot URL tracking and niki-bot by aroch on Wednesday August 13, 2014 @03:40PM (#8174653)
Yeah, I see how my wording is confusing. I've edited my post to use leaking instead of exposing