Re: [ARRL-LOTW] Expired certificate
- OK, I received my second new certificate from the ARRL today. I
installed it and have it working under Fedora 12. Thanks for the help
provided. If nothing else, it prodded me off of top dead center. I think
I actually caused the problem with the first certificate. After applying
for it, I think I deleted the certificate from TQSL, thinking that it
should not be there untl I received the .tq6 in the email. We can be our
own worst enemies some times. 73 to all on the list.
Rick Murphy/K1MU wrote:
> At 05:50 PM 11/28/2009, Roy G. Jackson wrote:
> >OK, I applied for and received a new .tq6 file for my current call,
> >N9RG. I have no .tq5, .tq6 or .tq8 files on my system, that I can find.
> >When I run TQSLCert and try to load the new certificate, I get a message
> >saying, "Certificate or private key not found." I am running Fedora 12
> >and the latest TQSLCert program for Linux. I am at a loss for where to
> >go from here. I should not have any certificate files on the disk, as
> >when I initially tried to load the PKCS#12 file is when I got the
> >original message about my certificate being expired. Any Linux users on
> >this list that can offer suggestions? Thanks and 73.
> You're to be congratulated for actually getting TrustedQSL to work on
> Linux. It's very out of date. Getting it to compile is difficult at
> best, and the binaries are for Fedora 3 when Fedora 12 is current. :-)
> [Offer to ARRL: I'll be happy to supply diffs to allow it to build on
> current versions of Linux if someone wants.]
> Now, on to your problem.
> First, the common cause for "Certificate or private key not found" is
> that you ran tqslcert on one computer to generate the certificate
> request and tried to load the resulting .tq6 file on a different computer.
> On a Linux system, when you run tqslcert to generate a certificate
> request, there will be a file in "~/.tqsl/keys/<callsign>" that
> contains your private key. (For you, it'll be "~/.tqsl/N9RG". When you
> run tqslcert on the correct system, you'll see the requested
> certificate showing up with a "slashed key" icon next to the callsign;
> if you don't see that, then the private key isn't on that computer for
> some reason. You can't restore the .tq6 if there's no corresponding
> private key.