Skip to main content Accessibility help
×
Hostname: page-component-8448b6f56d-qsmjn Total loading time: 0 Render date: 2024-04-24T14:46:29.524Z Has data issue: false hasContentIssue false

4 - Models

from Part I - Secure Multiparty Computation

Published online by Cambridge University Press:  05 August 2015

Ronald Cramer
Affiliation:
Stichting Centrum voor Wiskunde en Informatica (CWI), Amsterdam
Ivan Bjerre Damgård
Affiliation:
Aarhus Universitet, Denmark
Jesper Buus Nielsen
Affiliation:
Aarhus Universitet, Denmark
Get access

Summary

Introduction

The protocol we described in Chapter 3 is perfectly correct and perfectly private, but it cannot tolerate that any of the parties deviate from the protocol. In later chapters we will present protocols that are correct and private even if some parties do not follow the protocol. Such protocols are called robust. Before we can prove that these protocols are robust, we need a good definition of what we mean by that.

In this section we will describe a security model for cryptographic protocols known as the UC model. Here UC stands for universally composable. The name was adopted because a protocol proven secure in this model remains secure regardless of the context in which it is used. In other words, it can be “universally” composed with any set of other protocols. Our formulation of the UC model differs in several respects from the way it was originally formalized in the literature. We will hint at these differences as we go; some additional comments can be found in the Notes section of this chapter.

Before we look at the formal details, let us start by discussing the basic ideas of how to define privacy and robustness of a protocol and last, but not least, why and how these two concepts should be defined via one common definition because they are closely entangled.

Defining Privacy

It is convenient to first look back on how we defined privacy in Chapter 3. Informally, we defined a protocol to be private (against corruptions of size t) as follows: first, pick an input (x1,…,xn)for the protocol, and make a run of the protocol on this input. Then pick some C⊂{P1,…,Pn} with |C| ≤ t and consider the values {viewj}Pj∈C, where viewj is the view of party Pj in the execution. The values {viewj}PjCconstitute exactly the information leaked to the corrupted parties, C, during an execution. In the following we therefore call the values {viewj}PjC the leaked values.

We then want to say that the leaked values do not allow the corrupted parties to learn anything that they should not learn. It is clear that the corrupted parties necessarily must learn their own inputs and outputs; in fact, this is the entire purpose of the protocol. We therefore call the values {xj, yj}PjC the allowed values.

Type
Chapter
Information
Publisher: Cambridge University Press
Print publication year: 2015

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

  • Models
  • Ronald Cramer, Stichting Centrum voor Wiskunde en Informatica (CWI), Amsterdam, Ivan Bjerre Damgård, Aarhus Universitet, Denmark, Jesper Buus Nielsen, Aarhus Universitet, Denmark
  • Book: Secure Multiparty Computation and Secret Sharing
  • Online publication: 05 August 2015
  • Chapter DOI: https://doi.org/10.1017/CBO9781107337756.005
Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

  • Models
  • Ronald Cramer, Stichting Centrum voor Wiskunde en Informatica (CWI), Amsterdam, Ivan Bjerre Damgård, Aarhus Universitet, Denmark, Jesper Buus Nielsen, Aarhus Universitet, Denmark
  • Book: Secure Multiparty Computation and Secret Sharing
  • Online publication: 05 August 2015
  • Chapter DOI: https://doi.org/10.1017/CBO9781107337756.005
Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

  • Models
  • Ronald Cramer, Stichting Centrum voor Wiskunde en Informatica (CWI), Amsterdam, Ivan Bjerre Damgård, Aarhus Universitet, Denmark, Jesper Buus Nielsen, Aarhus Universitet, Denmark
  • Book: Secure Multiparty Computation and Secret Sharing
  • Online publication: 05 August 2015
  • Chapter DOI: https://doi.org/10.1017/CBO9781107337756.005
Available formats
×