3 factor authentication is something you know, something you have, and something you are. Current method is something you know -- the key...which as already been hacked so will be useless pretty soon and easy for a pirate to abuse. In computer terms we can combine the other two elements....
One thought is to use the Rig selection/Com port/Baud rate and pass it along with the message in place of what's being used now. That's why I asked about the # of bits available for this as that determines how to arrange this...don't need all the info to be uniquely identified. So rather than just K8R Verified We'd see this for example from information pulled straight from the Fox configuration. K8R Flex 192.168.1.1 Or K8R K4 COM5 115200 The other thing that would "fun" to do is catch the pirate by keeping the old callsign around when they change to the DXpedition call and transmit their callsign too. That's presuming their not smart enough to change configs. But could also grab their local IP address and transmit that. Mike W9MDB On Wednesday, July 24, 2024 at 03:15:17 PM CDT, Joe Taylor via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: Understandably, a number of people have asked us about how SuperFox works. I have explained that we are intentionally moving slowly and deliberately in our early tests, and we have not published source code or specifications in part because many details may still change. The basic SuperFox scheme has been proven to work well. It delivers the promised weak-signal gain of around 10 dB over multi-streaming FT8 with 5 streams. The present scheme will certainly be used for the Jarvis Island operations next month, but a variety of things could change after that. Our goals for design of a SuperFox mode have included the following: 1. Constant envelope waveform, and hence up to 10 dB signal-strength improvement over multi-streamed FT8. 2. Anti-piracy feature: a way to establish legitimacy of signal origin. 3. A way to prevent (or make much more difficult) misuse or our technology by derivative or modified programs, for example enabling robotic strings of QSOs. 4. Better use of available bandwidth: Fox should use (say) at least half of a ~3 kHz slice. 5. Better immunity to QRM, including deliberate QRM. 6. Operational aids for the Fox operator, including longer free text messages. As you can see, technical details have been important in our planning but sociological, moral, and even legal issues are involved as well. Objective 2 in the above list involves cyber security matters, an area in which we have little expertise. Our weak-signal performance requirements demand small message payloads, and these are incompatible with (for example) most public/private key schemes. For nearly all of its 24 year history the WSJT project has been entirely open source. Ideally we'd like to keep it that way. But objective 3 in the list is especially difficult (and likely impossible) to achieve in a fully open source project. We appreciate all the help we have received in testing an early SuperFox scheme. We hope many will work a new one when N5J operates as SuperFox from Jarvis Island. We'll continue working toward a maxmially effective SuperFox design in the presence of many challenges, including possible software licensing issues, and we welcome all constructive input from other interested hams. As always, our efforts are intended to benefit the wonderful hobby we share. -- 73, Joe, K1JT _______________________________________________ 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
