Ok, so you have a bunch of executables and a table of pre-computed CRC's. No, you have a bunch of executables, and for each you have a crypto hash signed with a private key. You could store the public key in the secure rom, but this guy wants to use a smart card, presumably because he wants to be able to re-key. Of course the card and the secure hardware still have to share a key (or key pair) so they can mutually authenticate. *************************************************************** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***************************************************************
- Re: MUSCLE Disk encryption and more Jim Rees
- Re: MUSCLE Disk encryption and more mgraffam
- Re: MUSCLE Disk encryption and more Patrick Valsecchi
- Re: MUSCLE Disk encryption and more mgraffam
- Re: MUSCLE Disk encryption and more Jeremy Impson
- Re: MUSCLE Disk encryption and more Patrick Valsecchi
- Re: MUSCLE Disk encryption and more Jim Rees
- Re: MUSCLE Disk encryption and more Patrick Valsecchi
- Re: MUSCLE Disk encryption and more Eric Murray
- Re: MUSCLE Disk encryption and more Jim Rees
- Re: MUSCLE Disk encryption and more Jim Rees
- Re: MUSCLE Disk encryption and more Naomaru Itoi
- Re: MUSCLE Disk encryption and more mgraffam
- Re: MUSCLE Disk encryption and more Karl Katewu
- Re: MUSCLE Disk encryption and more Patrick Valsecchi
- Re: MUSCLE Disk encryption and more Dr S N Henson
- Re: MUSCLE Disk encryption and more Peter Tomlinson
- Re: MUSCLE Disk encryption and more Alex Russell