W3C home > Mailing lists > Public > public-media-capture@w3.org > October 2015

RE: Comments/Questions on Media Capture Streams Privacy and Security Considerations

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Thu, 29 Oct 2015 07:08:01 -0000
To: "'Rigo Wenning'" <rigo@w3.org>, "'Eric Rescorla'" <ekr@rtfm.com>
Cc: "'Martin Thomson'" <martin.thomson@gmail.com>, "'public-privacy \(W3C mailing list\)'" <public-privacy@w3.org>, "'Mathieu Hofman'" <Mathieu.Hofman@citrix.com>, "'Harald Alvestrand'" <harald@alvestrand.no>, "'Nick Doty'" <npdoty@w3.org>, <public-media-capture@w3.org>
Message-ID: <632301d11218$8d4f13e0$a7ed3ba0$@baycloud.com>
Even when there is a visual indication people can miss it or not understand
what it is . Given the sensitivity of having a "hot" mike/camera, persistent
permissions should also have an expiry so even if people are unaware of them
they will not be there for perpetuity.

In general all permissions should have an expiry in my view, with the
duration reported when the permission is requested. (i.e. this should be
part of the permissions API, not just MediaCapture). Those that are less
sensitive may have a longer duration but MediaCapture should be relatively
short (hours?).


Mike



-----Original Message-----
From: Rigo Wenning [mailto:rigo@w3.org] 
Sent: 29 October 2015 06:52
To: Eric Rescorla <ekr@rtfm.com>
Cc: Martin Thomson <martin.thomson@gmail.com>; public-privacy (W3C mailing
list) <public-privacy@w3.org>; Mathieu Hofman <Mathieu.Hofman@citrix.com>;
Harald Alvestrand <harald@alvestrand.no>; Nick Doty <npdoty@w3.org>;
public-media-capture@w3.org
Subject: Re: Comments/Questions on Media Capture Streams  Privacy and
Security Considerations

On Thursday 29 October 2015 15:37:12 Eric Rescorla wrote:
> On Thu, Oct 29, 2015 at 3:35 PM, Rigo Wenning <rigo@w3.org> wrote:
> > On Thursday 29 October 2015 15:04:05 Eric Rescorla wrote:
> > > Chrome and Firefox do both of the two things listed in this quoted
block
> > > 
> > > 1. Inform the user that the devices are hot.
> > 
> > Ok, in this case I can understand that if one has a visual indication
that
> > mic
> > and camera are "on" the need for an additional prompt is somewhat moot.
> > 
> > > 2. Provide mechanisms for revoking consent.
> > 
> > This is then a question of usability. Is clicking on the visual
indication
> > allowing to revoke the consent/permission?
> 
> Yes, generally.

In this case, my earlier criticism was based on insufficient information. I 
think this does what it is supposed to do. I still think that persistent 
(forever) permissions are a mistake. But this is mitigated by the fact that 
the browser indicates when mic and camera are "on". 

 --Rigo
Received on Thursday, 29 October 2015 07:09:09 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 07:09:09 UTC