From af477c715965e6808bc1f218aa02a4d1b6c22120 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Wed, 11 Oct 2023 07:38:56 +0200 Subject: [PATCH 1/4] document limited Chromium support level --- README.md | 6 ++++-- chromium/README-Linux.md | 4 +++- chromium/README.md | 6 ++++-- chromium/scripts/README | 2 +- nginx/fulltest-provider/genconfig.py | 22 +++++++++++++--------- 5 files changed, 25 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 974c6ab2..d4fa17a3 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,8 @@ Currently supported packages: | **curl** | [Github: oqs-demos/curl](curl) | [Dockerhub: openquantumsafe/curl](https://hub.docker.com/repository/docker/openquantumsafe/curl) | | **Apache httpd** | [Github: oqs-demos/httpd](httpd) | [Dockerhub: openquantumsafe/httpd](https://hub.docker.com/repository/docker/openquantumsafe/httpd) | | **nginx** | [Github: oqs-demos/nginx](nginx) | [Dockerhub: openquantumsafe/nginx](https://hub.docker.com/repository/docker/openquantumsafe/nginx) | -| **Chromium** | [Github: oqs-demos/chromium](chromium) | [Binary for Ubuntu 20](https://github.com/open-quantum-safe/oqs-demos/releases/download/0.7.2/chromium-ubuntu-0.7.2.tgz) | + + | **OpenSSH** | [Github: oqs-demos/openssh](openssh) | [Dockerhub: openquantumsafe/openssh](https://hub.docker.com/repository/docker/openquantumsafe/openssh) | | **Wireshark** | [Github: oqs-demos/wireshark](wireshark) | [Dockerhub: openquantumsafe/wireshark](https://hub.docker.com/repository/docker/openquantumsafe/wireshark) | | **Epiphany** | [Github: oqs-demos/epiphany](epiphany) | [Dockerhub: openquantumsafe/epiphany](https://hub.docker.com/repository/docker/openquantumsafe/epiphany) | @@ -32,7 +33,8 @@ Currently supported packages: -You can use the openssl (s_client), curl and GNOME Web/epiphany clients with all algorithm combinations available at the Open Quantum Safe TLS/X.509 interoperability test server at https://test.openquantumsafe.org (set up using `oqs-provider v0.5.0` and `liboqs v0.8.0`). Chromium and `oqs-boringssl` are no longer maintained to the same set of algorithms, so are not to be expected to (inter)operate fully with the test server. +You can use the openssl (s_client), curl and GNOME Web/epiphany clients with all algorithm combinations available at the Open Quantum Safe TLS/X.509 interoperability test server at https://test.openquantumsafe.org (set up using `oqs-provider v0.5.0` and `liboqs v0.8.0`). + ## Contributing diff --git a/chromium/README-Linux.md b/chromium/README-Linux.md index f4782757..92aaa957 100644 --- a/chromium/README-Linux.md +++ b/chromium/README-Linux.md @@ -1,3 +1,5 @@ +** WARNING: THESE INSTRUCTIONS ARE OUTDATED. CONTRIBUTIONS WELCOME TO BRING THIS TO THE LATEST UP- AND DOWNSTREAM CODE LEVEL ** + Note that both cloning the source code as well as building Chromium can take several hours if you do not have excellent network connectivity and serious multicore CPUs at your disposal: The download has a size of over 40GB and even a size-and-performance optimized build (see note below) takes 1143 CPU user minutes on a 2.6GHz i7 CPU, i.e. something like 300 minutes or 5 hours on a quad-core system. 0. Ensure the system requirements listed [here](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#System-requirements) are met. @@ -64,4 +66,4 @@ If all steps outlined above have been successfully executed, one can extract a s ### Automated build scripts As the instructions above are complex and hard to get right the first time, a set of build scripts is included in the -scripts subdirectory. Please read scripts/README for more information on how to use them. \ No newline at end of file +scripts subdirectory. Please read scripts/README for more information on how to use them. diff --git a/chromium/README.md b/chromium/README.md index 89767667..a150dbeb 100644 --- a/chromium/README.md +++ b/chromium/README.md @@ -1,7 +1,9 @@ -This directory contains instructions and corresponding patches to build the Chromium web browser using the [OQS-BoringSSL fork](https://github.com/open-quantum-safe/boringssl), thereby enabling Chromium to use quantum-safe key exchange algorithms. Note that these instructions have been tested only on Windows 10, Ubuntu 18, 19, and 20 (x86_64) installations and apply at present only to a subset of quantum-safe key-exchanges as [documented here](https://github.com/open-quantum-safe/boringssl#key-exchange). +This directory contains no longer fully maintained instructions and corresponding patches to build the Chromium web browser using the [OQS-BoringSSL fork](https://github.com/open-quantum-safe/boringssl), thereby enabling Chromium to use quantum-safe key exchange algorithms. Note that these instructions have been tested only on Windows 10 installations and apply at present only to a subset of quantum-safe key-exchanges as [documented here](https://github.com/open-quantum-safe/boringssl#key-exchange). + +Please note that the Linux instructions are outdated and do not allow proper operation of a PQ-Chromium variant. The information is solely retained for people accepting this limitation. This limitation by no means should be understood as a preference for proprietary operating systems by the OQS team: Our focus remains on the support of open source software -- but we do not have the bandwidth to keep supporting the Chromium and BoringSSL PQ software stack at the same level as we did in the past. We welcome contributions and contributors allowing us to change this; most welcome would be contributions to bring up the Linux instructions and [patch](oqs-changes.patch) to the latest up- and downstream code level. --- -[Build Instructions for Linux](README-Linux.md) +[Outdated Build Instructions for Linux](README-Linux.md) [Build Instructions for Windows](README-Windows.md) diff --git a/chromium/scripts/README b/chromium/scripts/README index 156fd72f..f3624d45 100644 --- a/chromium/scripts/README +++ b/chromium/scripts/README @@ -1,5 +1,5 @@ These scripts help facilitate a build of PQC-enabled Chromium. -They have been tested on Ubuntu 20.04 . +They had been tested on Ubuntu 20.04 **BUT NO LONGER ARE MAINTAINED**. How to use : diff --git a/nginx/fulltest-provider/genconfig.py b/nginx/fulltest-provider/genconfig.py index c03b5e4c..d8d327eb 100644 --- a/nginx/fulltest-provider/genconfig.py +++ b/nginx/fulltest-provider/genconfig.py @@ -117,8 +117,9 @@ def write_nginx_config(f, i, cf, port, _sig, k): # deactivate if you don't like tables: i.write(""+sig+""+k+""+str(port)+""+sig+"/"+k+"\n") - if k in chromium_algs and not ("_" in sig and (sig.startswith("p") or (sig.startswith("rsa")))): - cf.write(""+sig+""+k+""+str(port)+""+sig+"/"+k+"\n") + # chromium support discontinued + #if k in chromium_algs and not ("_" in sig and (sig.startswith("p") or (sig.startswith("rsa")))): + # cf.write(""+sig+""+k+""+str(port)+""+sig+"/"+k+"\n") # generates nginx config @@ -126,14 +127,17 @@ def gen_conf(filename, indexbasefilename, chromiumfilename): port = STARTPORT assignments={} i = open(indexbasefilename, "w") - cf = open(chromiumfilename, "w") + # chromium support discontinued + cf = None + #cf = open(chromiumfilename, "w") # copy baseline templates with open(TEMPLATE_FILE, "r") as tf: for line in tf: i.write(line) - with open(CHROMIUM_TEMPLATE_FILE, "r") as ctf: - for line in ctf: - cf.write(line) + #chromium support discontinued + #with open(CHROMIUM_TEMPLATE_FILE, "r") as ctf: + # for line in ctf: + # cf.write(line) with open(filename, "w") as f: # baseline config @@ -193,9 +197,9 @@ def gen_conf(filename, indexbasefilename, chromiumfilename): i.write("\n") i.write("\n") i.close() - cf.write("\n") - cf.write("\n") - cf.close() + #cf.write("\n") + #cf.write("\n") + #cf.close() with open(ASSIGNMENT_FILE, 'w') as outfile: json.dump(assignments, outfile) From 9b200c8c84d37aa34484784bf1c931d18c8406f8 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Wed, 11 Oct 2023 07:42:18 +0200 Subject: [PATCH 2/4] correct table formatting --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index d4fa17a3..86cbb41b 100644 --- a/README.md +++ b/README.md @@ -17,8 +17,6 @@ Currently supported packages: | **curl** | [Github: oqs-demos/curl](curl) | [Dockerhub: openquantumsafe/curl](https://hub.docker.com/repository/docker/openquantumsafe/curl) | | **Apache httpd** | [Github: oqs-demos/httpd](httpd) | [Dockerhub: openquantumsafe/httpd](https://hub.docker.com/repository/docker/openquantumsafe/httpd) | | **nginx** | [Github: oqs-demos/nginx](nginx) | [Dockerhub: openquantumsafe/nginx](https://hub.docker.com/repository/docker/openquantumsafe/nginx) | - - | **OpenSSH** | [Github: oqs-demos/openssh](openssh) | [Dockerhub: openquantumsafe/openssh](https://hub.docker.com/repository/docker/openquantumsafe/openssh) | | **Wireshark** | [Github: oqs-demos/wireshark](wireshark) | [Dockerhub: openquantumsafe/wireshark](https://hub.docker.com/repository/docker/openquantumsafe/wireshark) | | **Epiphany** | [Github: oqs-demos/epiphany](epiphany) | [Dockerhub: openquantumsafe/epiphany](https://hub.docker.com/repository/docker/openquantumsafe/epiphany) | @@ -32,6 +30,7 @@ Currently supported packages: | **h2load** | [Github: oqs-demos/h2load](h2load) | [ Dockerhub: openquantumsafe/h2load](https://hub.docker.com/repository/docker/openquantumsafe/h2load) | + You can use the openssl (s_client), curl and GNOME Web/epiphany clients with all algorithm combinations available at the Open Quantum Safe TLS/X.509 interoperability test server at https://test.openquantumsafe.org (set up using `oqs-provider v0.5.0` and `liboqs v0.8.0`). From fc1a5450a49d3bbe07ca574c23eb880846b6df61 Mon Sep 17 00:00:00 2001 From: Raytonne <86047362+Raytonne@users.noreply.github.com> Date: Wed, 11 Oct 2023 00:48:50 -0500 Subject: [PATCH 3/4] Update Linux instructions --- chromium/README-Linux.md | 553 ++++++++++++++++++++++++++++++++++++--- 1 file changed, 510 insertions(+), 43 deletions(-) diff --git a/chromium/README-Linux.md b/chromium/README-Linux.md index 92aaa957..b63e613e 100644 --- a/chromium/README-Linux.md +++ b/chromium/README-Linux.md @@ -1,69 +1,536 @@ -** WARNING: THESE INSTRUCTIONS ARE OUTDATED. CONTRIBUTIONS WELCOME TO BRING THIS TO THE LATEST UP- AND DOWNSTREAM CODE LEVEL ** +# Instructions for Building Chromium on Linux -Note that both cloning the source code as well as building Chromium can take several hours if you do not have excellent network connectivity and serious multicore CPUs at your disposal: The download has a size of over 40GB and even a size-and-performance optimized build (see note below) takes 1143 CPU user minutes on a 2.6GHz i7 CPU, i.e. something like 300 minutes or 5 hours on a quad-core system. +### 1. Obtain the Chromium Source Code -0. Ensure the system requirements listed [here](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#System-requirements) are met. +Please read [Google's instructions](https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md) carefully, then complete every step before **Setting up the build**. -1. To obtain the source code, follow the instructions given [here](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#Install) in the "Install depot_tools" section and in the "Get the code" section up to (and not including) the "Install additional build dependencies" sub-section. Note: Do *not* set `--no-history` to save time as you need git history in the next step. +The rest of the instructions will use **$CHROMIUM_ROOT** to refer to the root directory of the Chromium source code. -2. Navigate to the root directory of the source code, which we will refer to hereafter as ``, and run `git checkout 100.0.4856.2`, which is the latest tag for which we have verified the build instructions. Then, to ensure that all of chromium's third party dependencies are compatible with this tag, run `gclient sync`. +### 2. Install Go and Perl -*Note*: Depending on the OS version installed, you may have to install python2, e.g., using `sudo apt install -y python2`, and ensure it's set as the system default, e.g., via `sudo ln -s /usr/bin/python2 /usr/bin/python`. +### 3. Switch to the OQS-BoringSSL -3. Navigate to `/third_party/boringssl/src`, and switch the BoringSSL source code to the OQS-BoringSSL fork by running the following commands: +```shellscript +cd $CHROMIUM_ROOT/third_party/boringssl/src +git remote add oqs-bssl https://github.com/open-quantum-safe/boringssl +git fetch oqs-bssl +git checkout -b oqs-bssl-master oqs-bssl/master +``` -- `git remote add oqs-bssl https://github.com/open-quantum-safe/boringssl` -- `git fetch oqs-bssl` -- `git checkout -b oqs-bssl-master e2d2587065eacfe97aaae940dd43cd964b71f5b4` +### 4. Clone and Build liboqs -4. In a directory of your choosing, clone and build liboqs as follows: +Choose a directory to store the liboqs source code and use the `cd` command to move to that directory. We will use ninja to build liboqs. -- `git clone --branch main https://github.com/open-quantum-safe/liboqs.git` -- `cd liboqs && mkdir build && cd build` -- `cmake .. -G"Ninja" -DCMAKE_INSTALL_PREFIX=/third_party/boringssl/src/oqs -DOQS_USE_OPENSSL=OFF` -- `ninja && ninja install` +```shellscript +git clone --branch main https://github.com/open-quantum-safe/liboqs.git +cd liboqs && mkdir build && cd build +cmake .. -G"Ninja" -DCMAKE_INSTALL_PREFIX=$CHROMIUM_ROOT/third_party/boringssl/src/oqs -DOQS_USE_OPENSSL=OFF +ninja && ninja install +``` -Note: You might have to install `ninja` if not already done, e.g., by running `sudo apt-get install ninja`. You also might want to run `SKIP_TESTS=doxygen,style ninja run_tests` to validate liboqs operating OK on your machine. For this you need to install `pytest` if not already present on your machine, e.g., by running `sudo apt-get install python3-pytest python3-pytest-xdist` first. +### 5. Enable Quantum-Safe Crypto -Note: If you want to execute the resulting binaries on another machine, be sure to also pass [-DOQS_DIST_BUILD=ON](https://github.com/open-quantum-safe/liboqs/wiki/Customizing-liboqs#oqs_dist_build) to the `cmake` command above to obtain code running on all machines of the same architecture type. +* Open _$CHROMIUM_ROOT/third_party/boringssl/BUILD.gn_. + * Find `config("external_config")`, then modify `include_dirs` + ```diff + config("external_config") { + -include_dirs = [ "src/include" ] + +include_dirs = [ "src/include", "src/oqs/include" ] + if (is_component_build) { + ``` + * Find `all_headers = crypto_headers + ssl_headers` and replace it with the following line + ```diff + all_sources = crypto_sources + ssl_sources + -all_headers = crypto_headers + ssl_headers + +all_headers = crypto_headers + ssl_headers + oqs_headers + + if (enable_rust_boringssl) { + ``` + * Find `component("boringssl")`, then add the following line after `friend = [ ":*" ]` + ```diff + public = all_headers + friend = [ ":*" ] + +libs = [ "//third_party/boringssl/src/oqs/lib/liboqs.a" ] + deps = [ "//third_party/boringssl/src/third_party/fiat:fiat_license" ] + ``` +* Open _$CHROMIUM_ROOT/net/quic/quic_stream_factory.cc_. + * Find `if (quic_stream_factory_->ssl_config_service_->GetSSLContextConfig()`, then modify `config_.set_preferred_groups` + ```diff + if (quic_stream_factory_->ssl_config_service_->GetSSLContextConfig() + .PostQuantumKeyAgreementEnabled()) { + - config_.set_preferred_groups({SSL_GROUP_X25519_KYBER768_DRAFT00, + + config_.set_preferred_groups({SSL_GROUP_KYBER512, SSL_GROUP_KYBER768, SSL_GROUP_KYBER1024, + + SSL_GROUP_HQC128, SSL_GROUP_HQC192, SSL_GROUP_HQC256, + + SSL_GROUP_BIKEL1, SSL_GROUP_BIKEL3, + + SSL_GROUP_FRODO640AES, SSL_GROUP_FRODO640SHAKE, SSL_GROUP_FRODO976AES, SSL_GROUP_FRODO976SHAKE, SSL_GROUP_FRODO1344AES, SSL_GROUP_FRODO1344SHAKE, + + SSL_GROUP_X25519_KYBER768_DRAFT00, + + SSL_GROUP_P256_KYBER512, SSL_GROUP_P384_KYBER768, SSL_GROUP_P521_KYBER1024, + + SSL_GROUP_P256_HQC128, SSL_GROUP_P384_HQC192, SSL_GROUP_P521_HQC256, + + SSL_GROUP_P256_BIKEL1, SSL_GROUP_P384_BIKEL3, + + SSL_GROUP_P256_FRODO640AES, SSL_GROUP_P256_FRODO640SHAKE, SSL_GROUP_P384_FRODO976AES, SSL_GROUP_P384_FRODO976SHAKE, SSL_GROUP_P521_FRODO1344AES, SSL_GROUP_P521_FRODO1344SHAKE, + SSL_GROUP_X25519, SSL_GROUP_SECP256R1, + SSL_GROUP_SECP384R1}); + } + ``` +* Open _$CHROMIUM_ROOT/net/socket/ssl_client_socket_impl.cc_. + * Find `if (context_->config().PostQuantumKeyAgreementEnabled()) {`, then modify `kCurves` + ```diff + if (context_->config().PostQuantumKeyAgreementEnabled()) { + - static const int kCurves[] = {NID_X25519Kyber768Draft00, NID_X25519, + - NID_X9_62_prime256v1, NID_secp384r1}; + + static const int kCurves[] = {NID_kyber512, NID_kyber768, NID_kyber1024, + + NID_hqc128, NID_hqc192, NID_hqc256, + + NID_bikel1, NID_bikel3, + + NID_p256_kyber512, NID_p384_kyber768, NID_p521_kyber1024, + + NID_p256_hqc128, NID_p384_hqc192, NID_p521_hqc256, + + NID_p256_bikel1, NID_p384_bikel3, + + NID_X25519Kyber768Draft00, NID_frodo640aes, NID_frodo640shake, NID_frodo976aes, NID_frodo976shake, NID_frodo1344aes, NID_frodo1344shake, + + NID_p256_frodo640aes, NID_p256_frodo640shake, NID_p384_frodo976aes, NID_p384_frodo976shake, NID_p521_frodo1344aes, NID_p521_frodo1344shake, + + NID_X25519, NID_X9_62_prime256v1, NID_secp384r1}; + if (!SSL_set1_curves(ssl_.get(), kCurves, std::size(kCurves))) { + return ERR_UNEXPECTED; + ``` + * Find `if (ssl_config_.disable_sha1_server_signatures) {`, then insert following lines after `SSL_SIGN_RSA_PSS_RSAE_SHA512, SSL_SIGN_RSA_PKCS1_SHA512,` + ```diff + SSL_SIGN_RSA_PSS_RSAE_SHA384, SSL_SIGN_RSA_PKCS1_SHA384, + SSL_SIGN_RSA_PSS_RSAE_SHA512, SSL_SIGN_RSA_PKCS1_SHA512, + + SSL_SIGN_DILITHIUM2, SSL_SIGN_DILITHIUM3, SSL_SIGN_DILITHIUM5, + + SSL_SIGN_FALCON512, SSL_SIGN_FALCON1024, + + SSL_SIGN_SPHINCSSHA2128FSIMPLE, SSL_SIGN_SPHINCSSHA2128SSIMPLE, SSL_SIGN_SPHINCSSHA2192FSIMPLE, SSL_SIGN_SPHINCSSHA2192SSIMPLE, SSL_SIGN_SPHINCSSHA2256FSIMPLE, SSL_SIGN_SPHINCSSHA2256SSIMPLE, + + SSL_SIGN_SPHINCSSHAKE128FSIMPLE, SSL_SIGN_SPHINCSSHAKE128SSIMPLE, SSL_SIGN_SPHINCSSHAKE192FSIMPLE, SSL_SIGN_SPHINCSSHAKE192SSIMPLE, SSL_SIGN_SPHINCSSHAKE256FSIMPLE, SSL_SIGN_SPHINCSSHAKE256SSIMPLE, + }; + if (!SSL_set_verify_algorithm_prefs(ssl_.get(), kVerifyPrefs, + ``` +* Open _$CHROMIUM_ROOT/net/cert/cert_verify_proc.cc_. + * Find `const char* CertTypeToString(X509Certificate::PublicKeyType cert_type) {`, then insert following lines after `return "ECDH";` + ```diff + case X509Certificate::kPublicKeyTypeECDH: + return "ECDH"; + + case X509Certificate::kPublicKeyTypeDilithium: + + return "Dilithium"; + + case X509Certificate::kPublicKeyTypeFalcon: + + return "Falcon"; + + case X509Certificate::kPublicKeyTypeSPHINCSSHA2: + + return "SPHINCSSHA2"; + + case X509Certificate::kPublicKeyTypeSPHINCSSHAKE: + + return "SPHINCSSHAKE"; + } + NOTREACHED(); + ``` + * Find `switch (*cert_algorithm) {`, then insert following lines after `case SignatureAlgorithm::kRsaPssSha512:` + ```diff + case SignatureAlgorithm::kRsaPssSha384: + case SignatureAlgorithm::kRsaPssSha512: + + case SignatureAlgorithm::kDilithium2: + + case SignatureAlgorithm::kDilithium3: + + case SignatureAlgorithm::kDilithium5: + + case SignatureAlgorithm::kFalcon512: + + case SignatureAlgorithm::kFalcon1024: + + case SignatureAlgorithm::kSPHINCSSHA2128fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2128ssimple: + + case SignatureAlgorithm::kSPHINCSSHA2192fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2192ssimple: + + case SignatureAlgorithm::kSPHINCSSHA2256fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2256ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE128fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE128ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE192fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE192ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE256fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE256ssimple: + return true; + } + ``` +* Open _$CHROMIUM_ROOT/net/cert/x509_certificate.cc_. + * Find `switch (EVP_PKEY_id(pkey.get())) {`, then insert following case statements + ```diff + case EVP_PKEY_DH: + *type = kPublicKeyTypeDH; + break; + + case EVP_PKEY_DILITHIUM2: + + case EVP_PKEY_DILITHIUM3: + + case EVP_PKEY_DILITHIUM5: + + *type = kPublicKeyTypeDilithium; + + break; + + case EVP_PKEY_FALCON512: + + case EVP_PKEY_FALCON1024: + + *type = kPublicKeyTypeFalcon; + + break; + + case EVP_PKEY_SPHINCSSHA2128FSIMPLE: + + case EVP_PKEY_SPHINCSSHA2128SSIMPLE: + + case EVP_PKEY_SPHINCSSHA2192FSIMPLE: + + case EVP_PKEY_SPHINCSSHA2192SSIMPLE: + + case EVP_PKEY_SPHINCSSHA2256FSIMPLE: + + case EVP_PKEY_SPHINCSSHA2256SSIMPLE: + + *type = kPublicKeyTypeSPHINCSSHA2; + + break; + + case EVP_PKEY_SPHINCSSHAKE128FSIMPLE: + + case EVP_PKEY_SPHINCSSHAKE128SSIMPLE: + + case EVP_PKEY_SPHINCSSHAKE192FSIMPLE: + + case EVP_PKEY_SPHINCSSHAKE192SSIMPLE: + + case EVP_PKEY_SPHINCSSHAKE256FSIMPLE: + + case EVP_PKEY_SPHINCSSHAKE256SSIMPLE: + + *type = kPublicKeyTypeSPHINCSSHAKE; + + break; + } + *size_bits = base::saturated_cast(EVP_PKEY_bits(pkey.get())); + ``` +* Open _$CHROMIUM_ROOT/net/cert/x509_certificate.h_. + * Find `enum PublicKeyType {`, then insert following lines before `kPublicKeyTypeECDH` + ```diff + kPublicKeyTypeECDSA, + kPublicKeyTypeDH, + + kPublicKeyTypeDilithium, + + kPublicKeyTypeFalcon, + + kPublicKeyTypeSPHINCSSHA2, + + kPublicKeyTypeSPHINCSSHAKE, + kPublicKeyTypeECDH + }; + ``` +* Open _$CHROMIUM_ROOT/net/cert/pki/signature_algorithm.cc_. + * Find `[[nodiscard]] bool IsEmpty(const der::Input& input) {`, then insert following lines before it + ```diff + const uint8_t kOidMgf1[] = {0x2a, 0x86, 0x48, 0x86, 0xf7, + 0x0d, 0x01, 0x01, 0x08}; -5. After successfully installing liboqs as per the above, navigate to `` and apply the `oqs-changes.patch` file provided here by running `git apply `. Then, navigate to `third_party/boringssl`, and run `python src/util/generate_build_files.py gn`. + +const uint8_t kOidDilithium2[] = {0x2b, 0x06, 0x01, 0x04, 0x01, 0x02, 0x82, 0x0b, 0x07, 0x04, 0x04}; + +const uint8_t kOidDilithium3[] = {0x2b, 0x06, 0x01, 0x04, 0x01, 0x02, 0x82, 0x0b, 0x07, 0x06, 0x05}; + +const uint8_t kOidDilithium5[] = {0x2b, 0x06, 0x01, 0x04, 0x01, 0x02, 0x82, 0x0b, 0x07, 0x08, 0x07}; + +const uint8_t kOidFalcon512[] = {0x2b, 0xce, 0x0f, 0x03, 0x06}; + +const uint8_t kOidFalcon1024[] = {0x2b, 0xce, 0x0f, 0x03, 0x09}; + +const uint8_t kOidSPHINCSSHA2128fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x04, 0x0d}; + +const uint8_t kOidSPHINCSSHA2128ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x04, 0x10}; + +const uint8_t kOidSPHINCSSHA2192fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x05, 0x0a}; + +const uint8_t kOidSPHINCSSHA2192ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x05, 0x0c}; + +const uint8_t kOidSPHINCSSHA2256fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x06, 0x0a}; + +const uint8_t kOidSPHINCSSHA2256ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x06, 0x0c}; + +const uint8_t kOidSPHINCSSHAKE128fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x07, 0x0d}; + +const uint8_t kOidSPHINCSSHAKE128ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x07, 0x10}; + +const uint8_t kOidSPHINCSSHAKE192fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x08, 0x0a}; + +const uint8_t kOidSPHINCSSHAKE192ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x08, 0x0c}; + +const uint8_t kOidSPHINCSSHAKE256fsimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x09, 0x0a}; + +const uint8_t kOidSPHINCSSHAKE256ssimple[] = {0x2b, 0xce, 0x0f, 0x06, 0x09, 0x0c}; + + + // Returns true if |input| is empty. + [[nodiscard]] bool IsEmpty(const der::Input& input) { + ``` + * Find `if (oid == der::Input(kOidRsaSsaPss)) {`, then insert following lines before it + ```diff + return SignatureAlgorithm::kEcdsaSha512; + } -Note: For this to succeed, you might have to install go if not already present on your machine, e.g., by running `sudo apt install golang-go`. If _any_ error occurs in this step, Chromium will build fine, just without support for quantum-safe crypto, i.e., only the final testing steps below will fail. + +if (oid == der::Input(kOidDilithium2)) { + + return SignatureAlgorithm::kDilithium2; + +} + +if (oid == der::Input(kOidDilithium3)) { + + return SignatureAlgorithm::kDilithium3; + +} + +if (oid == der::Input(kOidDilithium5)) { + + return SignatureAlgorithm::kDilithium5; + +} + +if (oid == der::Input(kOidFalcon512)) { + + return SignatureAlgorithm::kFalcon512; + +} + +if (oid == der::Input(kOidFalcon1024)) { + + return SignatureAlgorithm::kFalcon1024; + +} + +if (oid == der::Input(kOidSPHINCSSHA2128fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2128fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHA2128ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2128ssimple; + +} + +if (oid == der::Input(kOidSPHINCSSHA2192fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2192fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHA2192ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2192ssimple; + +} + +if (oid == der::Input(kOidSPHINCSSHA2256fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2256fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHA2256ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHA2256ssimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE128fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE128fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE128ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE128ssimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE192fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE192fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE192ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE192ssimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE256fsimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE256fsimple; + +} + +if (oid == der::Input(kOidSPHINCSSHAKE256ssimple)) { + + return SignatureAlgorithm::kSPHINCSSHAKE256ssimple; + +} + + + if (oid == der::Input(kOidRsaSsaPss)) { + return ParseRsaPss(params); + ``` + * Find `switch (alg) {`, then add following case statements + ```diff + case SignatureAlgorithm::kRsaPkcs1Sha256: + case SignatureAlgorithm::kEcdsaSha256: + +case SignatureAlgorithm::kDilithium2: + +case SignatureAlgorithm::kFalcon512: + +case SignatureAlgorithm::kSPHINCSSHA2128fsimple: + +case SignatureAlgorithm::kSPHINCSSHA2128ssimple: + +case SignatureAlgorithm::kSPHINCSSHAKE128fsimple: + +case SignatureAlgorithm::kSPHINCSSHAKE128ssimple: + return DigestAlgorithm::Sha256; -6. Finally, navigate back to and follow the instructions [here](https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#Install-additional-build-dependencies) from the "Install additional build dependencies" section onwards to build Chromium. + case SignatureAlgorithm::kRsaPkcs1Sha384: + case SignatureAlgorithm::kEcdsaSha384: + +case SignatureAlgorithm::kDilithium3: + +case SignatureAlgorithm::kSPHINCSSHA2192fsimple: + +case SignatureAlgorithm::kSPHINCSSHA2192ssimple: + +case SignatureAlgorithm::kSPHINCSSHAKE192fsimple: + +case SignatureAlgorithm::kSPHINCSSHAKE192ssimple: + return DigestAlgorithm::Sha384; -Note: If you have already built another chromium source tree (version), you may have to execute `gclient sync --force` to ensure all dependencies are properly updated. + case SignatureAlgorithm::kRsaPkcs1Sha512: + case SignatureAlgorithm::kEcdsaSha512: + +case SignatureAlgorithm::kDilithium5: + +case SignatureAlgorithm::kFalcon1024: + +case SignatureAlgorithm::kSPHINCSSHA2256fsimple: + +case SignatureAlgorithm::kSPHINCSSHA2256ssimple: + +case SignatureAlgorithm::kSPHINCSSHAKE256fsimple: + +case SignatureAlgorithm::kSPHINCSSHAKE256ssimple: + return DigestAlgorithm::Sha512; -Note: It is *strongly* advisable to set certain build options to obtain a size-and-performance optimized chromium variant, also saving on build time. Do this by executing `gn args out/Default` and adding the following variables to the configuration file opened in your editor: -``` -# Set build arguments here. See `gn help buildargs`. -is_debug = false -symbol_level = 0 -enable_nacl = false -blink_symbol_level=0 -``` + // It is ambiguous whether hash-matching RSASSA-PSS instantiations count as + // using one or multiple digests, but the corresponding digest is the only + ``` +* Open _$CHROMIUM_ROOT/net/cert/pki/signature_algorithm.h_. + * Find `enum class SignatureAlgorithm {`, then insert following lines after `kRsaPssSha512,` + ```diff + kRsaPssSha384, + kRsaPssSha512, + + kDilithium2, + + kDilithium3, + + kDilithium5, + + kFalcon512, + + kFalcon1024, + + kSPHINCSSHA2128fsimple, + + kSPHINCSSHA2128ssimple, + + kSPHINCSSHA2192fsimple, + + kSPHINCSSHA2192ssimple, + + kSPHINCSSHA2256fsimple, + + kSPHINCSSHA2256ssimple, + + kSPHINCSSHAKE128fsimple, + + kSPHINCSSHAKE128ssimple, + + kSPHINCSSHAKE192fsimple, + + kSPHINCSSHAKE192ssimple, + + kSPHINCSSHAKE256fsimple, + + kSPHINCSSHAKE256ssimple, + }; + ``` +* Open _$CHROMIUM_ROOT/net/cert/pki/simple_path_builder_delegate.cc_. + * Find `bool IsAcceptableCurveForEcdsa` function, then insert following lines before `switch (curve_nid) {` + ```diff + bool IsAcceptableCurveForEcdsa(int curve_nid) { + +if (IS_OQS_PKEY(curve_nid)) { + + return true; + +} + + + switch (curve_nid) { + ``` + * Find `bool SimplePathBuilderDelegate::IsSignatureAlgorithmAcceptable` function, then insert following lines after `case SignatureAlgorithm::kRsaPssSha512:` + ```diff + case SignatureAlgorithm::kRsaPssSha384: + case SignatureAlgorithm::kRsaPssSha512: + + case SignatureAlgorithm::kDilithium2: + + case SignatureAlgorithm::kDilithium3: + + case SignatureAlgorithm::kDilithium5: + + case SignatureAlgorithm::kFalcon512: + + case SignatureAlgorithm::kFalcon1024: + + case SignatureAlgorithm::kSPHINCSSHA2128fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2128ssimple: + + case SignatureAlgorithm::kSPHINCSSHA2192fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2192ssimple: + + case SignatureAlgorithm::kSPHINCSSHA2256fsimple: + + case SignatureAlgorithm::kSPHINCSSHA2256ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE128fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE128ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE192fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE192ssimple: + + case SignatureAlgorithm::kSPHINCSSHAKE256fsimple: + + case SignatureAlgorithm::kSPHINCSSHAKE256ssimple: + return true; + } + ``` + * Find `bool SimplePathBuilderDelegate::IsPublicKeyAcceptable` function, then insert following lines before `// Unexpected key type.` + ```diff + return true; + } + + +if (IS_OQS_PKEY(pkey_id)) { + + return true; + +} + + + // Unexpected key type. + return false; + ``` +* Open _$CHROMIUM_ROOT/net/cert/pki/verify_signed_data.cc_. + * Find `bool VerifySignedData` function, then insert following case statements to `switch (algorithm) {` + ```diff + std::string_view cache_algorithm_name; + switch (algorithm) { + + case SignatureAlgorithm::kDilithium2: + + expected_pkey_id = EVP_PKEY_DILITHIUM2; + + cache_algorithm_name = "Dilithium2"; + + break; + + case SignatureAlgorithm::kDilithium3: + + expected_pkey_id = EVP_PKEY_DILITHIUM3; + + cache_algorithm_name = "Dilithium3"; + + break; + + case SignatureAlgorithm::kDilithium5: + + expected_pkey_id = EVP_PKEY_DILITHIUM5; + + cache_algorithm_name = "Dilithium5"; + + break; + + case SignatureAlgorithm::kFalcon512: + + expected_pkey_id = EVP_PKEY_FALCON512; + + cache_algorithm_name = "Falcon512"; + + break; + + case SignatureAlgorithm::kFalcon1024: + + expected_pkey_id = EVP_PKEY_FALCON1024; + + cache_algorithm_name = "Falcon1024"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2128fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2128FSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2128fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2128ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2128SSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2128ssimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2192fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2192FSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2192fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2192ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2192SSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2192ssimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2256fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2256FSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2256fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHA2256ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHA2256SSIMPLE; + + cache_algorithm_name = "SPHINCSSHA2256ssimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE128fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE128FSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE128fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE128ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE128SSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE128ssimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE192fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE192FSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE192fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE192ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE192SSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE192ssimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE256fsimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE256FSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE256fsimple"; + + break; + + case SignatureAlgorithm::kSPHINCSSHAKE256ssimple: + + expected_pkey_id = EVP_PKEY_SPHINCSSHAKE256SSIMPLE; + + cache_algorithm_name = "SPHINCSSHAKE256ssimple"; + + break; + case SignatureAlgorithm::kRsaPkcs1Sha1: + expected_pkey_id = EVP_PKEY_RSA; + ``` + * Find `crypto::OpenSSLErrStackTracer err_tracer(FROM_HERE);`, then make following changes + ```diff + } + } + + +bool ret; + +if (IS_OQS_PKEY(expected_pkey_id)) { + + ret = oqs_verify_sig(public_key, signature_value_bytes.UnsafeData(), signature_value_bytes.Length(), signed_data.UnsafeData(), signed_data.Length()) ? true : false; + +} else { + crypto::OpenSSLErrStackTracer err_tracer(FROM_HERE); + + bssl::ScopedEVP_MD_CTX ctx; + EVP_PKEY_CTX* pctx = nullptr; // Owned by |ctx|. + + if (!EVP_DigestVerifyInit(ctx.get(), &pctx, digest, nullptr, public_key)) + return false; + if (is_rsa_pss) { + // All supported RSASSA-PSS algorithms match signing and MGF-1 digest. They + // also use the digest length as the salt length, which is specified with -1 + // in OpenSSL's API. + if (!EVP_PKEY_CTX_set_rsa_padding(pctx, RSA_PKCS1_PSS_PADDING) || + !EVP_PKEY_CTX_set_rsa_pss_saltlen(pctx, -1)) { + return false; + } + } -If the build completes successfully, i.e., the executable `chrome` has been created, one can verify that Chromium can perform a TLS 1.3 handshake using a post-quantum key exchange by executing these steps: + if (!EVP_DigestVerifyUpdate(ctx.get(), signed_data.UnsafeData(), + signed_data.Length())) { + return false; + } -0. Navigate to ``, and start Chromium by executing `./out/Default/chrome` -1. Navigate again to the `/third_party/boringssl/src` folder, and build OQS-BoringSSL as a standalone project by running `mkdir build && cd build && cmake -GNinja ..`. -2. Then, in the `build` directory, run `./tool/bssl server -accept 4433 -www -loop -curves `, where `` can be any key-exchange algorithm named [here](https://github.com/open-quantum-safe/boringssl/blob/e2d2587065eacfe97aaae940dd43cd964b71f5b4#supported-algorithms) that is supported by default by Chromium. The [kDefaultGroups array](https://github.com/open-quantum-safe/boringssl/wiki/Implementation-Notes) lists all such algorithms\*. -3. Load `https://localhost:4433` in Chromium. + -bool ret = + +ret = + 1 == EVP_DigestVerifyFinal(ctx.get(), signature_value_bytes.UnsafeData(), + signature_value_bytes.Length()); + +} -An alternative test consists of using the newly built Chromium to access the OQS test server at [https://test.openquantumsafe.org](https://test.openquantumsafe.org) and clicking on any of the algorithm combinations [supported by Chromium](https://github.com/open-quantum-safe/boringssl/blob/e2d2587065eacfe97aaae940dd43cd964b71f5b4/ssl/extensions.cc#L353), e.g., `p256_kyber512`). + if (!cache_key.empty()) { + cache->Store(cache_key, ret ? SignatureVerifyCache::Value::kValid + ``` +* Open _$CHROMIUM_ROOT/net/base/features.cc_. + * Find feature `PostQuantumKyber`, then enable it + ```diff + BASE_FEATURE(kPostQuantumKyber, + "PostQuantumKyber", + - base::FEATURE_DISABLED_BY_DEFAULT); + + base::FEATURE_ENABLED_BY_DEFAULT); + ``` -Note: In order to avoid certificate warnings, you need to [download the test site certificate](https://test.openquantumsafe.org/CA.crt) using the newly-built chromium. Then click the "..." Control extensions button in the top-right window corner of your newly built Chromium browser, select "Settings", click on "Privacy and Security" in the newly opened window on the left, click on "Security" in the window pane on the right, scroll down and click on "Manage certificates", click on the "Certificates" tab in the newly opened screen, click on "Import" near the top of the newly opened pane and click on the "Downloads" folder on the file selector window that opens. Then double-click on "CA.crt" and check the box next to "Trust this certificate for identifying websites" and finally click "OK". +### 6. Generate BoringSSL Build Files for Chromium -*Note: If you already had been running an OQS-enabled chromium and upgraded to a more current version, clearing the cache is strongly advised to avoid "inexplicable" errors.* +```shellscript +cd $CHROMIUM_ROOT/third_party/boringssl +python src/util/generate_build_files.py gn +``` + +### 7. Build + +```shellscript +cd $CHROMIUM_ROOT +gn args out/Default +``` + +Then append following lines to the configuration file opened in editor: -\* For an explanation of why Chromium supports only a subset of key-exchange algorithms by default, consult [OQS-BoringSSL's Implementation Notes wiki page](https://github.com/open-quantum-safe/boringssl/wiki/Implementation-Notes). +``` +is_debug = false +symbol_level = 0 +enable_nacl = false +blink_symbol_level = 0 +``` -### Shipping binary +Save and close the configuration file. Last, run `autoninja -C out/Default chrome`.\ +If the build completes successfully, it will create _chrome_ in _$CHROMIUM_ROOT/out/Default_. -If all steps outlined above have been successfully executed, one can extract a standalone binary distribution by running `tar czvf chromium-binary.tgz *` within the directory `/out/Default` and moving the resulting `tgz` archive to a suitable machine with all UI components for execution. In order to not transfer too many unnecessary files, passing the options `--exclude='obj/*' --exclude='gen/*' --exclude=v8_context_snapshot_generator --exclude=mksnapshot --exclude=make_top_domain_list_variables --exclude=toolchain.ninja --exclude='*__pycache__*' ` to the `tar` command eliminates many files that are not essential for correct operation of a binary Chromium (v94) release. +### 8. Miscellaneous -### Automated build scripts -As the instructions above are complex and hard to get right the first time, a set of build scripts is included in the -scripts subdirectory. Please read scripts/README for more information on how to use them. +- This guide is based on Windows instructions (which was published on July 1, 2023), and may be outdated. +- A certificate chain that includes quantum-safe signatures can only be validated if it terminates with a root certificate that is in the [Chrome Root Store](https://chromium.googlesource.com/chromium/src/+/main/net/data/ssl/chrome_root_store/faq.md). \ No newline at end of file From 0369457030c5367546a842d5ae172361a841ba13 Mon Sep 17 00:00:00 2001 From: Raytonne <86047362+Raytonne@users.noreply.github.com> Date: Wed, 11 Oct 2023 00:50:23 -0500 Subject: [PATCH 4/4] Update README.md --- chromium/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chromium/README.md b/chromium/README.md index a150dbeb..d3918df2 100644 --- a/chromium/README.md +++ b/chromium/README.md @@ -1,9 +1,9 @@ This directory contains no longer fully maintained instructions and corresponding patches to build the Chromium web browser using the [OQS-BoringSSL fork](https://github.com/open-quantum-safe/boringssl), thereby enabling Chromium to use quantum-safe key exchange algorithms. Note that these instructions have been tested only on Windows 10 installations and apply at present only to a subset of quantum-safe key-exchanges as [documented here](https://github.com/open-quantum-safe/boringssl#key-exchange). -Please note that the Linux instructions are outdated and do not allow proper operation of a PQ-Chromium variant. The information is solely retained for people accepting this limitation. This limitation by no means should be understood as a preference for proprietary operating systems by the OQS team: Our focus remains on the support of open source software -- but we do not have the bandwidth to keep supporting the Chromium and BoringSSL PQ software stack at the same level as we did in the past. We welcome contributions and contributors allowing us to change this; most welcome would be contributions to bring up the Linux instructions and [patch](oqs-changes.patch) to the latest up- and downstream code level. +The information is solely retained for people accepting this limitation. This limitation by no means should be understood as a preference for proprietary operating systems by the OQS team: Our focus remains on the support of open source software -- but we do not have the bandwidth to keep supporting the Chromium and BoringSSL PQ software stack at the same level as we did in the past. We welcome contributions and contributors allowing us to change this; most welcome would be contributions to bring up the Linux instructions and [patch](oqs-changes.patch) to the latest up- and downstream code level. --- -[Outdated Build Instructions for Linux](README-Linux.md) +[Untested Build Instructions for Linux](README-Linux.md) [Build Instructions for Windows](README-Windows.md)