=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
In the wise words of vuln@hexview.com, on Wednesday 04 August 2004 07:08:
> Clear text password exposure in Datakey's tokens and smartcards
[SNIP]
> Cause and Effect:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D
> The communication channel between the token and the driver is not
> encrypted. User's PIN can be retrieved using proxy driver or hardware
> sniffer.
Note that this is true for almost all card readers on the market, not only =
for=20
Datakey's. Having worked for companies using crypto smart cards, I have=20
conducted a few risk analysis about that. The conclusion has always been th=
at=20
if the PIN must be entered from a PC, and the attacker has means to install=
=20
software on the system (through directed viruses, social engineering, etc),=
=20
the game's over.
The only solution against that problem is to have the PIN entered using a=20
keypad on the reader. Only then does the cost of an attack raise=20
significantly. But that is opening another can of worms, because there is=20
(was?) no standard for card readers with attached pin pad (at the time,=20
PC/SCv2 wasn't finalised - is it?).
[SNIP]
Cheers,
Lionel
=2D --=20
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin
Lionel Ferette
BELNET CERT Coordinator
Rue de la Science 4 Tel: +32 2 7903385
1000 Brussels Fax: +32 2 7903375
Belgium PGP Key Id: 0x5662FD4B
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBEIYGDd3gqVZi/UsRAqEMAKDAISNaTuvH8eH37ER1wSO/zUq22gCgsG9W
PqY79HOMC3f+CWkUQXLPp1E=3D
=3Dk9PO
=2D----END PGP SIGNATURE-----

Likes:
![Re: [Full-Disclosure] Clear text password exposure in Datakey's tokens and smartcards](https://www.webhostingtalk.nl/images/WHT_rd/misc/dT.png)
Quote