MétaCan
Menu
Back to cohort

Device-independent Tokens with Password Protection Against Token Stealing

2024· article· en· W4403937688 on OpenAlexaff
Preston Haffey, Reihaneh Safavi–Naini, Sabyasachi Dutta

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicUser Authentication and Security Systems
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsPasswordSecurity tokenComputer scienceComputer security

Abstract

fetched live from OpenAlex

Single Sign-On (SSO) systems permit an identity provider (IdP) to issue a token to an authenticated user that can be presented to a third party, referred to as the relying party (RP), for authentication and access. The RP will verify the IdP’s signature on the token and if valid, accepts the user’s identity claim. SSO systems are widely used because they allow the user to authenticate themself to different service providers using a single password. Basic tokens are not bound to the user’s identity and if stolen, allow the adversary to impersonate the user. Token stealing can be prevented by embedding the user’s public key in the token. This, however, requires using the corresponding private key, in a challenge-response protocol, that must be stored in the device’s secure element, effectively binding the token to the device(s) that store the private key.In this paper we propose a novel approach to token protection that removes both above shortcomings by using a password pwdvthat can be different from the authentication password. The user embeds a function of pwdvin the token during the token issuing, and token presentation requires the proof of knowledge of pwdv. The tokens, called Proof-of-Password (PoPwd) possession, can be used with any RP without prior password registration. We give a construction and prove its security against a powerful adversary that fully controls the network and has access to token generation and verification oracles. We also provide a proofof-concept implementation of PoPwd, and compare it with two other commonly used token systems, one with and one without protection against token stealing, that we implement, showing feasibility and advantages of our system in practice.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.008
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.009
Threshold uncertainty score0.030

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.008
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0020.002
Scholarly communication0.0030.007
Open science0.0040.008
Research integrity0.0030.003
Insufficient payload (model declined to judge)0.0090.008

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.025
GPT teacher head0.245
Teacher spread0.220 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicUser Authentication and Security SystemsFrench-language works237,207