Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Two-third party CBF record linkage #5

Open
MrCsabaToth opened this issue Jul 5, 2013 · 0 comments
Open

Complete Two-third party CBF record linkage #5

MrCsabaToth opened this issue Jul 5, 2013 · 0 comments

Comments

@MrCsabaToth
Copy link
Owner

Right now Alice and Bob performs the bit shuffling needed for CBF encoding by performing a Diffie-Hellman Key exchange. The end result of that key exchange is the shared secret, which in this case is an integer number and is used as a seed for a pseudo random generator at both sides, thus ensuring exactly the same bit shuffling.

The message from both sides needed by the Diffie-Hellman protocol is piggy backed on the PersonMatchRequest entities, and exchanged as a part of the first phase record linkage of a three third party record linkage. So basically PAM (the parameter manager) helps exchanging the DH public keys as a MITM.

In order to perform a two third party CBF, Alice and Bob would need to perform the DH Key Exchange directly communicating with each other, prior to the final (and only in this case) record linkage. This will require some extra functions on the Remote EJB interface and synchronization/prioritization (Alice and Bob has to decide who controls the process).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant