So now we would require cryptographic signing of QSOs? I mean, I'd be ticked if someone used one of my callsigns, but I wouldn't rally the entire amateur community around a complex solution to the 'problem'.
It was hard enough for me as a computer professional to get TQSL set up, I gotta say I'd never bother with CryptoSignedQSO, and if I didn't opt-in, would my real QSOs be valid anywhere? A real rathole, IMHO. Not that it _couldn't_ be done, but another barrier to entry (and probably the requirement for a continuous Internet connection during QSOs without jumping through a bunch of hoops) doesn't feel to me like an advancement of the hobby. But you know, go ahead and write it, interface it to WSJT using the standard APIs, and see if it's adopted. "Run it up the flagpole and see if anyone salutes." 73, Willie > On Oct 11, 2023, at 8:58 PM, Ashhar Farhan via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > I guess, a simpler approach would be to provide a checksum derived from your > secret key associated with your callsign in your QSLs. > This needs to be outside the wsjtx. The infrastructure should be maintained > by a non-profit international body. Like the eff.org <http://eff.org/>. > - f > > On Tue, Oct 10, 2023, 11:58 PM Glenn Williams via wsjt-devel > <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>> > wrote: >> Hi, >> Why not be concerned about your password on QRZ.COM <http://qrz.com/>? If >> that gets >> hacked by someone they have access to a huge database of names and >> addresses to pick through. >> >> Password security is well described in: >> >> 12 character passwords are no longer safe enough. That's it. Done. All >> over. Tell your kids. >> >> https://www.hivesystems.io/blog/are-your-passwords-in-the-green?utm_source=tabletext >> >> --73, Glenn, AF8C >> >> -- >> This email has been checked for viruses by Avast antivirus software. >> www.avast.com <http://www.avast.com/> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
