Learn more about these different git repos.
Other Git URLs
If NSS is configured with NSS_DISABLE_DBM then Certmonger's self-tests fail:
Running test 002-keygen... Files /usr/src/tmp/runtestslZh53N and expected.out differ FAIL --- /usr/src/tmp/runtestslZh53N 2020-06-09 07:04:20.474428920 +0000 +++ expected.out 2020-01-31 15:38:19.000000000 +0000 @@ -0,0 +1,63 @@ +[nss:2048] +OK. +OK (RSA:2048). +OK. +OK (RSA:2048 after RSA:2048). +OK. +OK (RSA:2048 after RSA:2048). +keyi2048 +keyi2048 (candidate (next)) +[nss:3072] +OK. +OK (RSA:3072). +OK. ... cat 002-keygen/actual.err ... certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format.
and so on.
I'll open PR soon.
This should make 025-cacert-sql pass.
<img alt="0001-Handle-an-uninitialized-token-when-adding-CA-certs-t.patch" src="/certmonger/issue/raw/files/b7acf38c5a6280d375ee774cae7e9a850b2b336d1d476f1eef02bd980521ae97-0001-Handle-an-uninitialized-token-when-adding-CA-certs-t.patch" />
Do you want to integrate my patch into your PR or should I open the code change as a separate PR that yours will build on top of?
Merged PR 159
Metadata Update from @rcritten: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Sorry, I was on vacation. I've checked 'sql only' and 'dbm+sql' against your PR, both passed. Thank you.
Login to comment on this ticket.