aboutsummaryrefslogtreecommitdiff
path: root/patches/keypairtest.c.patch
diff options
context:
space:
mode:
authorBrent Cook <busterb@gmail.com>2024-03-25 02:27:16 -0500
committerBrent Cook <busterb@gmail.com>2024-03-25 02:39:33 -0500
commit011922e149e5b016669231a1dcc74ba902803645 (patch)
treee74cfb1359ed36c82669ce55c9a56afbb8d24d1d /patches/keypairtest.c.patch
parent0e30a6f66d0d9d95e586dcc9d01d2de8afc68cd6 (diff)
downloadportable-011922e149e5b016669231a1dcc74ba902803645.tar.gz
portable-011922e149e5b016669231a1dcc74ba902803645.tar.bz2
portable-011922e149e5b016669231a1dcc74ba902803645.zip
backport regress updates for new certs from jsing
Use the new certificates/chains in regress. The new certificates are more representative of the real world. The old certificates use weak algorithms and expire in the very near future. Most of our regress has already been switched over, this changes the remainder. Thanks to Bernhard M. Wiedemann for reminding us of the upcoming expiry. ok tb@
Diffstat (limited to 'patches/keypairtest.c.patch')
-rw-r--r--patches/keypairtest.c.patch11
1 files changed, 11 insertions, 0 deletions
diff --git a/patches/keypairtest.c.patch b/patches/keypairtest.c.patch
new file mode 100644
index 0000000..5d3b905
--- /dev/null
+++ b/patches/keypairtest.c.patch
@@ -0,0 +1,11 @@
1--- tests/keypairtest.c.orig Mon Mar 25 02:14:35 2024
2+++ tests/keypairtest.c Mon Mar 25 02:20:15 2024
3@@ -29,7 +29,7 @@
4 #include <tls_internal.h>
5
6 #define PUBKEY_HASH \
7- "SHA256:858d0f94beb0a08eb4f13871ba57bf0a2e081287d0efbaeb3bbac59dd8f1a8e5"
8+ "SHA256:f03c535d374614e7356c0a4e6fd37fe94297b60ed86212adcba40e8e0b07bc9f"
9
10 char *cert_file, *key_file, *ocsp_staple_file;
11