Journal article icon

Journal article

Verification Across Intellectual Property Boundaries.

Abstract:
In many industries, the share of software components provided by third-party suppliers is steadily increasing. As the suppliers seek to secure their intellectual property (IP) rights, the customer usually has no direct access to the suppliers' source code, and is able to enforce the use of verification tools only by legal requirements. In turn, the supplier has no means to convince the customer about successful verification without revealing the source code. This paper presents a new approach to resolve the conflict between the IP interests of the supplier and the quality interests of the customer. We introduce a protocol in which a dedicated server (called the "amanat") is controlled by both parties: the customer controls the verification task performed by the amanat, while the supplier controls the communication channels of the amanat to ensure that the amanat does not leak information about the source code. We argue that the protocol is both practically useful and mathematically sound. As the protocol is based on well-known (and relatively lightweight) cryptographic primitives, it allows a straightforward implementation on top of existing verification tool chains. To substantiate our security claims, we establish the correctness of the protocol by cryptographic reduction proofs. © Springer-Verlag Berlin Heidelberg 2007.
Publication status:
Published

Actions

Access Document

Publisher copy:
10.1007/978-3-540-73368-3_11

Authors

Contributors

Role:
Editor
Role:
Editor


Publisher:
Springer
Journal:
CAV More from this journal
Volume:
4590
Issue:
2
Pages:
82-94
Publication date:
2007-01-01
DOI:
EISSN:
1611-3349
ISSN:
1049-331X


Language:
English
Keywords:
Pubs id:
pubs:332662
UUID:
uuid:176b8c9c-c9c1-4f2c-ad23-2ed93ca22b05
Local pid:
pubs:332662
Source identifiers:
332662
Deposit date:
2012-12-19
ARK identifier:

Terms of use


Views and Downloads






If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP