- 15 5月, 2020 1 次提交
-
-
由 Matt Caswell 提交于
Reviewed-by: NRichard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/11839)
-
- 06 5月, 2020 1 次提交
-
-
由 Matt Caswell 提交于
The test_includes test was failing if OPENSSL_CONF_INCLUDE happened to be set in the user's environment. To ensure that no tests accidentally use this or other enviroment variables from the user's environment we automatically set them centrally for all tests. Reviewed-by: NTomas Mraz <tmraz@fedoraproject.org> (Merged from https://github.com/openssl/openssl/pull/11691)
-
- 06 12月, 2018 1 次提交
-
-
由 Richard Levitte 提交于
Reviewed-by: NMatt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/7767)
-
- 13 2月, 2018 1 次提交
-
-
由 Matt Caswell 提交于
Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
- 07 2月, 2018 1 次提交
-
-
由 Richard Levitte 提交于
The afalg engine was moved down from engines/afalg/ to engines/, but the test wasn't changed accordingly. This was undetected because the test program didn't fail when it couldn't load the engine. Reviewed-by: NRich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/5270)
-
- 22 4月, 2016 1 次提交
-
-
由 Rich Salz 提交于
Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
- 15 3月, 2016 1 次提交
-
-
由 Emilia Kasper 提交于
Also make it possible to disable afalg separately. we still need to update config again Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
- 07 3月, 2016 2 次提交
-
-
由 Matt Caswell 提交于
The new afalg test should have a copyright date of 2016. Also an incorrect buffer was being sent to EVP_CipherFinal_ex when decrypting. Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
由 clucey 提交于
Reviewed-by: NRichard Levitte <levitte@openssl.org> Reviewed-by: NMatt Caswell <matt@openssl.org>
-
- 22 2月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
We were kinda sorta using a mix of $disabled{"static-engine" and $disabled{"dynamic-engine"} in Configure. Let's avoid confusion, choose one of them and stick to it. Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 20 2月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
They depend on this feature because they use the engine ossltest, which is only available as a dynamic engine. Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 13 2月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
If the environment variable HARNESS_ACTIVE isn't defined or HARNESS_VERBOSE is defined, it's probable that lots of output is desired. Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 09 2月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
To be able to run tests when we've built in a directory other than the source tree, the testing framework needs a few adjustments. test/testlib/OpenSSL/Test.pm needs to know where it can find shlib_wrap.sh, and a number of other tests need to be told a different place to find engines than what they may be able to figure out on their own. Relying to $TOP is not enough, $SRCTOP and $BLDTOP can be used as an alternative. As part of this change, top_file and top_dir are removed and srctop_file, bldtop_file, srctop_dir and bldtop_dir take their place. Reviewed-by: NBen Laurie <ben@openssl.org>
-
- 26 1月, 2016 2 次提交
-
-
由 Richard Levitte 提交于
Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
-
由 Richard Levitte 提交于
Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 17 1月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
Make sure they detect that. Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
-
- 14 1月, 2016 1 次提交
-
-
由 Richard Levitte 提交于
Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
-
- 12 12月, 2015 1 次提交
-
-
由 Ben Laurie 提交于
Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 14 10月, 2015 1 次提交
-
-
由 Andy Polyakov 提交于
Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
- 07 9月, 2015 1 次提交
-
-
由 Richard Levitte 提交于
This involves adding $TOP/util as perl library in test/run_tests.pl. Reviewed-by: NRich Salz <rsalz@openssl.org>
-
- 12 8月, 2015 2 次提交
-
-
由 Matt Caswell 提交于
When using an anon DH ciphersuite a client should reject a 0 value for p. Reviewed-by: NRichard Levitte <levitte@openssl.org>
-
由 Matt Caswell 提交于
Two tests are added: one is a simple version tolerance test; the second is a test to ensure that OpenSSL operates correctly in the case of a zero length extensions block. The latter was broken inadvertently (now fixed) and it would have been helpful to have a test case for it. Reviewed-by: NRichard Levitte <levitte@openssl.org>
-