Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Identity coherence: combine claim-vs-measurement checks into one observation

Aperta
  • Qualcosa non va?
#98 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, javascript, nodejs, python
Ambito
backend, security

Direzione di ricerca

This is a tracking issue for an observe-only identity-coherence-v1 observation under experimental.observations; the payload names no source files. Start from the existing WebGL and font axes shipped in v1.42.0 and the linked issues #92, #93 and #94. Done means the open JS engine and TLS family axes report agree, contradict or unknown, and the acceptance checks pass identically across the three servers. Ask a maintainer before starting, because the axes are design-heavy.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement go javascript python

Consolidates #92, #93 and #94 into one detection.

Each compares what the browser claims to be (User-Agent, platform) with one measured property. They are combined into a single identity-coherence-v1 experimental observation, where each measurement is one axis that reports agree, contradict or unknown. Unknown never counts.

It is observe-only: it is reported under experimental.observations and never changes the production score, token issuance, rate limits or any existing FCAPTCHA_EXPERIMENTAL_BLOCKING policy. Any future enforcement would be a new, separately named policy.

Axes

  • Claim model and OS axes: WebGL graphics backend (from #93) and font set. Shipped in v1.42.0.
  • JS engine axis (from #92): derive Blink/Gecko/WebKit from the math/error fingerprints plus cheap client probes.
  • TLS family axis (from #94): classify a natively computed or trusted-proxy JA4 into chromium/gecko/webkit from structural traits. Never uses client-supplied JA3.

Acceptance (carried over)

  • Honest Chrome, Edge, Firefox and Safari on desktop and mobile never contradict their claim, and the bench personas stay within budget.
  • Every iOS browser runs WebKit, so CriOS/FxiOS with a WebKit engine or TLS hello is honest.
  • A TLS-intercepting proxy classifies as unknown, not as a mismatch, and how is documented.
  • Synthetic contradicting vectors fire identically in all three servers.

Canvas readback stability (#95) is tracked separately.

Lingua principale
JavaScript
Stelle
221
Fork
23
Merge medio
18h 50m
PR unite (30g)
42

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di WebDecoy/FCaptcha

Tutte le issue di WebDecoy/FCaptcha

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.