Experience Report: How to Extract Security Protocols' Specifications from C Libraries

Sandoval, Itzel Vazquez; Lenzini, Gabriele

doi:10.1109/compsac.2018.10325

Cited by 2 publications

(1 citation statement)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Following the approach in [22], we executed the first step of the methodology proposed here in Sec. 2.1 by reverse engineering a fragment of the source code files.…”

Section: The P ≡ P Protocolmentioning

confidence: 99%

Emerging Technologies for Authorization and Authentication

2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

To send encrypted emails, users typically need to create and exchange keys which later should be manually authenticated, for instance, by comparing long strings of characters. These tasks are cumbersome for the average user. To make more accessible the use of encrypted email, a secure email application named p ≡ p automates the key management operations; p ≡ p still requires the users to carry out the verification, however, the authentication process is simple: users have to compare familiar words instead of strings of random characters, then the application shows the users what level of trust they have achieved via colored visual indicators. Yet, users may not execute the authentication ceremony as intended, p ≡ p's trust rating may be wrongly assigned, or both. To learn whether p ≡ p's trust ratings (and the corresponding visual indicators) are assigned consistently, we present a formal security analysis of p ≡ p's authentication ceremony. From the software implementation in C, we derive the specifications of an abstract protocol for public key distribution, encryption and trust establishment; then, we model the protocol in a variant of the applied pi calculus and later formally verify and validate specific privacy and authentication properties. We also discuss alternative research directions that could enrich the analysis.

show abstract

“…Following the approach in [22], we executed the first step of the methodology proposed here in Sec. 2.1 by reverse engineering a fragment of the source code files.…”

Section: The P ≡ P Protocolmentioning

confidence: 99%