run this repo just like libpsi？ about volepsi

[ladnir]

thats correct

[nihaoqingtuan]

But when I run the executable, only the test case shows pass, and using -help doesn't give command help like libpsi does.

[ladnir]

Take a look at main. Should be pretty self explanatory. There an example where protocol messages are manually passed between parties by writing the messages to files and having other other party read the file. This example demonstrates how to pass messaged if you don't want to use something like a network socket.

There is also the performance benchmark code that computes the running time. This uses a custom socket for communication that only works within a single program, ie no tcp/ip socket.

As previously mentioned, I will be adding another example with tls support over tcp/ip.

volepsi/frontend/main.cpp

Line 146 in 74404b7

int main(int argc, char** argv)

[nihaoqingtuan]

i get it. so i have to write it myself. thanks

[ladnir]

What are you trying to achieve?

[nihaoqingtuan]

I tried testing the performance metrics of this psi and I thought it would be as easy as testing using libpsi.

[ladnir]

It should be easy to get performance numbers. Call frontend with

-perf -psi

You can set the log2 of the set size using -nn 10. This would run the psi with 2^10 items per set. Here area few other parameters you can set. See here

volepsi/frontend/perf.cpp

Line 347 in 74404b7

auto n = 1ull << cmd.getOr("nn", 10);

[nihaoqingtuan]

i start to try it. And i want to know if the command of this library has help,just like libpsi.

[nihaoqingtuan]

i get it. This repo doesn't yet allow us to import data files ourselves like libpsi does. The project has not yet been implemented

[ladnir]

No, but could be added. Will be updating the code this weekend most likely.

[RindalVisa]

ok, you should be able to do everything you want now. There is a help section for frontend. You can do the PSI using a file as your set and you can now run everything over tls.

[RindalVisa]

git pull
python3 build.py -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON --clean

[nihaoqingtuan]

Is boost a third-party library that needs to be downloaded and installed like openssl?

[ladnir]

It's a third party library. The default behavior is to look for boost on the system and if not found then to automatically download it for you. Are you getting issues with boost?

[nihaoqingtuan]

i use "python3 build.py -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON",but it doesn't work.

[ladnir]

Did you use --clean?

[nihaoqingtuan]

CMake Error: Unknown argument --clean

[ladnir]

git pull
python3 build.py -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON --clean 

[ladnir]

What OS are you on?

[ladnir]

Assuming linux means Ubuntu sudo apt-get install openssl openssl-dev

[nihaoqingtuan]

i have downloaded openssl.

[nihaoqingtuan]

OpenSSL 3.0.5 5 Jul 2022 (Library: OpenSSL 3.0.5 5 Jul 2022)

[nihaoqingtuan]

maybe it's not openssl. I reloaded volepsi yesterday and there was no such thing, just a mistake at the beginning. After re-downloading and pulling again today, there is this problem.

i will try to delete all clean

[ladnir]

Should be as the readme says:

git clone https://github.com/Visa-Research/volepsi.git
cd volepsi
python3 build.py  -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON

the issue is that you are manually building libOTe with the wrong parameters.

[ladnir]

Please post the full output of

cd .\thirdparty\libOTe\thirdparty\coproto\
python3 .\build.py -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON

[ladnir]

From that folder (coproto), can you remove the out/ folder and rerun build.py and post the result.

I'm a bit confused about this error. It appears you have openssl but you can't linking the openssl library.

[ladnir]

And now cmake --build out/build/linux --verbose

[ladnir]

This seems a bit complicated.
The issue appears to be a conflict between the version of openssl being included and linked. It seems that the library is doing #include <openssl/ssl.h> and this is given a newer version of openssl compared to the one being linked /usr/lib64/libssl.so. Maybe you have multiple versions of openssl installed?

Can you add

    message("OPENSSL_INCLUDE_DIR=${OPENSSL_INCLUDE_DIR}")
    message("OPENSSL_SSL_LIBRARY=${OPENSSL_SSL_LIBRARY}")
    message("OPENSSL_LIBRARIES  =${OPENSSL_LIBRARIES}")
    message("OPENSSL_VERSION    =${OPENSSL_VERSION}")

to the end of .../coproto/cmake/coprotoFindDeps.cmake.

One test to see if you have an openssl version conflict would be to

mkdir /usr/lib64/temp
mv /usr/lib64/libssl.* /usr/lib64/temp/
mv /usr/lib64/libcrypto.* /usr/lib64/temp/

Later you can move these back if you want, i.e. mv /usr/lib64/temp/* /usr/lib64/. Then rebuild coproto.

rm -rf out/
cmake -S . -B out/build/linux/ -DCOPROTO_ENABLE_BOOST=ON -DCOPROTO_ENABLE_OPENSSL=ON
cmake --build out/build/linux --verbose

Post the output of this...

This will tell us if cmake can find some other version of openssl on your system, hopefully the same version that #include <openssl/ssl.h> is finding.

Alternatively, we could build openssl from source and directly use that version. That is a bit involved and havent needed to do that in the past.

[nihaoqingtuan]

i remember that linux has openssl and i also download new openssl.

[ladnir]

Can you Uninstaller the apt-get version?

[nihaoqingtuan]

my os uses yum

[ladnir]

Well not sure. You can try to Uninstaller your version of openssl. Or you can use a docker/contain/vm.

[nihaoqingtuan]

i will try again