SOEMPI icon indicating copy to clipboard operation
SOEMPI copied to clipboard

Complete Two-third party CBF record linkage

Open MrCsabaToth opened this issue 11 years ago • 0 comments

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).

MrCsabaToth avatar Jul 05 '13 04:07 MrCsabaToth