diff options
author | Tomas Mraz <tomas@openssl.org> | 2021-03-25 12:46:29 +0100 |
---|---|---|
committer | Tomas Mraz <tomas@openssl.org> | 2021-03-26 14:24:06 +0100 |
commit | cede07dc51728edce77336f0fe5fce6d62ed7654 (patch) | |
tree | 6d5e606a2acdfa8c9107bb2f26ae66676948a2e1 /test/data2.bin | |
parent | 6b2e51dd36c2f7f1ec24e84288324a12cfe3549e (diff) | |
download | openssl-cede07dc51728edce77336f0fe5fce6d62ed7654.tar.gz |
Remove the external BoringSSL test
Fixes #14424
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/14682)
Diffstat (limited to 'test/data2.bin')
-rw-r--r-- | test/data2.bin | 245 |
1 files changed, 59 insertions, 186 deletions
diff --git a/test/data2.bin b/test/data2.bin index c4f9691a26..40c1bdad13 100644 --- a/test/data2.bin +++ b/test/data2.bin @@ -1,188 +1,61 @@ TEST DATA2 -Running external test suites with OpenSSL -========================================= - -It is possible to integrate external test suites into OpenSSL's "make test". -This capability is considered a developer option and does not work on all -platforms. - - - -The BoringSSL test suite -======================== - -In order to run the BoringSSL tests with OpenSSL, first checkout the BoringSSL -source code into an appropriate directory. This can be done in two ways: - -1) Separately from the OpenSSL checkout using: - - $ git clone https://boringssl.googlesource.com/boringssl boringssl - - The BoringSSL tests are only confirmed to work at a specific commit in the - BoringSSL repository. Later commits may or may not pass the test suite: - - $ cd boringssl - $ git checkout 490469f850e - -2) Using the already configured submodule settings in OpenSSL: - - $ git submodule update --init - -Configure the OpenSSL source code to enable the external tests: - -$ cd ../openssl -$ ./config enable-ssl3 enable-ssl3-method enable-weak-ssl-ciphers \ - enable-external-tests - -Note that using other config options than those given above may cause the tests -to fail. - -Run the OpenSSL tests by providing the path to the BoringSSL test runner in the -BORING_RUNNER_DIR environment variable: - -$ BORING_RUNNER_DIR=/path/to/boringssl/ssl/test/runner make test - -Note that the test suite may change directory while running so the path provided -should be absolute and not relative to the current working directory. - -To see more detailed output you can run just the BoringSSL tests with the -verbose option: - -$ VERBOSE=1 BORING_RUNNER_DIR=/path/to/boringssl/ssl/test/runner make \ - TESTS="test_external_boringssl" test - - -Test failures and suppressions ------------------------------- - -A large number of the BoringSSL tests are known to fail. A test could fail -because of many possible reasons. For example: - -- A bug in OpenSSL -- Different interpretations of standards -- Assumptions about the way BoringSSL works that do not apply to OpenSSL -- The test uses APIs added to BoringSSL that are not present in OpenSSL -- etc - -In order to provide a "clean" baseline run with all the tests passing a config -file has been provided that suppresses the running of tests that are known to -fail. These suppressions are held in the file "test/ossl_shim/ossl_config.json" -within the OpenSSL source code. - -The community is encouraged to contribute patches which reduce the number of -suppressions that are currently present. - - -Python PYCA/Cryptography test suite -=================================== - -This python test suite runs cryptographic tests with a local OpenSSL build as -the implementation. - -First checkout the PYCA/Cryptography module into ./pyca-cryptography using: - -$ git submodule update --init - -Then configure/build OpenSSL compatible with the python module: - -$ ./config shared enable-external-tests -$ make - -The tests will run in a python virtual environment which requires virtualenv -to be installed. - -$ make test VERBOSE=1 TESTS=test_external_pyca - -Test failures and suppressions ------------------------------- - -Some tests target older (<=1.0.2) versions so will not run. Other tests target -other crypto implementations so are not relevant. Currently no tests fail. - - -krb5 test suite -=============== - -Much like the PYCA/Cryptography test suite, this builds and runs the krb5 -tests against the local OpenSSL build. - -You will need a git checkout of krb5 at the top level: - -$ git clone https://github.com/krb5/krb5 - -krb5's master has to pass this same CI, but a known-good version is -krb5-1.15.1-final if you want to be sure. - -$ cd krb5 -$ git checkout krb5-1.15.1-final -$ cd .. - -OpenSSL must be built with external tests enabled: - -$ ./config enable-external-tests -$ make - -krb5's tests will then be run as part of the rest of the suite, or can be -explicitly run (with more debugging): - -$ VERBOSE=1 make TESTS=test_external_krb5 test - -Test-failures suppressions --------------------------- - -krb5 will automatically adapt its test suite to account for the configuration -of your system. Certain tests may require more installed packages to run. No -tests are expected to fail. - - -GOST engine test suite -=============== - -Much like the PYCA/Cryptography test suite, this builds and runs the GOST engine -tests against the local OpenSSL build. - -You will need a git checkout of gost-engine at the top level: - -$ git submodule update --init - -Then configure/build OpenSSL enabling external tests: - -$ ./config shared enable-external-tests -$ make - -GOST engine requires CMake for the build process. - -GOST engine tests will then be run as part of the rest of the suite, or can be -explicitly run (with more debugging): - -$ make test VERBOSE=1 TESTS=test_external_gost_engine - -Updating test suites -==================== - -To update the commit for any of the above test suites: - -- Make sure the submodules are cloned locally: - - $ git submodule update --init --recursive - -- Enter subdirectory and pull from the repository (use a specific branch/tag if required): - - $ cd <submodule-dir> - $ git pull origin master - -- Go to root directory, there should be a new git status: - - $ cd ../ - $ git status - ... - # modified: <submodule-dir> (new commits) - ... - -- Add/commit/push the update - - git add <submodule-dir> - git commit -m "Updated <submodule> to latest commit" - git push - +This is just some data that is meant to be different from the contents +of the data.bin file. + +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod +tempor incididunt ut labore et dolore magna aliqua. Hendrerit dolor magna +eget est. Integer enim neque volutpat ac tincidunt vitae. Erat imperdiet +sed euismod nisi porta. Sit amet volutpat consequat mauris nunc. +Fermentum leo vel orci porta non. Purus viverra accumsan in nisl. +Volutpat maecenas volutpat blandit aliquam etiam erat velit scelerisque. +Gravida in fermentum et sollicitudin ac orci phasellus. Ut eu sem integer +vitae justo eget. Enim tortor at auctor urna nunc id. Laoreet non +curabitur gravida arcu ac tortor dignissim convallis aenean. A lacus +vestibulum sed arcu non odio euismod lacinia. In metus vulputate eu +scelerisque felis imperdiet proin fermentum. Semper quis lectus nulla at +volutpat diam ut venenatis tellus. Hac habitasse platea dictumst quisque. +Augue ut lectus arcu bibendum at varius vel pharetra. Nisl nunc mi ipsum +faucibus vitae aliquet. Nec sagittis aliquam malesuada bibendum arcu +vitae. Tellus id interdum velit laoreet id donec ultrices. + +Eget gravida cum sociis natoque. Nunc vel risus commodo viverra maecenas +accumsan. Enim lobortis scelerisque fermentum dui faucibus. Quis eleifend +quam adipiscing vitae. Nec nam aliquam sem et tortor. Pharetra massa +massa ultricies mi quis hendrerit. Tellus in metus vulputate eu +scelerisque. Et ultrices neque ornare aenean euismod elementum. Tellus +mauris a diam maecenas sed enim ut sem viverra. Fermentum leo vel orci +porta non pulvinar neque. Risus nullam eget felis eget nunc. Sed tempus +urna et pharetra pharetra massa massa ultricies. Dui sapien eget mi +proin. Vitae elementum curabitur vitae nunc sed velit dignissim sodales. +Sed arcu non odio euismod lacinia at. Enim praesent elementum facilisis +leo vel fringilla. Vel facilisis volutpat est velit egestas dui id ornare +arcu. Arcu dictum varius duis at. Pretium lectus quam id leo in vitae. + +Egestas fringilla phasellus faucibus scelerisque eleifend donec. Ut +ornare lectus sit amet est placerat in egestas. Viverra ipsum nunc +aliquet bibendum enim facilisis gravida neque. Commodo ullamcorper a +lacus vestibulum. Urna molestie at elementum eu. Mi in nulla posuere +sollicitudin aliquam ultrices sagittis orci a. Orci sagittis eu volutpat +odio facilisis mauris sit. Volutpat ac tincidunt vitae semper quis. +Adipiscing elit duis tristique sollicitudin nibh. Dignissim enim sit amet +venenatis urna cursus. Lacus luctus accumsan tortor posuere ac ut. Eu +feugiat pretium nibh ipsum consequat nisl. Arcu risus quis varius quam +quisque id diam. Urna nec tincidunt praesent semper feugiat nibh sed. Sed +libero enim sed faucibus turpis in eu mi. + +Suspendisse faucibus interdum posuere lorem ipsum dolor sit amet. Aliquet +eget sit amet tellus cras adipiscing enim. Lectus proin nibh nisl +condimentum id. Et odio pellentesque diam volutpat commodo sed egestas +egestas. Tempor id eu nisl nunc mi ipsum. Egestas erat imperdiet sed +euismod nisi porta lorem mollis aliquam. Pretium quam vulputate dignissim +suspendisse in est. Volutpat commodo sed egestas egestas fringilla. In +aliquam sem fringilla ut. Viverra accumsan in nisl nisi. Nam at lectus +urna duis convallis convallis. Tortor posuere ac ut consequat semper. +Pellentesque habitant morbi tristique senectus et netus et malesuada. +Aliquet enim tortor at auctor urna nunc id cursus metus. Sit amet luctus +venenatis lectus magna. A diam maecenas sed enim ut sem viverra aliquet. +Pellentesque sit amet porttitor eget dolor morbi. Eget lorem dolor sed +viverra ipsum nunc aliquet bibendum enim. Iaculis urna id volutpat lacus +laoreet non curabitur. Mattis vulputate enim nulla aliquet porttitor +lacus luctus accumsan tortor. |