Description of problem: Use genkey to create a self-signed SSL certificate. When the keypair generation completes and the locality, hostname, etc. are entered, the key is not created and an error message is displayed. Version-Release number of selected component (if applicable): How reproducible: Completely reproducable. I've tried this on multiple F16 hosts. Steps to Reproduce: 1. genkey 2. Choose "no" to send to Certificate Authority 3. Do not encrypt the private key 4. Enter the location information. 5. Press "Next" Actual results: Error: Was not able to create a certificate for this host: Press return to exit. "(null): " shows up at the shell window. dmesg shows: [75013.649780] keyutil[22286]: segfault at 10 ip 462adbdb sp bfb760b0 error 4 in libc-2.14.90.so[46268000+1a7000] Expected results: Key files generated. Additional info: Note that running "keyutil --help", the output starts with "Usage: (null) [options]" - for some reason, argv[0] isn't being passed.
After brief testing, this was seen to be when a field in the genkeys data-collection window had an unescaped comma (i.e. "," instead of "\,".) The tested field was the company name. Suggest someone revisiting the code for the above and seeing how it parses commas within argv parameters.
keyutil and genkey are part of the crypto-utils package, not the keyutils package.
Created attachment 658876 [details] Crash report from failed genkey
Following the same steps, but with the following command for genkey: genkey --days 3650 mail.example.com The domainname used in the command differs from the actual domain name of the server (we are transitioning to a new domain). Not sure if that is helpful.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is 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" 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
still reproducible in Fedora 17
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Commit: http://pkgs.fedoraproject.org/gitweb/?p=crypto-utils.git;a=commitdiff;h=3c5bc63a88f5d1ff334cf3509a6613a7b58eaf2c Package: crypto-utils-2.4.1-47.fc21 Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=494035
Commit: http://pkgs.fedoraproject.org/gitweb/?p=crypto-utils.git;a=commitdiff;h=3c5bc63a88f5d1ff334cf3509a6613a7b58eaf2c Package: crypto-utils-2.4.1-47.fc20 Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=494042
crypto-utils-2.4.1-48.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2014-1362/crypto-utils-2.4.1-48.fc20
crypto-utils-2.4.1-48.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/crypto-utils-2.4.1-48.fc19
crypto-utils-2.4.1-48.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
crypto-utils-2.4.1-48.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Fixed in updates.