Re: [wsjt-devel] SuperFox Practice Session

2024-07-24 Thread DX Jami via wsjt-devel
Joe, Wishing your wife a speedy recovery.  Now you have to do the grocery shopping😄            Danny          AH6FX … AH6FX/W4 Sent from Yahoo Mail for iPad On Tuesday, July 23, 2024, 3:48 PM, Jim Preston via wsjt-devel wrote: Joe, My thoughts and prayers are with both of you. 73, Jim N6V

[wsjt-devel] SuperFox: How does it work?

2024-07-24 Thread Joe Taylor via wsjt-devel
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 sc

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread James Shaver via wsjt-devel
+1 to Hasan - nobody is forcing anyone to use SF.  You're spending more time splitting hairs about this than any useful output and wasting everyone's time and bandwidth - the Dev list is becoming less useful as a result. Go ahead and develop your own thing if all you are going to do is point

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Fons Adriaensen via wsjt-devel
On Wed, Jul 24, 2024 at 02:19:51PM +0100, Hibby via wsjt-devel wrote: > Identity and keysigning is a solved problem True. What is required here is a public-key signature scheme. The fox produces a key pair and publishes the public key which is then used by the hounds. The problem is that all p

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Tom M0LTE via wsjt-devel
How so? On Wed, 24 Jul 2024 at 14:05, Hasan N0AN via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Yes, congratulations are in order. You have now made it easy for the > Pirates, before it was somewhat more difficult. > Way to go. > Hasan > > > On Wed, Jul 24, 2024 at 7:31 AM Jonathan M

Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq

2024-07-24 Thread Andy Durbin via wsjt-devel
Joe, Thanks for taking the time to improve my understanding of how WSJT-X frequency control and reporting is designed to work. The design may be intuitive for a VHF/UHF operator but it certainly was not for me as someone who only works HF and 6 m chasing DX. I think what I'd like to do is run

Re: [wsjt-devel] Licensing Issue of SuperFox Mode

2024-07-24 Thread Hibby via wsjt-devel
Hey Neil, Don't worry - bubble not burst. I'm choosing to not pick a fight about the specific licensing of the binaries. Arguments about licensing are full of opinions and not very fun. They usually end up in flame wars and cold disagreement, as I think we can see from the previous discussion.

Re: [wsjt-devel] Licensing Issue of SuperFox Mode

2024-07-24 Thread Neil Zampella via wsjt-devel
Hate to burst your bubble, the binaries do NOT have to be stripped, as they can be included as an exception to the GPL license. Neil, KN3ILZ On 7/24/2024 4:05 AM, Hibby wrote: Hi all, Turns out you can't tell furries that a superfox is proprietary! https://sprocketfox.io/xssfox/2024/07/24/sup

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Hibby via wsjt-devel
Hi Hasan, To be clear, Jonathan has so far posted to the list and not facilitated any pirates! To summarise what is going on (and separate from any tedious license discussions) - in the interests of preventing DXPedition piracy, some people are playing with the new binaries and have surmised t

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Jonathan McComb via wsjt-devel
Hasan, No. An insecure algorithm, that no-one has had any opportunity to review due to the source code for the superfox binaries not being published, has made it no more difficult than it previously was for the pirates. Jonathan, GI3JMC On Wed, Jul 24, 2024 at 2:03 PM Hasan N0AN wrote: > Yes,

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Hasan N0AN via wsjt-devel
Yes, congratulations are in order. You have now made it easy for the Pirates, before it was somewhat more difficult. Way to go. Hasan On Wed, Jul 24, 2024 at 7:31 AM Jonathan McComb via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hasan, > > Did you actually take the time to read **an

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Jonathan McComb via wsjt-devel
Hasan, Did you actually take the time to read **and understand** the blog post I linked, and the contents of the similar discussions (linked below) regarding the superfox binaries in the mailing list? https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/ZoMmzGysLjXJ5B2O%40msg.df7cb.de/#msg587

Re: [wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Hasan N0AN via wsjt-devel
Jonathon, Then don't use SuperFox Hasan On Wed, Jul 24, 2024 at 5:25 AM Jonathan McComb via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > https://sprocketfox.io/xssfox/2024/07/24/superflawed/ > > The Superfox mode uses security by obscurity, (which is never a good > thing) by failing t

[wsjt-devel] Superhound operating protocol

2024-07-24 Thread Charles Suckling via wsjt-devel
Today I had my first attempt to work K8R on 12m, I obtained fairly quickly a report, and sent TX3 in response but received no RR73 from them. Decodes were solid, so I did not miss any message containing the RR73. TX messages from me continued with TX3 until I manually ceased (after about 8 repe

[wsjt-devel] WSJT-X SuperFox Verification is flawed

2024-07-24 Thread Jonathan McComb via wsjt-devel
https://sprocketfox.io/xssfox/2024/07/24/superflawed/ The Superfox mode uses security by obscurity, (which is never a good thing) by failing to publish any source code for the dedicated superfox binaries to allow for peer review. It is exceptionally misguided. Amateur Radio should be available to

Re: [wsjt-devel] Licensing Issue of SuperFox Mode

2024-07-24 Thread Hibby via wsjt-devel
Hi all, Turns out you can't tell furries that a superfox is proprietary! https://sprocketfox.io/xssfox/2024/07/24/superflawed/ After I mentioned my disappointment and concern about the implications of closed binaries in this week's zero retries [1], including making users in debian, ubuntu, r