The site can't provide a secure connection: https://localhost:4433 about oqs-demos HOT 9 CLOSED

Hi @yogitagolhani - great to see you kept working on this. When you say

I am able to successfully rin the TLS connection in boringssl

do you mean to have done a successful command-line (BoringSSL) TLS-interaction with your test server? Could you show a dump of that, please?

Another idea coming to my mind when seeing what you're trying to do, could you try another KEX than 'oqs_kem_default', say 'frodo640aes' (just in case the liboqs default algorithm is not the same)? In any case, I'm sure @xvzcf has more and better ideas, too.

from oqs-demos.

from oqs-demos.

Hi @yogitagolhani, can you pass the -curves p256_frodo640aes option to bssl server and then try to connect to it using Chromium?

from oqs-demos.

Hi,
I had passed the curves values but still no luck. i have attached the error logs.
Open browser.txt

pass curves.txt

from oqs-demos.

Hello Team,
Any idea on the issue? Also when i ran the command git apply BUILD.gn.patch it says unrecognized input though i am able to run the next command succssefully.

from oqs-demos.

Have you checked out the correct Chromium commit (i.e tag 85.0.4161.2)? You should also make sure to apply the patch and re-generate the BoringSSL GN build files before building Chromium.

from oqs-demos.

Hello Team,

The chromium version is correct and we followed the same steos as mentioned in the document. But no luck :(

from oqs-demos.

Hello Team,
Any idea on the issue? Also when i ran the command git apply BUILD.gn.patch it says unrecognized input though i am able to run the next command succssefully.

@yogitagolhani Sorry in the delay answering: I now went through the whole process myself and the above shows that you did not properly apply the patch correctly: You need to be in CHROMIUM_ROOT (/src) and apply the patch there e.g. like this git apply /home/parallels/git/oqs-demos/chromium/BUILD.gn.patch. Without applying this patch successfully/without error message, you do not get QSC algorithm support added to your build (but the build succeeds -- until you try using a QSC algorithm). This then explains all your problems. So: Be sure to apply the patch without error:

Check that the string "oqs" appears in the file CHROMIUM_ROOT/third_party/boringssl/BUILD.gn, e.g., by running grep oqs third_party/boringssl/BUILD.gn: If this command generates no output, OQS code is not being compiled into your chromium executable.

Another way to check that OQS has been properly compiled into chromium is by checking the symbols of the library libboringssl.so used by chromium, e.g., as such nm chromium/src/out/Default/libboringssl.so | grep oqs: Again, no output means your chromium will not be able to successfully run QSC.

from oqs-demos.

Closing this issue. If the problem persists, please reopen.

from oqs-demos.