Failed to build Chromium about oqs-demos HOT 15 CLOSED

Hi, this looks like liboqs did not get properly installed: Please check step 4 of the instructions carefully: maybe you did not set "<CHROMIUM_ROOT>" correctly for your setting? Maybe try running find . -name oqs.h to check the whereabouts of this OQS key include file in your chromium source tree.

from oqs-demos.

Hi we are getting a similar issue. We built liboqs successfully (as evident by the tests) and we noticed that the oqs folder is located in include folder of liboqs/build as well as liboqs.a inside liboqs/lib. Here is a picture of the paths:

Issue: when we go onto building by running autoninja -C out/Default chrome we get the following error:

admin1@dcs-quantum:~/chromium/src$ autoninja -C out/Default chrome
ninja: Entering directory `out/Default'
ninja: error: '../../third_party/boringssl/src/oqs/lib/liboqs.a', needed by 'obj/base/libbase.a', missing and no known rule to make it

Could I just move around the liboqs?

from oqs-demos.

@baentsch i guess the better question is, since moving around did seem to work until i just ran into another issue:

Where should I have put this build directory in order for me to successfully execute autoninja -C out/Default chrome

from oqs-demos.

@AndyChung1997 i am successfully building now and i re applied the oqs-mods patch. when you applied oqs-mods patch was it successful? I did some git force commands so hopefully all is correct but i was getting the error you mentioned above which seems to have gone away...

from oqs-demos.

@baentsch there is an issue with applying the patch it keeps saying the file is corrupt if you have any guidance on this

from oqs-demos.

Please share the steps that would allow reproduction of the issue (incl. trace of error message, ideally). Thanks.

from oqs-demos.

@AndyChung1997 i am successfully building now and i re applied the oqs-mods patch. when you applied oqs-mods patch was it successful? I did some git force commands so hopefully all is correct but i was getting the error you mentioned above which seems to have gone away...

@taylormadehdz Yes, I am successfully building now. I forgot to apply oqs-mods.patch last time. Thank you for your suggestion.

from oqs-demos.

Hi, this looks like liboqs did not get properly installed: Please check step 4 of the instructions carefully: maybe you did not set "<CHROMIUM_ROOT>" correctly for your setting? Maybe try running find . -name oqs.h to check the whereabouts of this OQS key include file in your chromium source tree.

@baentsch Thank you. I forgot to apply oqs-mods.patch last time. Now, my Chromium can work successfully. 😄

from oqs-demos.

@baentsch Hi, I want to verify that Chromium can perform a TLS 1.3 handshake using a post-quantum key-exchange. I navigate to the <CHROMIUM_ROOT>/third_party/boringssl/src folder, and build OQS-BoringSSL by running mkdir build && cd build && cmake -GNinja .. . Then the CLI shows No package 'libunwind-generic' found . Here is a picture of error message :

Will it cause an error in the next step if I ignore this error message?

Then, in the build directory, I run ./tool/bssl server -accept 4433 -www -loop -curves kyber512 . It tells me there is no such directory. Here is a picture of error message :

The previous instructions are executed successfully. How can I fix this issue?

from oqs-demos.

Will it cause an error in the next step if I ignore this error message?

This library unwind does not ring a bell to me. So you could try to continue without it (but you could also try to install it: What about running apt install libunwind-dev?). What you should do at the end of building oqs-boringssl is test it: run python3 oqs_scripts/try_handshake.py in the "<CHROMIUM_ROOT>/third_party/boringssl/src" folder: If you see a "Connected" in the output, that part works OK.

To the next question: If ./tool/bssl does not exist, the oqs-boringssl build failed for sure. Did you run ninja at all? Or did you only run cmake?

from oqs-demos.

Wow - I just see in our build instructions that the actual build command (ninja) is missing: I think, the full command should be mkdir build && cd build && cmake -GNinja .. && ninja. @xvzcf Do you agree? The main Chromium build does not take care of that, right?

from oqs-demos.

Will it cause an error in the next step if I ignore this error message?

This library unwind does not ring a bell to me. So you could try to continue without it (but you could also try to install it: What about running apt install libunwind-dev?). What you should do at the end of building oqs-boringssl is test it: run python3 oqs_scripts/try_handshake.py in the "<CHROMIUM_ROOT>/third_party/boringssl/src" folder: If you see a "Connected" in the output, that part works OK.

To the next question: If ./tool/bssl does not exist, the oqs-boringssl build failed for sure. Did you run ninja at all? Or did you only run cmake?

I ran ninja , and ./tool/bssl exists. When I used the newly built Chromium to access the OQS test server, the error message said NO_SHARED_GROUP . Here is a picture of error message :

Did I miss some steps?

from oqs-demos.

"NO_SHARED_GROUP" means exactly that: Server and client have no KEM algorithms (TLS1.3 groups) in common: You started the test server with "group" (or "curve" in the old terminology) kyber512 while Chromium only supports a small subset as per the documentation: Only these work --> Try starting bssl for example with group "p256_kyber90s512" and it should work.

from oqs-demos.

"NO_SHARED_GROUP" means exactly that: Server and client have no KEM algorithms (TLS1.3 groups) in common: You started the test server with "group" (or "curve" in the old terminology) kyber512 while Chromium only supports a small subset as per the documentation: Only these work --> Try starting bssl for example with group "p256_kyber90s512" and it should work.

@baentsch It can work. Thank you for your help. 😄

from oqs-demos.

UW. Closing issue accordingly.

from oqs-demos.