EDBT 2026 Demo / reviewers in the wild / expert
Anish Athayle
dblp:184/6066
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Network and information security
1 paper |
Authentication and access control · 50% Usable security · 50% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Authentication and access control
password authentication |
0.2 | 1 | 2016 | pASSWORD tYPOS and How to Correct Them Securely · IEEE Symposium on Security and Privacy 2016 |
Usable security
password usability |
0.2 | 1 | 2016 | pASSWORD tYPOS and How to Correct Them Securely · IEEE Symposium on Security and Privacy 2016 |
Methods — techniques the papers use, named apart from their topics
user study · 0.2security analysis · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | pASSWORD tYPOS and How to Correct Them SecurelyabstractWe provide the first treatment of typo-tolerant password authentication for arbitrary user-selected passwords. Such a system, rather than simply rejecting a login attempt with an incorrect password, tries to correct common typographical errors on behalf of the user. Limited forms of typo-tolerance have been used in some industry settings, but to date there has been no analysis of the utility and security of such schemes. We quantify the kinds and rates of typos made by users via studies conducted on Amazon Mechanical Turk and via instrumentation of the production login infrastructure at Dropbox. The instrumentation at Dropbox did not record user passwords or otherwise change authentication policy, but recorded only the frequency of observed typos. Our experiments reveal that almost 10% of login attempts fail due to a handful of simple, easily correctable typos, such as capitalization errors. We show that correcting just a few of these typos would reduce login delays for a significant fraction of users as well as enable an additional 3% of users to achieve successful login. We introduce a framework for reasoning about typo-tolerance, and investigate the seemingly inherent tension here between security and usability of passwords. We use our framework to show that there exist typo-tolerant authentication schemes that can get corrections for "free": we prove they are as secure as schemes that always reject mistyped passwords. Building off this theory, we detail a variety of practical strategies for securely implementing typo-tolerance. Rahul Chatterjee 0001, Anish Athayle, Devdatta Akhawe, Ari Juels, Thomas Ristenpart |
IEEE Symposium on Security and Privacy | 2 |