So, snakeoil of the highest order, then. On 23 July 2014 18:16:51 GMT+01:00, John Preston <[email protected]> wrote: >You can find the results of my inquiry below. ¬_¬ > >-------- Forwarded Message -------- >> From: Art Matsak <[email protected]> >> To: John Preston <[email protected]> >> Subject: Re: Security specifics >> Date: Wed, 23 Jul 2014 18:34:28 +0200 >> >> Hi John, >> >> Thank you for your interest in Gruveo. Gruveo uses WebRTC, an open >technology for browser realtime communication. You can find details on >its security architecture here: >> >> http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-10 >> >> Please note that WebRTC is work in progress and its specifications >may change in the future. >> >> To answer your other questions, Gruveo is a proprietary product. >> >> Best regards, >> >> Art Matsak >> Founder and CEO >> Gruveo >> https://www.gruveo.com >> >> >> On 23 Jul 2014, at 18:19, John Preston <[email protected]> wrote: >> >> > From: John Preston <[email protected]> >> > Subject: Security specifics >> > >> > Message Body: >> > Hey all, >> > >> > Like the idea, but I'd like to know about the specifics of how >Gruveo is designed. Specifically: >> > * what is the threat model? >> > * what are the network protocol specifications? Packet formats, >ciphers and modes, and semantics all critically determine the security >of the system. >> > * who owns the IP, and how is it licensed? >> > * what's the development model like? >> > >> > Thanks for your time, :) >> > John >> > >> > -- >> > This mail is sent via contact form on Gruveo https://www.gruveo.com >> >
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
