From b7c623e732720fecf491beccb0a1d3fa54a1a5c1 Mon Sep 17 00:00:00 2001 From: Michael Baentsch <57787676+baentsch@users.noreply.github.com> Date: Tue, 17 Oct 2023 06:30:03 +0200 Subject: [PATCH] PR template update & OpenSSL clarification (#1582) * add test requirement to PR template * add OpenSSL 1.1.1 caveat * remove OQS-OpenSSL111 and OQS-BoringSSL from PR template checklist * add link to documentation of OPENSSL_ROOT_DIR --- .github/pull_request_template.md | 5 ++++- CONFIGURE.md | 2 +- README.md | 2 +- 3 files changed, 6 insertions(+), 3 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index de6bae3869..5fc3756a66 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -2,9 +2,12 @@ + + * [ ] Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from *x.y.z* to *x.(y+1).0*.) -* [ ] Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in [oqs-provider](https://github.com/open-quantum-safe/oqs-provider), [OQS-OpenSSL](https://github.com/open-quantum-safe/openssl), [OQS-BoringSSL](https://github.com/open-quantum-safe/boringssl), and [OQS-OpenSSH](https://github.com/open-quantum-safe/openssh) will also need to be ready for review and merge by the time this is merged.) +* [ ] Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., [oqs-provider](https://github.com/open-quantum-safe/oqs-provider) and [OQS-OpenSSH](https://github.com/open-quantum-safe/openssh) will also need to be ready for review and merge by the time this is merged.) + diff --git a/CONFIGURE.md b/CONFIGURE.md index 519b0eebab..d5407ca5ff 100644 --- a/CONFIGURE.md +++ b/CONFIGURE.md @@ -106,7 +106,7 @@ By default, These default choices have been made in order to optimize the default performance of all algorithms. Changing them implies performance penalties. -When `OQS_USE_OPENSSL` is `ON`, CMake also scans the filesystem to find the minimum version of OpenSSL required by liboqs (which happens to be 1.1.1). The `OPENSSL_ROOT_DIR` option can be set to aid CMake in its search. +When `OQS_USE_OPENSSL` is `ON`, CMake also scans the filesystem to find the minimum version of OpenSSL required by liboqs (which happens to be 1.1.1). The [OPENSSL_ROOT_DIR](https://cmake.org/cmake/help/latest/module/FindOpenSSL.html) option can be set to aid CMake in its search. **Default**: `ON`. diff --git a/README.md b/README.md index ef415c6f12..7d3b198310 100644 --- a/README.md +++ b/README.md @@ -91,7 +91,7 @@ In order to optimize support effort, brew install cmake ninja openssl@1.1 wget doxygen graphviz astyle valgrind pip3 install pytest pytest-xdist pyyaml - Note that, if you want liboqs to use OpenSSL for various symmetric crypto algorithms (AES, SHA-2, etc.) then you must have OpenSSL version 1.1.1 or higher. + Note that, if you want liboqs to use OpenSSL for various symmetric crypto algorithms (AES, SHA-2, etc.) then you must have OpenSSL installed (version 3.x recommended; EOL version 1.1.1 also still possible). 2. Get the source: