Error running a segment of the code of OTExample about libscapi

[liorko87]

Hello,

The code required a config file:
ConfigFile cf(configFile);
What is the path you are passing to the function as configFile?

[andremmvgabriel]

Hello, and thanks for answering.

I have the config file in the same folder as the cpp file. So, after compiling the cpp, I run the code with the command line:

./exe_oblivious_transfer 1 "test_oblivious_transfer_config.txt"

Since both files are in the same folder, I'm assuming that I can specify its path with only its name "test_oblivious_transfer_config.txt"

Let me check what happens if I specify all the path to it.

[andremmvgabriel]

Yes, the same error occurs when I specify the entire path to the config file.

[liorko87]

The error come from this line at your code:
auto dlog = make_shared<OpenSSLDlogECF2m>();
The error message comes from this line at libscapi, and does not related to your OT file.

When you are using this object, it relies that a file called: ../include/configFiles/NISTEC.txt exists.

[andremmvgabriel]

Hmm, I've suspected also that because in the libscapi documentation, in the "Quickstart" tab, you have a sample code with the following line:

DlogGroup* dlog = new OpenSSLDlogECF2m("include/configFiles/NISTEC.txt", "K-233");

Where the path to the NISTEC file is specified. So should the error be fixed if I change the line that is giving an error as following?

auto dlog = make_shared<OpenSSLDlogECF2m>("path_to_NISTEC.txt", "K-233");

[liorko87]

Yes, it should work.

[andremmvgabriel]

Okay, so I've changed the error line to:

auto dlog = make_shared<OpenSSLDlogECF2m>("../../../../libscapi/include/configFiles/NISTEC.txt", "K-233");

The error about the const char* was solved indeed! Thanks!
However, now there is another issue showing in the console, which is:

terminate called after throwing an instance of 'std::invalid_argument'
what():  x, y values are not a point on this curve

This happens in the line: output.g0 = dlog->generateElement(false, point);
Is this error because of the "K-233" specified previously?

[liorko87]

I tried to run your code with K-163 and it works fine.

[andremmvgabriel]

Perfect! Works fine now!

Thank you for all the help you have provided.