2

I am trying to implement a chatroulette-sque app, and WebRTC seems to be the best choice as far implementing something that doesn't take a vast amount of server resources. My current scheme is to create a WebSocket connection to my server to be able to establish a connection between two random hosts. However the downside of that is that I am forced to exchange their details. Is the most potentially harmful data that is being shared an IP address? and if so what could the IP be used for? or are there bigger things I need to worry about?

Improve this question
1
  • 2
    Note that leaking IP Address also leaks your location, which is fine if you're chatting with someone you know, but may be problematic if you are chatting with strangers and could be used to personally identify you if you have static IP Address so it may become a privacy issue.
    – Lie Ryan
    Commented Apr 19, 2016 at 0:23

1 Answer 1

Reset to default
1

In terms of IP address leakage you might want to see How bad is the leaking of Internal IP addresses through external DNS.

Nowadays, WebRTC works only on HTTPS and you should also use WebSockets on wss instead of ws. And I guess this way you should be fine.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .