From: | David Zhang <david(dot)zhang(at)highgo(dot)ca> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Subject: | Re: Proposal for implementing OCSP Stapling in PostgreSQL |
Date: | 2024-03-06 00:12:06 |
Message-ID: | f44d520e-76ce-4046-afc1-6af052a2ec93@highgo.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Hackers,
This is the third version patch for "Certificate status check using OCSP
Stapling" with ssl regression test cases added.
Here is how I run the ssl regression test:
./configure --enable-tap-tests --with-openssl
make -j
cd src/test/ssl
make sslfiles
make check PG_TEST_EXTRA=ssl
expected results:
# +++ tap check in src/test/ssl +++
t/001_ssltests.pl .. ok
t/002_scram.pl ..... ok
t/003_sslinfo.pl ... ok
All tests successful.
Files=3, Tests=279, 17 wallclock secs ( 0.05 usr 0.01 sys + 2.32
cusr 2.16 csys = 4.54 CPU)
Result: PASS
Notes, before executing the SSL regression tests with the command `make
check PG_TEST_EXTRA=ssl`, it is necessary to wait for 1 minute after
running `make sslfiles`. This delay is required because the newly
generated OCSP responses for the 'expired' test cases need 1 minute to
pass the nextUpdate period. Once the stapled OCSP response files for the
tests are committed as test input, there is no need to wait, similar to
certificate files.
Any comments or feedback would be greatly appreciated!
Thank you,
David
Attachment | Content-Type | Size |
---|---|---|
0001-support-certificate-status-check-using-OCSP-stapling.patch | text/plain | 15.5 KB |
0002-doc-support-certificate-status-check-using-OCSP-stap.patch | text/plain | 4.2 KB |
0003-test-support-certificate-status-check-using-OCSP-sta.patch | text/plain | 21.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2024-03-06 00:24:09 | Re: Improve readability by using designated initializers when possible |
Previous Message | Michael Paquier | 2024-03-05 23:25:16 | Re: Hooking into ExplainOneQuery() complicated by missing standard_ExplainOneQuery |