Bug#987332: aprx automatically starts up with really bad default config

[Hibby <d@vehibberd.com>]

Hi all,

I had a quick look at the code - config.c carries a validate_callsign_input() function, which I think we could patch a check in to cause the program to exit with an incorrect callsign for APRS-IS error.

Alternatively, it’s checking for a 6 character callsign, so we could make N0CALL-1  longer by a character or two in the config to force an error.

Do either of these seem like a reasonable way to force an error, or will this just end up with the failed upgrades we want to avoid?

—
Hibby
MM0RFN