Can anyone explain please, whether WebRTC is a protocol or not? After reading this: http://www.webrtc.org/faq#TOC-Why-should-I-use-WebRTC- I thought it's just an API to enable other protocols (XMPP/Jingle, SIP etc.) to be built through JavaScript. Or is it a protocol after all?
WebRTC Copy – OTR and fast file transfers over WebRTC
21–28 of 28 posts
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#22Earlier quoted context omitted.
It looks like this is leaking the room name to Google Analytics. After thinking about this more, I'm going to go ahead and remove that. I should be able to monitor the server itself to make sure it isn't getting overloaded.
removed - https://github.com/erbbysam/webRTCCopy/commit/c1f35404414d63...
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#23Can anyone explain please, whether WebRTC is a protocol or not? After reading this: http://www.webrtc.org/faq#TOC-Why-should-I-use-WebRTC- I thought it's just an API to enable other protocols (XMPP/Jingle, SIP etc.) to be built through JavaScript. Or is it a protocol after all?
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#24Earlier quoted context omitted.
removed - https://github.com/erbbysam/webRTCCopy/commit/c1f35404414d63...
Are you hosting the site through Github Pages?
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#25Earlier quoted context omitted.
Does Google now have a log that I visited: https://rtccopy.com/#csFXmvXW And if somebody else had visited that same room, would they have a log of that too?
It looks like this is leaking the room name to Google Analytics. After thinking about this more, I'm going to go ahead and remove that. I should be able to monitor the server itself to make sure it isn't getting overloaded.
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#26The problem with sites like these are that you have to trust the site owner to not just add some javascript to the page which breaks the security of your conversation. Except this site is worse, because they also let their third party user tracking provider run arbitrary script on every page too. Nice as a demo of technology though.
If your concern is the security of 3rd party JS you should already be using NoSript/ScriptSafe [1]. Keep same-domain policy as safe and 3rd party domains blocked and opt-in only by default. The day-to-day UX experience of browsing the web is only minimally affected and significantly safer. Better than adblock. If your concern is the host operator, well obv can't circumvent that. Unless you use OSS chrome plugins and…
My concern was that he made the security/privacy worse than it needed to be, for other people, by including Google Analytics on the page.
He has now stated that he's seen that the room name is in fact being leaked to Google Analytics, and so has removed it. But even if he hadn't seen this, you still shouldn't include any third party hosted scripts on pages like these because you've no idea if/when they'll change in a manner which compromises security/privacy in future. No malicious intent required.
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#27Earlier quoted context omitted.
If your concern is the host operator, well obv can't circumvent that. Of course we can circumvent that. Make a plugin to alert the user whenever the JS changes.
What do you base your initial known good JS on though? What is the user supposed to do with the information that the JS has changed? A diff of minified JS isn't that helpful.
Re: WebRTC Copy – OTR and fast file transfers over WebRTC
#28The problem with sites like these are that you have to trust the site owner to not just add some javascript to the page which breaks the security of your conversation. Except this site is worse, because they also let their third party user tracking provider run arbitrary script on every page too. Nice as a demo of technology though.
The problem with sites like this is that readers such as mike-cardwell are not cool enough to download the sources themselves and host it where they trust it.
I wont be interested in running web based mail/chat clients until we get to a point where browsers have built in APIs that allow people to write trustable apps.