Re: [b2g] WebAPI Security Discussion: Camera API

2012-04-25 Thread Randell Jesup
I wrote: >There's also the "how" we do preview in a shader. Normally, for >streaming preview we'd use getUserMedia() (which is where we can hook >permissions, camera selection, etc) and take the MediaStream and feed it >to whatever (video elements, peerconnections, etc). I presented a slide >deck

Re: [b2g] WebAPI Security Discussion: Camera API

2012-04-25 Thread Randell Jesup
>Apps on other devices do get access to the preview to be able to do >things with it like providing effects. The proposal to use WebGL >shaders to modify the preview seems to ameliorate that issue in a way >that other platforms aren't using (which is good). An API to open the >preview that takes

Re: [b2g] WebAPI Security Discussion: Camera API

2012-04-25 Thread Jim Straus
Apps on other devices do get access to the preview to be able to do things with it like providing effects. The proposal to use WebGL shaders to modify the preview seems to ameliorate that issue in a way that other platforms aren't using (which is good). An API to open the preview that takes an

browser fingerprinting research

2012-04-25 Thread Ian Melven
Hi, some European researchers have been doing a project on user fingerprinting via the browser, including fingerprinting a user across multiple browsers. They also have created the Firegloves addon that attempts to minimize leaked data that can be used to fingerprint a user. Their study would

Re: WebAPI Security Discussion: Camera API

2012-04-25 Thread Jason Miller
> > This *is* a dangerous ability to give, though it's equivalent to what > users grant Skype or WebEx or Hangouts already by installing them > (perhaps less, actually). Agreed. App installation can never be free from danger. Regardless of any security restrictions, you are granting the app perm