This is on loading a .tq6 file after sending an initial certificate request.
Fedora 21, TrustedQSL v2.0.3
From diagnostic log:
TQSL Diagnostics
TQSL V2.0.3 build [pkg-v2.0.2-4-g0544a16]
(c) 2001-2014
American Radio Relay League
TrustedQSL library V2.4
Configuration data V2.8
wxWidgets 2.8.12 (Unicode)
libcurl V7.37.0
OpenSSL 1.0.1i 6 Aug 2014
zlib V1.2.8
Berkeley DB 5.3.28: (September 9, 2013)
...
Fri Mar 13 20:20:45 2015 notifyImport: type=274, message=Duplicate Trusted Root Authority certificate: American Radio Relay League Logbook of the World, data=0x1d78860
Fri Mar 13 20:20:45 2015 notifyImport: type=273, message=Duplicate Certificate Authority certificate: American Radio Relay League Logbook of the World, data=0x1d78860
Fri Mar 13 20:20:45 2015 notifyImport: type=528, message=certificate signature failure, data=0x1d78860
...
Fri Mar 13 20:20:45 2015 LCW_FinalPage::refresh:
certificate signature failure
I am not sure what to make of the zero loaded private keys. The ~/.tqsl/keys/ directory still contains the file containing the private key, having the filename of my callsign.
I've installed the debuginfo package and have been attempting to determine the problem via debugging, but that looks like a long road.
I appreciate any pointers.
Thanks,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "Certificate signature failure" seems to indicate that the TQ6 file you're trying to load isn't validating.
Did you build TQSL on Fedora from source, or get it from some repository? My "Linux" builds are done on Fedora, so there shouldn't be any real compatibility issues there.
Perhaps try downloading the TQ6 file from the LoTW website.
(Send me details at k1mu at arrl dot net if you want to troubleshoot further.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Rick,
Thanks a lot for the very quick support on private email on this question over the weekend.
For the benefit of other readers:
Fedora 21 has changed the default configuration for openssl to disallow the signature algorithm used in the certificate.
Setting the environmental variable OPENSSL_ENABLE_MD5_VERIFY=1 re-enables the algorithm in openssl. By using the below command to launch tqsl, I was able to load the certificate:
OPENSSL_ENABLE_MD5_VERIFY=1 tqsl
Users may choose to instead set that variable in .bashrc files rather than specifying it on the command line to launch tqsl.
--Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is on loading a .tq6 file after sending an initial certificate request.
Fedora 21, TrustedQSL v2.0.3
From diagnostic log:
I am not sure what to make of the zero loaded private keys. The ~/.tqsl/keys/ directory still contains the file containing the private key, having the filename of my callsign.
I've installed the debuginfo package and have been attempting to determine the problem via debugging, but that looks like a long road.
I appreciate any pointers.
Thanks,
Thomas
The "Certificate signature failure" seems to indicate that the TQ6 file you're trying to load isn't validating.
Did you build TQSL on Fedora from source, or get it from some repository? My "Linux" builds are done on Fedora, so there shouldn't be any real compatibility issues there.
Perhaps try downloading the TQ6 file from the LoTW website.
(Send me details at k1mu at arrl dot net if you want to troubleshoot further.)
Rick,
Thanks a lot for the very quick support on private email on this question over the weekend.
For the benefit of other readers:
Fedora 21 has changed the default configuration for openssl to disallow the signature algorithm used in the certificate.
Setting the environmental variable OPENSSL_ENABLE_MD5_VERIFY=1 re-enables the algorithm in openssl. By using the below command to launch tqsl, I was able to load the certificate:
Users may choose to instead set that variable in .bashrc files rather than specifying it on the command line to launch tqsl.
--Thomas