full-disclosure - SmartCards programming...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <43848CD4.9000305@csuohio.edu>
Date: Wed Nov 23 15:39:05 2005
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: SmartCards programming...

> I bought 2 Goldcards (one of my teacher advised me to buy a such card to 
> do what I want... but I think a physical attack can allow someone to 
> copy the content of the card or the stored key when the authentication 
> is doing but to begin its perhaps the more simple card I can find ...)

Um .. that's exactly the problem smartcards attempt to address. It's 
highly unlikey you'll be able to copy the protected contents without 
resorting to a timing attack or the like (and that has been addressed 
lately as well).

If you're really patient, you could decapsulate the chip and read the 
eeprom contents with a microscope .. but that sort of defeats the 
purporse as you've destroyed the original.

As to your other question, a .hex file is just a binary image.

~Mike.