Rebecca Chang Swee Fun 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
..
base 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
patches 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
src 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
.clang-format 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
BUILD.gn 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
DEPS 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
DIR_METADATA 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
LICENSE 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
OWNERS 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago
README.chromium 213e2ca447 Publish chromium based on 102.0.5005.115 1 year ago

README.chromium

Name: PSM (Private Set Membership) client side
URL: None
Version: 24-Feb-2022
License: Apache Version 2.0
License File: LICENSE
Security Critical: yes

Description:

Private Set Membership (PSM) is a cryptographic protocol that
allows users to privately query whether the user's identifier is a
member of a set of identifiers held by a server in a
privacy-preserving manner.

For privacy, the Private Set Membership protocol guarantees the
following:
- The server does not learn any information about the sensitive
portion of the user's queried identifier. In particular, this also
means that the server does not learn whether the queried
identifier was a member or not.
- The querying user learns no information about the set of
identifiers that are stored by the server beyond whether the
querying user's identifier is a member or not of the server-held
set of identifiers. In other words, the querying user learns the
bare minimum amount of information which is only the answer of the
membership query.

Local Modifications:

Applying local modifications live in //third_party/private_membership/patches/
can be done by running the following commands:

$ export PSM_CLIENT_PATH=/src/third_party/private_membership/patches
$ for patch in $PSM_CLIENT_PATH/patches/*; do patch -s -p1 < $patch; done

In case of conflict, update those patches accordingly and save them back in
//third_party/private_membership/patches/.