2005
DOI: 10.1016/j.cose.2004.06.014
|View full text |Cite
|
Sign up to set email alerts
|

Keyjacking: the surprising insecurity of client-side SSL

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0

Year Published

2006
2006
2021
2021

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 20 publications
(13 citation statements)
references
References 4 publications
0
13
0
Order By: Relevance
“…The keyboard input information that is stored in the internal buffer uses the encoded key already received to encode in a block-encoding format. The control of the security input window directly reads in the keyboard input information from the keyboard security driver and uses it on the encoded key to provide it to an application program after a decoding process [8].…”
Section: Software Approachmentioning
confidence: 99%
“…The keyboard input information that is stored in the internal buffer uses the encoded key already received to encode in a block-encoding format. The control of the security input window directly reads in the keyboard input information from the keyboard security driver and uses it on the encoded key to provide it to an application program after a decoding process [8].…”
Section: Software Approachmentioning
confidence: 99%
“…RSA's SecureID [12] adds an additional factor of authentication, although deploying tokens may not be appropriate for all organizations. Smartcards and USB PKI tokens face similar cost and logistical challenges; moreover, a compromised workstation can take advantage of the access to the user's keypair, even with userand system-level controls in place [7]. Instead of reducing the size of the Trusted Computing Base (TCB) to fit a secure co-processing unit as in the SHEMP project [6], our work uses an external device (i.e.…”
Section: Related Workmentioning
confidence: 99%
“…Alice could use a PKI-equipped USB token-but this requires that W contain drivers for this token, and (what's worse) can expose Alice's key to malicious use by W [7].…”
Section: System Designmentioning
confidence: 99%
“…Indeed, the keyjacking work by Marchesini et al showed that keys stored on the Spyrus Rosetta USB token and the Aladdin eToken were vulnerable to attack through the Windows CryptoAPI (CAPI) system, which those devices use to enable the interface between the private key and applications on the workstation [11]. PKI devices such as these do not aid the user in making trust decisions, nor do they offer relying parties with a way to judge whether the private key may have been subjected to keyjacking by a malicious workstation.…”
Section: Prior Workmentioning
confidence: 99%
“…The keyjacking work of Marchesini et al showed that conditions #1 and #2 fail in situations satisfying #3 [11]. However, even if an enterprise solves the problem of securing a user's private keys at one standard machine, it is still necessary to make user PKI portable, and to accommodate the fact that not all machines in the enterprise will have the same level of trustworthiness.…”
Section: Introductionmentioning
confidence: 99%