Reasoning with past to prove pkcs#11 keys secure

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 6561 LNCS, Issue , 2011, Pages 96-110

  Fröschle, Sibylle ^a   Sommer, Nils ^b  

^a UNIVERSITY OF OLDENBURG   (Germany)

^b MWR InfoSecurity   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

BACKWARDS ANALYSIS; FIRST-ORDER; FIRST-ORDER LANGUAGE; HARDWARE SECURITY; LINEAR TIME LOGIC; SECURITY API; SECURITY PROPERTIES;

SMART CARDS;

FORMAL LOGIC;

EID: 79952605484     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/978-3-642-19751-2_7     Document Type: Conference Paper

References (11)

1. http://csd.informatik.uni-oldenburg.de/~sib
2. Borgström, J.: Monotonicity for multiple key managment tokens (2009); presentation at ASA 2009
3. Castellini, C.: Automated Reasoning in Quantified Modal and Temporal Logic. Ph.D. thesis, University of Edinburgh (2004)
4. Clulow, J.: On the security of PKCS #11. In: Walter, C.D., Koç, Ç .K., Paar, C. (eds.) CHES 2003. LNCS, vol. 2779, pp. 411-425. Springer, Heidelberg (2003)
5. D'Agostino, M., Gabbay, D.M., Hähnle, R., Posegga, J.: Handbook of Tableau Methods. Kluwer Academic Publishers, Dordrecht (1999)
6. Delaune, S., Kremer, S., Steel, G.: Formal analysis of PKCS#11. In: CSF 2008, pp. 331-344. IEEE Computer Society Press, Los Alamitos (2008)
7. Fröschle, S., Steel, G.: Analysing PKCS#11 key management aPIs with unbounded fresh data. In: Degano, P., Vigaǹo, L. (eds.) ARSPA-WITS 2009. LNCS, vol. 5511, pp. 92-106. Springer, Heidelberg (2009)
8. Gabbay, D.M.: Labelled Deductive Systems, vol. 1. Oxford Science Publications (1996)
9. Kröger, F., Merz, S.: Temporal Logic and State Systems. Springer, Heidelberg (2008)
10. RSA Laboratories: PKCS#11: Cryptographic Token Interface Standard, vol. v2.30, Draft 4. RSA Security Inc. (July 2009)
11. Thayer, F.J.T., Herzog, J.C., Guttman, J.D.: Strand spaces: Why is a security protocol correct? In: IEEE Symposium on Security and Privacy, pp. 160-171 (1998)