delta/libgit2.git/tests/online/badssl.c, branch ethomson/test_https github.com: libgit2/libgit2.git badssl: RC4 should not fail with ECERTIFICATE 2020-12-14T10:43:07+00:00 Edward Thomson ethomson@edwardthomson.com 2020-12-14T10:43:07+00:00 589b8129e065b0bcfdbb7c4eee815b6e149218bc Using RC4 is not a _certificate_ problem, it's a cipher problem. The SSL implementation should and will fail with an unrecoverable error (-1). There's no opportunity to accept/continue. 
Using RC4 is not a _certificate_ problem, it's a cipher problem.  The
SSL implementation should and will fail with an unrecoverable error
(-1).  There's no opportunity to accept/continue.
badssl: re-enable RC4 test 2020-12-13T15:56:36+00:00 Carlos Martín Nieto cmn@dwim.me 2017-11-18T14:51:08+00:00 89ffa98eacde35b045b16586be196dc2ca89ab0c This used to fail with an error indicating a mis-use of OpenSSL on platforms using it due to poor error handling. Re-enable it even if this isn't the right error code to use for now. 
This used to fail with an error indicating a mis-use of OpenSSL on platforms
using it due to poor error handling. Re-enable it even if this isn't the right
error code to use for now.
cmake: define GIT_HTTPS when HTTPS is supported 2017-04-25T08:15:59+00:00 Patrick Steinhardt ps@pks.im 2017-04-25T08:14:19+00:00 a4de1ae38980ea52d675d52d60d19f1bec61c127 






https: don't test that RC4 is invalid
2017-01-09T18:32:11+00:00

Carlos Martín Nieto
cmn@dwim.me

2017-01-09T17:53:21+00:00

2ac57aa89bde788173b54bd153430369deec64c0

None of our crypto backends actually reject RC4 as a cipher so don't
test for it and instead keep it as something we'd like to do.





None of our crypto backends actually reject RC4 as a cipher so don't
test for it and instead keep it as something we'd like to do.







http: correct the expected error for RC4
2017-01-09T17:58:58+00:00

Carlos Martín Nieto
cmn@dwim.me

2017-01-09T17:50:17+00:00

3829ba2e710553893faf6336cc6b2f3fc17a293e

We must make sure that we're getting a certificate error from the
library so we know that we're testing the right thing.





We must make sure that we're getting a certificate error from the
library so we know that we're testing the right thing.







http: perform 'badssl' check also via certificate callback
2017-01-06T17:09:52+00:00

Carlos Martín Nieto
cmn@dwim.me

2017-01-06T10:51:31+00:00

98d66240ecb7765e191da19b535c75c92ccc90fe

Make sure that the callbacks do also get a 'valid' value of zero when
the certificate we're looking at is in valid and assert that within the
test.





Make sure that the callbacks do also get a 'valid' value of zero when
the certificate we're looking at is in valid and assert that within the
test.







Use general cl_git_fail because the error is generic
2016-03-14T12:41:41+00:00

Dirkjan Bussink
d.bussink@gmail.com

2016-03-14T12:41:41+00:00

c577efbbb5565d078a08eae211cfb04987199809












Setup better defaults for OpenSSL ciphers
2016-03-14T12:07:13+00:00

Dirkjan Bussink
d.bussink@gmail.com

2016-03-14T12:02:00+00:00

fa72d6daf8624b9d2b11566625d0f588016c11db

This ensures that when using OpenSSL a safe default set of ciphers
is selected. This is done so that the client communicates securely
and we don't accidentally enable unsafe ciphers like RC4, or even
worse some old export ciphers.

Implements the first part of https://github.com/libgit2/libgit2/issues/3682





This ensures that when using OpenSSL a safe default set of ciphers
is selected. This is done so that the client communicates securely
and we don't accidentally enable unsafe ciphers like RC4, or even
worse some old export ciphers.

Implements the first part of https://github.com/libgit2/libgit2/issues/3682







Fix build for unit test
2015-11-02T21:19:25+00:00

Leo Yang
lyang@topologyinc.com

2015-10-30T17:53:53+00:00

505e4531b7e52daf6caa9eac9904d9a014e0d14f

If none of GIT_OPENSSL, GIT_WINHTTP or GIT_SECURE_TRANSPORT
is defined we should also be able to build the unit test.





If none of GIT_OPENSSL, GIT_WINHTTP or GIT_SECURE_TRANSPORT
is defined we should also be able to build the unit test.







net: add tests against badssl.com
2015-09-27T20:56:25+00:00

Carlos Martín Nieto
cmn@dwim.me

2015-09-27T20:48:39+00:00

53a2870514fb06b7aebfd1c55c19a61704906596

These provide bad X.509 certificates, which we should refuse to connect
to by default.





These provide bad X.509 certificates, which we should refuse to connect
to by default.