Red Hat Bugzilla – Bug 600670
Last modified: 2010-11-10 17:13:37 EST
+++ This bug was initially created as a clone of Bug #598160 +++
Description of problem:
I received an email with the following:
Certificate for hostname 'iridium', in file (or by nickname):
The certificate needs to be renewed; this can be done
using the 'genkey' program.
When attempting to run genkey --days 365 localhost (this is a workstation using a self signed key) I get an error about a /etc/pki/tls/private/localhost.key existing, to remove it first and then re-run genkey. Once removed if I re-run genkey I get an immediate segfault. I just ran this on a CentOS 5.4 box moments before without a problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. genkey --days 365 servername
--- Additional comment from email@example.com on 2010-06-01 11:19:52 EDT ---
Also, genkey --gdb servername is of no help as it just segfaults anyway before getting into gdb
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Created attachment 423352 [details]
simpler script that segfaults
This is not a bug on genkey. This script is basically a HelloWorld that uses perl_Newt and when I run it, 'perl ./hello.pl elio', it segfaults on F-13 and not on F-12. I looked at perl_newt in F-12 &F-13 and the code is identical expect that it was rebuilt with a slighly newer version of perl in F-13.
My perl skills are a bit limited and knowledge of perl_newt more so.
Joe, do you see anything wrong with hello.pl?
Ah, sorry for blaming you for this unnecessarily, my bad :(
Yes this is clearly a perl-Newt issue.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.