Re: Detecting incognito mode

Hi all,

We had a fun hackathon working on making a simple website that will detect
private browsing modes for FF, Safari and Chrome. The project seems to be
relevant in light of Chrome announcing that they will remove the ability to
use Filesystem API as a signal for Incognito Mode (which points to W3C TAG
doc):
https://www.blog.google/outreach-initiatives/google-news-initiative/protecting-private-browsing-chrome/

The website is at https://shivankaul.com/panoptibrowse/. Like I said, quite
simple, though Edward (CCed) has indicated interest in helping making it
look prettier and be more useful.

The project GitHub is at: https://github.com/ShivanKaul/panoptibrowse

Also taking suggestions for more inspired project names.

On Wed, Jun 26, 2019 at 2:36 AM Shivan Kaul Sahib <shivankaulsahib@gmail.com>
wrote:

> I signed up for a table at the IETF hackathon:
> https://trac.ietf.org/trac/ietf/meeting/wiki/105hackathon
>
> On Tue, Jun 18, 2019 at 1:25 PM Nataliia Bielova <
> nataliia.bielova@inria.fr> wrote:
>
>> Dear all,
>>
>> in the past we’ve done some research on browser fingerprinting by browser
>> extensions [1], and in particular we have looked into fingerprinting by
>> tracking protection extensions: AdBlock, Disconnect, Ghostery and Privacy
>> Badger. We analyzed the tradeoff between the privacy loss (how
>> fingerprintable users with such extensions are) and the level of protection
>> provided by these extensions — see Section 7 for more details.
>>
>> [1]
>> http://www-sop.inria.fr/members/Nataliia.Bielova/papers/Guly-etal-18-WPES.pdf
>>
>>
>> Best,
>> Nataliia
>>
>> ---
>> Nataliia Bielova
>> Researcher at Inria
>> http://www-sop.inria.fr/members/Nataliia.Bielova/
>> https://twitter.com/nataliabielova
>>
>> > On 18 Jun 2019, at 18:35, Pete Snyder <psnyder@brave.com> wrote:
>> >
>> > I’m currently not planning on being in Montreal, so sadly I won’t be
>> able to join you.  But there is a sig amount of research work in this area
>> (identifying / fingerprinting users based on their use of privacy tools,
>> and the privacy properties of private browsing modes).
>> >
>> > I know some of those papers have been shared on this mailing list
>> already, but I’d be happy to gather and (re)share some if it’d be helpful.
>> >
>> > Pete Snyder
>> > {pes,psnyder}@brave.com
>> > Brave Software
>> > Privacy Researcher
>> >
>> >> On Jun 18, 2019, at 5:14 AM, Samuel Weiler <weiler@w3.org> wrote:
>> >>
>> >> On 6/16/19 4:29 PM, Shivan Kaul Sahib wrote:
>> >>> Thanks Nick.
>> >>> A couple of IETFs ago at the f2f PING meeting, folks discussed
>> building a "Panopticlick <https://panopticlick.eff.org/> for Private
>> Browsing Mode" i.e. a web page that a user can navigate to while in
>> private-browsing mode and check if 1) they are detectable, 2) what
>> guarantees their browser provides them while in private-browsing (doesn't
>> retain cookies, etc). It would also be somewhat similar to the WebRTC Local
>> IP Address leak page we worked on last year (though I hope with prettier
>> UI/marketing): https://ntblk.github.io/webrtc-privacy/
>> >>> If there's interest and people are showing up for IETF next month in
>> Montreal, we could get a table at the hackathon, else async.
>> >>
>> >> That would amuse me, and I plan to be around.  Anyone else?
>> >>
>> >
>> >
>>
>>