Trusted QSL V2.0 Release Notes This version of Trusted QSL has been revamped to combine tqslcert and tqsl into a single program, added additional documentation for certificate operations, and includes a new, task-oriented Graphical User Interface (GUI). On Windows, simply install TQSL 2.0. The installer will automatically uninstall older versions of Trusted QSL while preserving your configuration information. On Mac OS X, open the disk image (.dmg) file and drag the “Trusted QSL” folder to your Applications folder. Tell the installer to “Replace All” to uninstall old files. For Linux systems, unpack the tar file and read the INSTALL file for directions. There are several things that you will notice when you run the new TQSL program is that the GUI is very different. See the screen shot below.

The GUI has buttons for major operations. In this case, the first tab has log operations such as signing a log as well as a function for creating a new ADIF log, and for logging in to the Logbook of The World site. Below this is a screen area that will be used to display status messages for any operations that you perform.

The GUI also has tabs for operations on Station Locations and Callsign Certificates. The Station Location tab (accessed by clicking on the “Station Locations” label displays your station locations and associated call signs as shown below.

Many of the buttons on this page are disabled (and greyed out) until you select a location to edit, delete, or display. This is also true for the callsign certificate page.

The Callsign Certificates tab looks similar to the old tqslcert display with action buttons added.

The certificates on the left area show one significant change between tqslcert 1.x and tqsl 2.0. Earlier releases of Trusted QSL only displayed current callsign certificates by default. In 2.0, tqsl always displays all of the installed callsign certificates. If a callsign certificate has expired, it will be displayed with a clock icon with a “!” in a red triangle . If a callsign certificate has been replaced (i.e. a newer certificate for that callsign has been installed), the icon will have an A->B image

to denote that this certificate has been replaced.

For completeness, here are all of the icons and what they represent: This is a normal callsign certificate, ready for use. This certificate is damaged1. It cannot be used until restored from a backup or a .p12 file. This represents a certificate request (a new or a renewal) where the .tq6 response from LoTW has not yet been installed. This callsign certificate has expired. This callsign certificate has been replaced with a newer one also installed on your computer.

There are no reasons to keep expired or replaced callsign certificates around. Users are encouraged to select deleted certificates using a right mouse click and choosing “Delete Callsign Certificate”.

1

This icon appears when the “Private Key” is missing or cannot be read.

In addition to the new GUI, 2.0 adds a feature that allows full backup and restore of all TQSL data, automated uploads of callsign certificate requests, and several other major and minor changes. The following list describes the major changes in the v2.0-RC1 release. TQSLLIB changes Fix atoi() calls throughout to use strtol() so that strings like 012 aren't treated as Octal due to the leading zeroes, or rejected because of numbers like ‘09’. Change the default Cabrillo callsign field to 8, not 5. This is often the right field to use while the older default (5) was never the right callsign field. Fix OpenSSL workaround needed for 1.0.0c of OpenSSL so that it only applies to that release, not later releases with the fix already in place. This change allows tqsllib to build on many Linux systems with more recent OpenSSL. Add new tqsllib APIs:

     

Retrieve a named field from a station location Merge a station location definition into the database Add the ability to export station locations APIs to export and import certificates Base-64 encoded APIs to export and import duplicates database records Added an API to calculate the difference between dates

Verify that the BAND and FREQ fields are consistent. Disallow frequencies outside of valid ranges for ham bands. This catches "10110" used (KHz) versus the ADIF required 10.110 (MHz). Always convert frequency values in Cabrillo logs to Megahertz independent of the contest type (HF/VHF). TQSL changes Major feature Additions: Merge tqslcert into tqsl. Update the graphical user interface to be more user friendly. For the Callsign Certificates tree display, don't display the certificate provider list if there's only one provider. Detect new versions of the TQSL configuration file when performing the "check for updates" operation (manual or automatic) and allow the user to update the configuration file if there is a newer one available. Allow users to back up and restore their TQSL configuration in a portable file. Automatically back up the configuration to a user-specified directory (or to a default one) unless this is disabled. Add diagnostic logging capability. This is used to store a verbose log from cURL and to write a trace log that can be used by the developers to help determine the source of defects. Display unique icons in the certificate tree to allow expired and superseded certificates can be distinguished. Always display all callsign certificates, including expired and superseded certificates. Detect and report invalid frequencies in ADIF files (outside of ham bands, entered in KHz versus MHz.)

Validate the format of Grid Squares when they're entered for a station location. This also fixes the case to be normalized, upper case for the Field, lower case for the subsquare (FM18ju, for example). Correct the defect that could cause invalid QSOs (bad call signs, for example) to result in a cancellation message from an attempt to sign the log but not provide detail on what QSO failed. Automatically back up the user's configuration whenever TQSL closes. Display the versions of the major software packages built into TQSL as part of the "Help/About" text. Don't ask the user to choose the file type for certificate load operations, just provide a file open dialog and allow them to choose. When issuing a callsign certificate request, default to "signed" unless there are no usable certificates to be used to sign the request. Add text to the dialog box explaining when unsigned requests should be used. Remove the initial "Certificate Providers" page from the certificate request wizard as it serves no current purpose. Use consistent terminology throughout - "Callsign Certificate" and "Station Location". Replace atoi() calls with strtol() to correct parsing of strings like '012' so they are not treated as octal. Enforce frequency entry in the ADIF editor, ensuring that frequencies are entered correctly (in MHz) and within an amateur band. Reject frequencies that are not consistent with the BAND setting. Correct the exit code for circumstances when -a abort is used and a bad QSO is detected. Display the error information on that QSO before exiting. Add new command line options "-b" to select the start date for QSOs to be signed (begin) and -e to select the end date for QSOs to be signed. Warn users on startup when they have a certificate that's going to expire soon (in less than 60 days) and allow them to generate a renewal request. Back up certificate details (address, entity) when backing up as .p12 file. Change the title of the certificate request window to reflect whether this is a new or a renewed certificate. Add the ability to automatically upload a certificate request to the LoTW site. Make the preferences window a top-level window so it doesn't block activity in the help screen, etc. Delete obsolete mode maps when signing a log. When creating a station location, default to the callsign selected on the locations tree if one is selected. Add a button to the Log Operations window that opens the Logbook of The World website. Add a new command line option, -n, which checks for new versions of critical TQSL files then exits. This is designed for use by logging programs that operate TQSL on behalf of the user. Add network proxy preference settings to allow users to use the TQSL network-based functions on networks that require all traffic to use a proxy.

Grab window focus when prompting for the certificate password to ensure that the password window appears on top of the calling logger. Simplify the messages displayed on certificate import (relegate the details to the diagnostic log). Detect additional network transfer errors (from log uploads, updates, etc.) and translate them into more userfriendly text.