06.11.2014 Views

A User Centric Security Model for Tamper-Resistant Devices

A User Centric Security Model for Tamper-Resistant Devices

A User Centric Security Model for Tamper-Resistant Devices

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6.6 Analysis of the Proposed Protocols<br />

securely communicate with each other. One exception to this is the STCP SC . The SC generates<br />

the Die-Hellman exponential be<strong>for</strong>e the SP but it does not reveal the values until<br />

it receives the Die-Hellman exponential from the SP. In this way, they satisfy requirements<br />

SOG-3 to SOG-5 and SOG-12 like the other two STCPs; because generating the<br />

Die-Hellman exponential be<strong>for</strong>e SP is not a problem as long as it is not revealed to the SP.<br />

All communicating parties in the STCPs use the generated session keys to securely communicate<br />

with each other, which gives an implicit mutual key conrmation, satisfying the<br />

SOG-6.<br />

In the STCPs, session keys generated in one session have no link with the session keys<br />

generated in other sessions, even when a session is established between the same entities.<br />

This enables the protocol to provide resilience against the known-key security (SOG-7).<br />

This unlinkability of session keys is because each entity not only generates a new Die-<br />

Hellman exponential but also a random number, both of which are used during the STCP<br />

to generate new session keys. There<strong>for</strong>e, even if an adversary A nds out about the<br />

exponentials and random numbers of a session, it would not enable him to generate past<br />

or future session keys.<br />

Furthermore, to provide unknown key share resilience (SOG8) the STCPs include the<br />

Die-Hellman exponentials and random numbers along with identities of individual entities<br />

in a message (e.g. hs and hp) that is then signed by all communicating entities. There<strong>for</strong>e,<br />

the receiving entity can then ascertain the identity of the entity with which it has shared<br />

the key by verifying the signature and parameters used to generate the session keys (e.g.<br />

Die-Hellman exponentials and random numbers).<br />

The STCPs can be considered KCI-resilient (SOG9) protocols, as the protection against<br />

the KCI is based on the digital signatures. In addition, the cryptographic certicates of<br />

each signature key include its association with a particular SP or smart card. There<strong>for</strong>e, if<br />

A has the knowledge of the signature key of a smart card (or an SP) then it can masquerade<br />

the smart card to other entities but not other entities to the smart card. Another point to<br />

note is that during the STCPs, all signed messages and certicates are encrypted using the<br />

session key. This facilitates the STCPs in meeting the requirements SOG-8 and SOG-9,<br />

as an adversary cannot substitute the certicate or signature.<br />

The STCPs also meet the perfect <strong>for</strong>ward secrecy (SOG10) by making the key generation<br />

process independent of any long-term keys. The session keys are generated using fresh<br />

values of Die-Hellman exponentials and random numbers, regardless of the long-term<br />

keys like the smart card, user, and SP signature keys. There<strong>for</strong>e, even if A nds out the<br />

signature key of any entity, this knowledge will not enable him to nd out past session<br />

keys.<br />

147

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!