[Fiware-webui] Fwd: Executive summary of Privacy GE and link collection

[Philipp Slusallek]

Hi,

I was contacted by a new group in FIWARE that are offering privacy
preserving credencials as GEs within FIWARE (this is actually technology
from IBM where they will be polishing the API). This may be interesting
 for commenting on city data, POIs, or any other feature in our demos.

If this is interesting to you, please contact Stephan Neuhaus directly
(but keep me in CC, so I see if there is interest). He is especially
intreested in hearing how people would want to use the technology and
what would be good API features.


Best,

	Philipp


-------- Weitergeleitete Nachricht --------
Betreff: Executive summary of Privacy GE and link collection
Datum: Mon, 27 Oct 2014 17:47:21 +0100
Von: Stephan Neuhaus <stephan.neuhaus at zhaw.ch>
An: 'Philipp Slusallek' <philipp.slusallek at dfki.de>

Dear Prof Slusallek,

here is an executive summary of the Privacy GE.  If users of WebUI find
it interesting and would like to use it, they are in a position to shape
the service API; if they provide us with a sufficiently detailed use
case description, we will strive to make our API support their use case.
 If you know of a particularly good example, we could get in touch
directly with them.  I'm also available to come to Saarbrücken to give a
mini-seminar if that's needed.

Best regards,

Stephan Neuhaus

Links:

Codebase https://github.com/p2abcengine/p2abcengine
Concepts
https://github.com/p2abcengine/p2abcengine/wiki/Concepts-and-Features
Documentation https://github.com/p2abcengine/p2abcengine/wiki



FI-WARE Phase II Privacy GE Executive Summary
=============================================

The Privacy GE allows providers of services to use credentials that
are anonymous and yet allow the verification of attributes.  This
allows the service provider to verify only those attributes that are
absolutely needed for it to provide the service.  For example, a
provider of a virtual city tour might allow anonymous comments, but
only to those people who can prove that they are citizens.  Another
example is the verification of voting age where credential holders
can prove that they are above a certain age without having to reveal
their date of birth.

Our scheme knows five roles:

* The ISSUER issues privacy-preserving credentials.

* The REVOCATION AUTHORITY (optional) keeps track of credential
  revocation. Credentials may be revoked by the ISSUER (for example,
  they might have been used for fraud) or by the USER; see below (the
  credential may have been stolen or otherwise compromised).

* The VERIFIER controls access to aresource by taking
  privacy-preserving credentials and checking them for freshness (with
  the REVOCATION AUTHORITY) and correctness.

* The USER obtains credentials from an ISSUER and uses them with a
  VERIFIER.  With these credentials, USERs can create different
  pseudonyms for every interaction with a VERIFIER, and VERIFIERs will
  not be able to detect from those pseudonyms that these interactions
  are from the same USER. In fact, this is true even if the VERIFIER
  and the ISSUER collude.  When verifying a credential with a
  VERIFIER, that VERIFIER will say to the USER things like, "I need
  you to reveal attributes 'citizenship' and 'gender' to me, issued by
  'City of Helsinki'".  This is known as a presentation policy.  The
  USER then reveals the gender and citizenship attributes, but not,
  for example, the name or other personally identifying information.

* An INSPECTOR may, under certain circumstances, undo the privacy
  protection offered by the privacy-preserving credentials.  This
  might be necessary for example if it has been established that some
  credential has been used in a crime.  This part is totally optional
  and it is clear to the USER at the credential issuance stage that an
  INSPECTOR may be involved later. It is thus impossible to undo a
  USER's privacy without them being aware that this is potentially the
  case.


-- 

-------------------------------------------------------------------------
Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH
Trippstadter Strasse 122, D-67663 Kaiserslautern

Geschäftsführung:
  Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)
  Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats:
  Prof. Dr. h.c. Hans A. Aukes

Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.: DE 148646973, Steuernummer:  19/673/0060/3
---------------------------------------------------------------------------


-------------- next part --------------
A non-text attachment was scrubbed...
Name: philipp_slusallek.vcf
Type: text/x-vcard
Size: 441 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-webui/attachments/20141027/ef36892a/attachment.vcf>