REGTESTS: ssl: add the same cert for client/server

Add the same certificate in server and bind line so we can try to catch
problems like in issue #1748 when updating over the CLI.
This commit is contained in:
William Lallemand 2022-06-20 18:01:30 +02:00
parent cb6c5f4683
commit ae6547f65f
2 changed files with 4 additions and 0 deletions

View File

@ -43,6 +43,8 @@ haproxy h1 -conf {
listen clear-lst listen clear-lst
bind "fd@${clearlst}" bind "fd@${clearlst}"
# dummy bind used to test a change when the same crt is used as server and bind
bind "fd@${foobarlst}" ssl crt ${testdir}/set_cafile_client.pem ca-file ${testdir}/set_cafile_interCA1.crt verify none
server s1 "${tmpdir}/ssl.sock" ssl crt ${testdir}/set_cafile_client.pem ca-file ${testdir}/set_cafile_interCA1.crt verify none server s1 "${tmpdir}/ssl.sock" ssl crt ${testdir}/set_cafile_client.pem ca-file ${testdir}/set_cafile_interCA1.crt verify none
listen clear-verified-lst listen clear-verified-lst

View File

@ -69,6 +69,8 @@ haproxy h1 -conf {
listen ssl-lst listen ssl-lst
bind "${tmpdir}/ssl.sock" ssl crt ${testdir}/common.pem strict-sni bind "${tmpdir}/ssl.sock" ssl crt ${testdir}/common.pem strict-sni
server s1 ${s1_addr}:${s1_port} server s1 ${s1_addr}:${s1_port}
# dummy server used to test a change when the same crt is used as server and bind
server s2 ${s1_addr}:${s1_port} ssl crt ${testdir}/common.pem verify none weight 0
listen other-ssl-lst listen other-ssl-lst
bind "${tmpdir}/other-ssl.sock" ssl crt-list ${testdir}/set_default_cert.crt-list bind "${tmpdir}/other-ssl.sock" ssl crt-list ${testdir}/set_default_cert.crt-list