Migration to EL9
Merge request reports
Activity
Filter activity
Tests on EL9:
$ faketime '2023-11-14 08:15:42' prove t/eec_cert1.t ................ ok t/eec_cert2.t ................ ok t/eec_chain.t ................ ok t/eec_subject1.t ............. ok t/eec_subject2.t ............. ok t/eec_subject3.t ............. ok t/encoding.t ................. ok t/expired.t .................. ok t/expired_ac.t ............... ok t/no_ac.t .................... ok t/no_ssl.t ................... ok t/no_ta.t .................... ok t/ssl_log_voms_plain_http.t .. skipped: to check later t/ssl_no_client_authn.t ...... ok t/subrequest.t ............... ok t/untrusted_ac1.t ............ ok t/untrusted_ac2.t ............ ok t/valid_ac.t ................. ok All tests successful. Files=18, Tests=40, 5 wallclock secs ( 0.06 usr 0.04 sys + 3.18 cusr 0.51 csys = 3.79 CPU) Result: PASS
Note that:
- the VOMS module was included statically inside the NGINX build, which means that all the tests have been modified temporarily in order to remove the line
load_module /etc/nginx/modules/ngx_http_voms_module.so;
- the certificates are based on weak tecnology (MD5 and similar), so I had to enable the LEGACY crypto policy system-wide
# update-crypto-policies --set LEGACY
- the certificates are also expired, hence the use of
faketime
- the VOMS module was included statically inside the NGINX build, which means that all the tests have been modified temporarily in order to remove the line
mentioned in commit dc82caa1
Please register or sign in to reply