News for hackers. Stuff that matters.
Re:Hello Firefox, this is Chrome calling by dbaupp on Monday February 04, 2013 @02:35PM (#5166500)
I feel like DataChannels are the best part of the WebRTC standard (or would be, if they were usable): a true p2p connection allowing transfer of arbitrary data without plugins or anything. This gives multiplayer games, file transfers, realtime chat and collaborative editors (let your imagination run wild...) and the only thing a server is required for is establishing the connection (and saving state). This functionality is much more exciting than simple video or audio chat.
Re:Hello Firefox, this is Chrome calling by FuzzyDunlop on Monday February 04, 2013 @02:39PM (#5166525)
I agree, and it's easy to tell just in the way you can describe it. The first thing video/audio chat brings to mind to anyone is 'Skype in the browser'. That's still cool and there is definitely more potential than that, but just having an arbitrary connection is a lot more open ended and exciting.
Re:Hello Firefox, this is Chrome calling by TazeTSchnitzel on Monday February 04, 2013 @04:36PM (#5167310)
This is what really excites me. I want to build a P2P DHT in the browser, basically see if I can implement something like Freenet entirely in JS.
Re:Hello Firefox, this is Chrome calling by pjscott on Monday February 04, 2013 @06:33PM (#5168003)
You might be interested in KadOH:

https://github.com/jinroh/kadoh

It's a JavaScript implementation of the Kademlia DHT. It doesn't support WebRTC as a transport yet, but they're working on it. The code looks pretty reasonable, and they seem to have some momentum going.

Re:Hello Firefox, this is Chrome calling by TazeTSchnitzel on Tuesday February 05, 2013 @10:17AM (#5171028)
Thanks! This looks really interesting.
Re:Hello Firefox, this is Chrome calling by est on Monday February 04, 2013 @07:30PM (#5168246)
Re:Hello Firefox, this is Chrome calling by comex on Monday February 04, 2013 @02:56PM (#5166654)
Unfortunately, if this page is accurate, DataChannels don't really work yet:

http://www.webrtc.org/chrome#TOC-Data-Channels-

A shame, because I have a use in mind for them. :)

Re:Hello Firefox, this is Chrome calling by pthatcherg on Monday February 04, 2013 @11:09PM (#5168976)
Firefox has as full DataChannel implementation (SCTP-based), while Chrome has a partial one (RTP-based). They don't interoperate yet. I implemented most of the partial implementation and am working on the full implementation now.

I'm glad that you're excited about them. I am too. I hope to have it ready for you soon :).

Re:Hello Firefox, this is Chrome calling by comex on Monday February 04, 2013 @11:15PM (#5169010)
Good to hear.

Out of curiosity - do you mean that you're writing a full SCTP-based implementation, or completing the RTP-based one? The standard draft specifies SCTP, right?

edit: this was addressed in another post.

Re:Hello Firefox, this is Chrome calling by phowat on Monday February 04, 2013 @03:14PM (#5166772)
It works on some alpha release of both Firefox and Chrome. There are already some file transfer apps if you're curious, although I haven't tested myself: https://github.com/lindstroem/FileTransfer and https://github.com/peer5/sharefest . Also, the folks from easyrtc ( https://github.com/priologic/easyrtc ) have already started working on adding DataChannels to their library.
Re:Hello Firefox, this is Chrome calling by tracker1 on Monday February 04, 2013 @03:27PM (#5166871)
A bit-torrent like client in the native browser would be interesting... wonder where Opera is on this one.
Re:Hello Firefox, this is Chrome calling by Torgo on Monday February 04, 2013 @05:41PM (#5167700)
I tried this less than a week ago on Linux platform and was unsuccessful. I am also waiting on this feature, want to do some cool stuff :-)
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Monday February 04, 2013 @08:45PM (#5168527)
They recently appeared behind an about:flags flag. :)
Re:Hello Firefox, this is Chrome calling by comex on Monday February 04, 2013 @08:50PM (#5168548)
Well, when I heard that WebRTC was in Chrome stable I thought this must surely include DataChannel, since it's simpler than a full-blown video stack. So although it being behind a flag is better news than it not being there at all, I was still pretty disappointed when I read that page :)

edit: also, I don't see it as an about:flags flag.

edit 2: I should just tunnel data through video then, what could possibly go wrong?

Re:Hello Firefox, this is Chrome calling by pthatcherg on Monday February 04, 2013 @11:13PM (#5168993)
It's not quite that simple. We (I work with the Chrome team) have an RTP-based data channel (sort of what you call "tunnel through the video" already in Chrome), but it provides no congestion control or reliability. To provide those, the IETF has proposed as the standard to use SCTP. Firefox has already integrated SCTP into their implementation, and we're working to get it into Chrome. So, you can start using the API now, but it'll get much better soon.
Re:Hello Firefox, this is Chrome calling by carterschonwald on Thursday February 07, 2013 @03:25PM (#5184303)
Sctp is a pretty cool protocol. I'm actually planning on including it as part of a user land network stack I'm slowly working on.
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Tuesday February 05, 2013 @08:02AM (#5170408)
Sorry, I forget not everyone is on the Dev channel, but I have this available:

Enable RTCDataChannel. Mac, Windows, Linux, Chrome OS, Android: Enable experimental RTCDataChannel for peer-to-peer data communications. Disable

Version 26.0.1397.2 dev

Re:Hello Firefox, this is Chrome calling by TylerE on Monday February 04, 2013 @03:08PM (#5166734)
What sort of security is in place - e.g. what's stopping a pop-up ad from logging keystrokes and sending them to a remote endpoint?
Re:Hello Firefox, this is Chrome calling by dbaupp on Monday February 04, 2013 @03:17PM (#5166798)
This is possible with current technology: $(document).keypress(sendKeypressInfo)
Re:Hello Firefox, this is Chrome calling by cj on Monday February 04, 2013 @05:16PM (#5167553)
$(document).keypress won't pick up keystrokes from across tabs or windows. So unless the popup is the active window, you should be safe from something like this.
Re:Hello Firefox, this is Chrome calling by est on Monday February 04, 2013 @07:29PM (#5168244)
Hmm, we are not talking about web page js here, we are talking about Chrome API js here. It's far more powerful.
Re:Hello Firefox, this is Chrome calling by TylerE on Monday February 04, 2013 @03:41PM (#5166964)
Won't the Same Origin Policy limit the exposure via ajax?
Re:Hello Firefox, this is Chrome calling by cousin_it on Monday February 04, 2013 @03:52PM (#5167038)
They don't have to use ajax. They can load an image with an arbitrary url and pass the keypress data in the url parameters, or dynamically create a script tag, or create an iframe and submit a form in it, etc. The script tag method also lets them get data back from the remote endpoint, if the remote endpoint is kind enough to encode it as JSONP.
Re:Hello Firefox, this is Chrome calling by marcusf on Monday February 04, 2013 @05:07PM (#5167490)
I think he's referring to a hostile script trying to bind to keydown -- usually you shove the banners in iframes to limit this possibility when you include external untrusted content. I assume the same holds true here, though.
Re:Hello Firefox, this is Chrome calling by ianb on Monday February 04, 2013 @05:55PM (#5167792)
The Same Origin Policy can be overridden by the site accepting the connection (http://www.w3.org/TR/cors/), so assuming that site is hosted by the attacker it wouldn't be helpful. If the site used (and the browser supported) a Content Security Policy (http://www.w3.org/TR/CSP/) you could restrict such outgoing connections.
Re:Hello Firefox, this is Chrome calling by navpatel on Monday February 04, 2013 @06:28PM (#5167979)
I don't think this is an issue. The popup would only capture whatever keystrokes are typed into the popup (as dbaupp illustrated). DataChannels doesn't change the boundaries within which a webpage/Javascript runs
Re:Hello Firefox, this is Chrome calling by jonknee on Monday February 04, 2013 @03:01PM (#5166687)
Hopefully DataConnections will also be used for video an audio so that encrypted connections can be used.
Re:Hello Firefox, this is Chrome calling by dbaupp on Monday February 04, 2013 @03:22PM (#5166828)
(Just so you don't copy my mistake, I was incorrect when I called them DataConnections, the term is DataChannel.)
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Monday February 04, 2013 @08:46PM (#5168528)
They already are. But sure, you could do that if you wanted.
Re:Hello Firefox, this is Chrome calling by pthatcherg on Monday February 04, 2013 @11:16PM (#5169017)
It's true that the audio, video, and data are all encrypted. But it's not the case that you can send audio and video over the data channel. Well, you could send audio and video data, but there's no way to pipe audio and video data into the data channel. That's an interesting idea, but it would probably take a long time to figure out and become part of the standard, if it ever happened at all. We'd probably need a worthwhile use case to justify it.
Re:Hello Firefox, this is Chrome calling by drivebyacct2 on Tuesday February 05, 2013 @08:04AM (#5170414)
My bad, I haven't played with this stuff in... jeez, nearly a year. I had a PoC with an signaling server written in Go, but it hasn't even been updated since the move from ROAP to JSEP and I haven't played with the compat js shim either...
Re:Hello Firefox, this is Chrome calling by account_taken on Monday February 04, 2013 @03:42PM (#5166974)
Yeah, let's start calling it web 4.0 now. Truly exciting stuff.