MétaCan
Menu
Back to cohort
Record W2401830601

On "identities", "names", "NAMES", "ROLES" and Security: A Manifesto.

2011· preprint· en· W2401830601 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIACR Cryptology ePrint Archive · 2011
Typepreprint
Languageen
FieldComputer Science
TopicAdvanced Authentication Protocols Security
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsKey (lock)Identity (music)PseudonymManifestoInternet privacyConfusionComputer scienceThe InternetSession (web analytics)Computer securityPolitical scienceWorld Wide WebLawPsychology
DOInot available

Abstract

fetched live from OpenAlex

There is a great deal of confusion in the cryptology literature relating to various identity related issues. By “names” (lower case), we are referring to informal, personal ways that we indicate others; by “NAMES” (upper case) we are referring to official ways that we use to indicate others. Both of these concepts are often confused with “identity”, which is something else altogether, and with “ROLES”. These confusions can lead to insecurities in key exchange as well as in other internet activities that relate to identity. We discuss why we should not use names in protocols and why we cannot use identities. We discuss why, in a public-key infrastructure, we need to use NAMES in key-exchange protocols, and how they should be chosen and why they have to be unique, and why we should not use NAMES in session protocols. We also argue for the importance of secure ROLEs in key-exchange protocols.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Open science
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.357
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.000
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0030.008
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0000.001

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.017
GPT teacher head0.274
Teacher spread0.257 · 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