Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Luke Dickinson

dblp:205/2032 · DBLP profile ↗
← Back
5ranked-venue papers
1as first author
0since 2021 · last 2019
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 5 · 1 first-author

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
3 papers
Authentication and access control · 40% Usable security · 28% Network security · 21%
Software engineering, system software, and programming languages
1 paper
Operating systems · 100%

Topics — the 7 heaviest of 9, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Usable security
authentication usability
0.312018
A Tale of Two Studies: The Best and Worst of YubiKey Usability · IEEE Symposium on Security and Privacy 2018
Network security › secure communication › secure communication protocol
TLS
0.312018
The Secure Socket API: TLS as an Operating System Service · USENIX Security Symposium 2018
Authentication and access control › multi-factor authentication
two-factor authentication
0.312018
A Tale of Two Studies: The Best and Worst of YubiKey Usability · IEEE Symposium on Security and Privacy 2018
Authentication and access control › cryptographic authentication
certificate-based authentication
0.312017
TrustBase: An Architecture to Repair and Strengthen Certificate-based Authentication · USENIX Security Symposium 2017
Operating systems
network stack
0.112018
The Secure Socket API: TLS as an Operating System Service · USENIX Security Symposium 2018
Cryptographic protocols and secure computation › key management › public key infrastructure
certificate validation
0.112017
TrustBase: An Architecture to Repair and Strengthen Certificate-based Authentication · USENIX Security Symposium 2017
Cryptographic protocols and secure computation › key management
public key infrastructure
0.112017
TrustBase: An Architecture to Repair and Strengthen Certificate-based Authentication · USENIX Security Symposium 2017

Methods — techniques the papers use, named apart from their topics

API design · 0.7longitudinal study · 0.3laboratory study · 0.3architecture design · 0.3
YearPublicationVenuePosition
2019 Leveraging locality of reference for certificate revocation
abstract
X.509 certificate revocation defends against man-in-the-middle attacks involving a compromised certificate. Certificate revocation strategies face scalability, effectiveness, and deployment challenges as HTTPS adoption rates have soared. We propose Certificate Revocation Table (CRT), a new revocation strategy that is competitive with or exceeds alternative state-of-the-art solutions in effectiveness, efficiency, certificate growth scalability, mass revocation event scalability, revocation timeliness, privacy, and deployment requirements. The CRT design assumes that locality of reference applies to the certificates accessed by an organization. The CRT periodically checks the revocation status of X.509 certificates recently used by the organization. Pre-checking the revocation status of certificates the clients are likely to use avoids the security problems of on-demand certificate revocation checking.
Luke Dickinson, Trevor Smith 0002, Kent E. Seamons
ACSAC1
2019 A Usability Study of Four Secure Email Tools Using Paired Participants
abstract
Secure email is increasingly being touted as usable by novice users, with a push for adoption based on recent concerns about government surveillance. To determine whether secure email is ready for grassroots adoption, we employ a laboratory user study that recruits pairs of novice users to install and use several of the latest systems to exchange secure messages. We present both quantitative and qualitative results from 28 pairs of novices as they use Private WebMail (Pwm), Tutanota, and Virtru and 10 pairs of novices as they use Mailvelope. Participants report being more at ease with this type of study and better able to cope with mistakes since both participants are “on the same page.” We find that users prefer integrated solutions over depot-based solutions and that tutorials are important in helping first-time users. Finally, our results demonstrate that Pretty Good Privacy using manual key management is still unusable for novice users, with 9 of 10 participant pairs failing to complete the study.
Scott Ruoti, Jeff Andersen, Luke Dickinson, Scott Heidbrink, Tyler Monson, Mark O'Neill, Ken Reese, Brad Spendlove, Elham Vaziripour, Justin Wu, Daniel Zappala, Kent E. Seamons
ACM Trans. Priv. Secur.3
2018 A Tale of Two Studies: The Best and Worst of YubiKey Usability
abstract
Two-factor authentication (2FA) significantly improves the security of password-based authentication. Recently, there has been increased interest in Universal 2nd Factor (U2F) security keys-small hardware devices that require users to press a button on the security key to authenticate. To examine the usability of security keys in non-enterprise usage, we conducted two user studies of the YubiKey, a popular line of U2F security keys. The first study tasked 31 participants with configuring a Windows, Google, and Facebook account to authenticate using a YubiKey. This study revealed problems with setup instructions and workflow including users locking themselves out of their operating system or thinking they had successfully enabled 2FA when they had not. In contrast, the second study had 25 participants use a YubiKey in their daily lives over a period of four weeks, revealing that participants generally enjoyed the experience. Conducting both a laboratory and longitudinal study yielded insights into the usability of security keys that would not have been evident from either study in isolation. Based on our analysis, we recommend standardizing the setup process, enabling verification of success, allowing shared accounts, integrating with operating systems, and preventing lockouts.
Joshua Reynolds, Trevor Smith 0002, Ken Reese, Luke Dickinson, Scott Ruoti, Kent E. Seamons
IEEE Symposium on Security and Privacy4
2018 The Secure Socket API: TLS as an Operating System Service
Mark O'Neill, Scott Heidbrink, Jordan Whitehead, Tanner Perdue, Luke Dickinson, Torstein Collett, Nick Bonner, Kent E. Seamons, Daniel Zappala
USENIX Security Symposium5
2017 TrustBase: An Architecture to Repair and Strengthen Certificate-based Authentication
Mark O'Neill, Scott Heidbrink, Scott Ruoti, Jordan Whitehead, Dan Bunker, Luke Dickinson, Travis Hendershot, Joshua Reynolds, Kent E. Seamons, Daniel Zappala
USENIX Security Symposium6