Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-soc
Navigation:
Lists: gentoo-soc: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-soc@g.o
From: Fabian Groffen <grobian@g.o>
Subject: Re: About "Create and release a Gentoo stats server/client"
Date: Thu, 2 Apr 2009 18:58:26 +0200
On 02-04-2009 17:50:50 +0200, Sebastian Pipping wrote:
> Fabian Groffen wrote:
> > Is it really necessary to associate collected information to personal
> > data at all?
> 
> Are you referring to item
> 
>   * Add user's real name and contact info if wanted
> 
> ? That's completely optional.  I expect some people to
> be willing to share their contact info, especially in the
> beginning.  It's not "needed" in any way.  Does that answer
> your question?

I was wondering if this was necessary at all, and hence if you should
include it.

> >  What if there would be a unique identifier (hashed MAC
> > address?) that just identifies the Gentoo installation, would that be
> > enough?  That way you can track without any privacy issues involved, I
> > think.
> 
> We could use such an identifier to identify repeated submissions
> (users should send in more up to date again later) and handle
> some kind of "database pollution" attacks.  We wouldn't catch
> attackers that change their MAC before submission.

I actually assumed that "updates" are one of the most important
happenings of a system like this.  Updates actually allow you to see
when and how people update, what the effect of an GSLA is, usage
patterns, etc. etc.

DoS attacks are different problem, but most probably can easily be
solved by infra using some rate-limiting.  Poisoning attacks are again a
different thing, but perhaps not so important because their impact is
low, and when detected easily remedied (restart from scratch, restore
backup ...)

> I suppose a privacy issue still exists as you might be able to
> resolve certain changes in submission data over time down
> to a person.  I better not construct scenarios here, but I'm
> afraid that would be possible.

So, question, is dealing with the privacy via identity problem one that
gives you any extra benefits, or can you entirely let it go?


-- 
Fabian Groffen
Gentoo on a different level


Replies:
Gentoo stats gathering vs. privacy protection (was Re: About "Create and release a Gentoo stats server/client")
-- Sebastian Pipping
References:
About "Create and release a Gentoo stats server/client"
-- Sebastian Pipping
Re: About "Create and release a Gentoo stats server/client"
-- Sebastian Pipping
Re: About "Create and release a Gentoo stats server/client"
-- Fabian Groffen
Re: About "Create and release a Gentoo stats server/client"
-- Sebastian Pipping
Navigation:
Lists: gentoo-soc: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: About "Create and release a Gentoo stats server/client"
Next by thread:
Gentoo stats gathering vs. privacy protection (was Re: About "Create and release a Gentoo stats server/client")
Previous by date:
Re: About "Create and release a Gentoo stats server/client"
Next by date:
Re: About "Create and release a Gentoo stats server/client"


Updated Jun 17, 2009

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.