abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 6803 bytes cmdline: certutil -C -d . -c testca -a -i rootca.req -v 12 -m 0 comment: What i am trying to achieve is to renew a self signed CA certificate using the same private key component: nss Attached file: coredump, 1081344 bytes crash_function: PR_Write executable: /usr/bin/certutil kernel: 2.6.35.14-96.fc14.x86_64 package: nss-tools-3.12.10-4.fc14 rating: 4 reason: Process /usr/bin/certutil was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1320218175 uid: 500 How to reproduce ----- 1.Create a Self signed Root CA certificate $certutil -S -d . -n "testca" -s "CN=rootca0,o=Example.com,c=US" -t "CT,," -x -2 -m 0000 -v 1 Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI testca CTu,u,u www u,u,u 2.Create a Request using certutil and -R options using the same private key as used by "testca" , to create a new Certificate for self signed CA with increased validity period than the earlier created in Step-1 certutil -d . -R -k "NSS Certificate DB:testca" -s "CN=rootca0,o=Example.com,c=US" -a -o rootca.req -m 0 -v 12 3. Sign the Request using the old CA created in Step-1 certutil -C -d . -c "testca" -a -i rootca.req -v 12 -m 0 Enter Password or Pin for "NSS Certificate DB": Segmentation fault (core dumped)
Created attachment 531269 [details] File: backtrace
This issue occurs because -o (output) was not passed when signing the request file. certutil -C -d . -c "testca" -a -i rootca.req -v 12 -m 0 It would be nice if it gives warning that -o options is not specified rather than crashing.
Yes and according to certutil -H .... -C Create a new binary certificate from a BINARY cert request ... -o output-cert Output binary cert to this file (default is stdout) .... it should have written the cert to standard output.
I logged the bug upstream https://bugzilla.mozilla.org/show_bug.cgi?id=699290 and will submit a patch.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping