PeerSig

Pilot phase: the relay runs on the same machine as this server and is operated by the same team, so for now it does not hide participants' network addresses from the study team. The other protections (blind tokens, counts only, randomized response, thresholds) apply in full.

PeerSig finds which applications send which TLS fingerprints (JA4). Volunteers run a small app that watches the start of the encrypted connections their computer makes and, once a week, contributes which applications sent which fingerprints, as anonymous ballots. The result is a public ground-truth table for traffic classification research.

Take part: get a code

Why a code? The collection only accepts ballots from enrolled participants, so that nobody can reach it uncontrolled from the internet and flood it with made-up results (spam). A code lets one computer send at most 512 anonymous ballots a week. It does not tell the server which ballots are yours: ballot tokens are signed blind, so a ballot cannot be traced back to the code that obtained it.

From the UCLouvain network

On campus or through the UCLouvain VPN: the server checks that your connection comes from the UCLouvain network and hands you a code, with nothing to fill in. It does not keep your network address.

By e-mail

The code is sent to this address. The server does not keep the address: it keeps a keyed hash of it, so that one address gets at most 3 codes (one per computer). Nothing links that hash to your code.

Then

  1. Install PeerSig from the releases page (macOS or Linux).
  2. Open it and enter your code. The addresses are filled in already; they should be:
    • Server: https://peersig.org
    • Relay: https://relay.peersig.org
  3. Each week, PeerSig shows you what it will send and waits a day before sending it.

Questions about the study: contact@peersig.org.

How data is protected

Current week: 0. Configuration. The full design is in docs/privacy.md.

Home · Released fingerprints · Source code