Re: [docs-and-reports] Include FHE as an instantiation of private computation (#24)

> I want to be a little pedantic here about how we define things. When we talk about assumption related to security, these assumptions are cryptographic hardness assumptions (mathematical problems that have been studied for a long time) for MPC and assumptions for isolation, which come in so many different forms such as isolation at hardware level or software level).
> 
> I think the number of parties and the assumption of non-collusion is a different type of assumption. This is more about the architecture and the trust assumptions we want to make. Once we have chosen this architecture the question is how we define a protocol/technology that achieves our goal within this architecture and trust assumptions. In this sense I would like to distinguish these assumptions for the adversarial and trust model from the assumptions that underly the security properties of the protocols that are already assuming the chosen trust model.
>
> I agree with Erik that TEEs do not require multiple parties and actually that's the main way they are used - one party computes and we assume this party cannot peek in the computation. For the TEEs are not MPC, they are obfuscation - this a cryptographic primitive which has been defined and studies extensively (many impossibility results there), and has exactly the properties that TEEs aim to achieve.
>
> I am a bit unsure about putting FHE and MPC as different objects - MPC is the much broader notion, FHE can be viewed as a specific tool that give you an MPC protocol with minimal interaction, one party can do the computation on the encrypted data and then you need to have distributed decryption.

_Originally posted by @marianapr in https://github.com/patcg/docs-and-reports/pull/14#discussion_r999907062_

-- 
GitHub Notification of comment by eriktaubeneck
Please view or discuss this issue at https://github.com/patcg/docs-and-reports/issues/24#issuecomment-1287380417 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 21 October 2022 19:58:48 UTC