|
Re: SMTP Problems with Spotcollector
Dave AA6YQ
+ AA6YQ comments below
I didn't see where in Gmail to specify SSL as adequate. + See https://support.google.com/accounts/answer/6010255?hl=en + which is now referenced by the documentation in 73,
|
|
|
|
Re: DXKeeper uploads every QSO to LotW despite checkbox for this feature is unchecked
Gene W3UA
Technically, none of the above. I'm using hamlog.online agent, which takes QSO data from WSJT-X (on modified port), uploads QSO to hamlog online and simultaneously sends UDP packet to DXLab using standard WSJT-X UDP port -- so DXLab thinks that it's getting data from WSJT-X. UDP packets from WSJT-X are not modified in any way -- so to DXLab it should look like direct connection to WSJT. DXkeeper logs the QSO perfectly -- so my only trouble is that QSO is also sent to LotW...
73, Gene W3UA
|
|
|
|
Re: SMTP Problems with Spotcollector
I didn't see where in Gmail to specify SSL as adequate.
Jim N7US
Sent from Samsung tablet
-------- Original message --------
From: "Ben Coleman NJ8J via groups.io" <nj8j@...>
Date: 6/5/21 9:47 PM (GMT-06:00)
To: DXLab@groups.io
Subject: Re: [DXLab] SMTP Problems with Spotcollector
On 6/5/2021 9:18 PM, Dave AA6YQ wrote:
> To send email, SpotCollector employs a Microsoft-provided mechanism (CDO > - Collaboration Data Objects) that is has not been updated to support > TLS. Finding an alternative mechanism that supports TLS and making it > work would not be rocket science, but testing all of the different usage > scenarios would require significant effort. Note that there are 2 different uses of the SSL and TLS terminology here: 1. How SMTP specifies using encryption for the client connection: using SSL (port 465, which starts using encryption from the moment of the connection) or using the Submission port (port 587) and using the Start TLS command to start encryption (sometimes abbreviated to TLS). 2. The actual "SSL" encryption protocol used for encryption - SSL (versions 1.0, 2.0, and 3.0, all considered obsolete and insecure), and TLS (versions 1.0, 1.1 (both considered obsolete), 1.2, and 1.3). Note that "TLS" in the first usage may very well use any of the SSL or TLS protcols of the second usage. I believe Tom is referring to the second usage. It wouldn't surprise me if CDO lacks "TLS" in either usage. Lacking it in the first is a mere inconvenience. Lacking it in the second is more serious, as the SSL 1.0, 2.0, and 3.0 protocols are considered insecure and breakable. Many users of this type of encryption are requiring TLS 1.2 or TLS 1.3, and there is some movement towards accepting only TLS 1.3. If CDO can't use TLS 1.2 or TLS 1.3, that's going to make the priority of switching to another mechanism higher. Ben -- Ben Coleman nj8j@... "I love the way Microsoft follows standards. In much the same manner that fish follow migrating caribou." Paul Tomblin
|
|
|
|
Re: SMTP Problems with Spotcollector
On 6/5/2021 9:18 PM, Dave AA6YQ wrote:
To send email, SpotCollector employs a Microsoft-provided mechanism (CDO - Collaboration Data Objects) that is has not been updated to support TLS. Finding an alternative mechanism that supports TLS and making it work would not be rocket science, but testing all of the different usage scenarios would require significant effort.Note that there are 2 different uses of the SSL and TLS terminology here: 1. How SMTP specifies using encryption for the client connection: using SSL (port 465, which starts using encryption from the moment of the connection) or using the Submission port (port 587) and using the Start TLS command to start encryption (sometimes abbreviated to TLS). 2. The actual "SSL" encryption protocol used for encryption - SSL (versions 1.0, 2.0, and 3.0, all considered obsolete and insecure), and TLS (versions 1.0, 1.1 (both considered obsolete), 1.2, and 1.3). Note that "TLS" in the first usage may very well use any of the SSL or TLS protcols of the second usage. I believe Tom is referring to the second usage. It wouldn't surprise me if CDO lacks "TLS" in either usage. Lacking it in the first is a mere inconvenience. Lacking it in the second is more serious, as the SSL 1.0, 2.0, and 3.0 protocols are considered insecure and breakable. Many users of this type of encryption are requiring TLS 1.2 or TLS 1.3, and there is some movement towards accepting only TLS 1.3. If CDO can't use TLS 1.2 or TLS 1.3, that's going to make the priority of switching to another mechanism higher. Ben -- Ben Coleman nj8j@benshome.net "I love the way Microsoft follows standards. In much the same manner that fish follow migrating caribou." Paul Tomblin
|
|
|
|
Re: SMTP Problems with Spotcollector
Dave AA6YQ
+ AA6YQ comments below
While I agree a DX spot is not a risk, the gmail credentials are sent over that same pipe. If it uses SSL ( long since deprecated) than TLS 1.2 ( at least), that is a risk to the credentials. + To send email, SpotCollector employs a Microsoft-provided mechanism (CDO - Collaboration Data Objects) that is has not been updated to support TLS. Finding an alternative mechanism that supports TLS and making it work would not be rocket science, but testing all of the different usage scenarios would require significant effort. + Users concerned with the continued use of SSL to access their primary Gmail account could setup a secondary Gmail account for the exclusive use of SpotCollector notifications, and with unique credentials (username and password); any exposure of these secondary account credentials due to the relative weakness of SSL would not compromise the security of their primary Gmail account. 73, 73,
|
|
|
|
Re: SMTP Problems with Spotcollector
Dave,
While I agree a DX spot is not a risk, the gmail credentials are sent over that same pipe. If it uses SSL ( long since deprecated) than TLS 1.2 ( at least), that is a risk to the credentials. Can SpotCollector not support TLS? I never noticed this since I use a local Raspberry Pi as my network’s SMTP relay. It actually talks to GMail. Tom NY4I Principal Solutions Architect Better Software Solutions, Inc. 727-437-2771
|
|
|
|
Pathfinder search library update
Dave AA6YQ
The next time you start Pathfinder, an Update button will appear in its Main window's upper-left corner. Clicking this button will
update Pathfinder's search of the French Online Callbook, thanks to Björn SM0SBL. Note that the New Zealand online callbook has been updated, and now employs encryption in its interaction with web browsers -- and thus cannot be reverse engineered. To avoid being prompted with a non-functional ZL search button, delete the ZL.txt file from Pathfinder's Searches folder. Thanks to Gary ZL2IFB for this information. 73, Dave, AA6YQ
|
|
|
|
Re: Winwarbler not decoding
ve3ki
It might have been 75 baud RTTY. There's a contest this weekend in which RTTY75 is one of the contest modes.
toggle quoted messageShow quoted text
73, Rich VE3KI
On Sat, Jun 5, 2021 at 05:41 PM, Ted Boerkamp wrote:
|
|
|
|
Re: SMTP Problems with Spotcollector
Dave AA6YQ
+ AA6YQ comments below
I dug around on Google and had to specifically enable "Less Secure App access" but it seems to be working now. Thanks... "Less secure app access Some apps and devices use less secure sign-in technology, which makes your account vulnerable. You can turn off access for these apps, which we recommend, or turn it on if you want to use them despite the risks. Google will automatically turn this setting OFF if it’s not being used." + Thanks! There's not much risk of sending DX notifications via SSL instead of TLS. I've added a note with your finding to the recommended Gmail settings in https://www.dxlabsuite.com/spotcollector/Help/ConfigurationNotifications.htm#Settings%20for%20popular%20outgoing%20email%20servers 73, Dave, AA6YQ
|
|
|
|
Re: Winwarbler not decoding
Dave AA6YQ
+ AA6YQ comments below
Hello All.I turned on my radio and I am currently tuned to 14.088.05 and there is a Station on rtty pretty strong here in Ontario Canada. However I have winwarbler set up with 3 receive partitions..mmtty, 2 tone and a pk232. I cannot decode this station at all on any of the partitions its just gibberish being printed. Any suggestions what I am missing here?? I am receiving on 20m LSB RTTY on a yaesu FT1000MP. Any help appreciated. Its always worked before so I think its something + The station might be transmitting RTTY "upside down" (in which case check the "RTTY Receive" panel's Reverse box) or the station might be transmitting RTTY using a baud rate other than 45.45 (in which case try specifying a different Speed a the top of the Configuration window's RTTY tab - like 50, or 75); see http://www.w1hkj.com/modes/rtty.htm 73, Dave, AA6YQ
|
|
|
|
Winwarbler not decoding
Ted Boerkamp
Hello All…I turned on my radio and I am currently tuned to 14.088.05 and there is a Station on rtty pretty strong here in Ontario Canada. However I have winwarbler set up with 3 receive partitions….mmtty, 2 tone and a pk232. I cannot decode this station at all on any of the partitions its just gibberish being printed. Any suggestions what I am missing here?? I am receiving on 20m LSB RTTY on a yaesu FT1000MP. Any help appreciated. Its always worked before so I think its something simple I am missing. Thanks 73 Ted VE3SS
|
|
|
|
Re: DXKeeper uploads every QSO to LotW despite checkbox for this feature is unchecked
Dave AA6YQ
+ AA6YQ comments below
I recently connected WSJT-X to DXLab. For some reason, when I complete QSO made with WSJT-X, DXkeeper not only records it into its database, but also sends a 1-QSO file to LotW. I don't like this behavior, so I disabled it long time ago by unchecking the checkbox "Upload each QSO logged via capture window lo LotW" in Lotw Tab in DXKeeper QSL configuration. Maybe WSJT connector has different configuration which I simply can't find? How can I disable this? Maybe this feature (sending 1-QSO files to LotW) should be configured once for each mode and source of incoming QSOs?+ Are you using the direct interoperation bewteen DXLab and WSJT-X, or are you using JT-Alert? 73, Dave, AA6YQ
|
|
|
|
DXKeeper uploads every QSO to LotW despite checkbox for this feature is unchecked
Gene W3UA
I recently connected WSJT-X to DXLab. For some reason, when I complete QSO made with WSJT-X, DXkeeper not only records it into its database, but also sends a 1-QSO file to LotW. I don't like this behavior, so I disabled it long time ago by unchecking the checkbox "Upload each QSO logged via capture window lo LotW" in Lotw Tab in DXKeeper QSL configuration. Maybe WSJT connector has different configuration which I simply can't find? How can I disable this? Maybe this feature (sending 1-QSO files to LotW) should be configured once for each mode and source of incoming QSOs?
73, Gene W3UA
|
|
|
|
Re: SMTP Problems with Spotcollector
peril2k <peril2k@...>
I dug around on Google and had to specifically enable "Less Secure App access" but it seems to be working now. Thanks...
"Less secure app access Some apps and devices use less secure sign-in technology, which makes your account vulnerable. You can turn off access for these apps, which we recommend, or turn it on if you want to use them despite the risks. Google will automatically turn this setting OFF if it’s not being used." Again - these are Google's deal, not me...I've used DXL for over 10 years and am a fan :-)
|
|
|
|
Re: SMTP Problems with Spotcollector
peril2k <peril2k@...>
On Fri, Jun 4, 2021 at 10:29 PM, Dave AA6YQ wrote:
https://www.dxlabsuite.com/spotcollector/Help/ConfigurationNotifications.htm#Settings%20for%20popular%20outgoing%20email%20servers"Sign-in attempt was blocked." "Suspicious attempt to sign in from a less secure app." Their words, not mine ;-)
|
|
|
|
Re: SMTP Problems with Spotcollector
peril2k <peril2k@...>
TNX Dave -
I got a Google security alert saying that a "Less secure" app was trying to access my account and they blocked it and noted changes as to which apps could access the account. I'm not being accusatory. I had had Google's SMTP server set up for several years and it worked fine. Used SSL with authentication, etc. I'll compare my settings with the link in your documentation and see if I can re-create the Google message.
|
|
|
|
Re: SpotCollector - Strange scrolling experience
Dave AA6YQ
+ AA6YQ comments below
They are functional, but if I scroll "up" to the top of the list, it then scrolls back down to the bottom (oldest) spot. + Sounds like you have auto-scroll enabled. Click the flashing words "auto-scroll" in the Main window's upper-right corner. 73,
|
|
|
|
Re: SpotCollector - Strange scrolling experience
Jon KM8V
They are functional, but if I scroll "up" to the top of the list, it then scrolls back down to the bottom (oldest) spot.
Previously, unless I am imagining things, it would hold the scroll at the top of the list, with the most recent spots.
|
|
|
|
Re: VK CB in Pathfinder Fails
Hi Bjorn,
toggle quoted messageShow quoted text
I did do that, but it still failed. I suspect I have something wrong in one of the fields, but cannot work out what. 73 de Phil GU0SUP
-----Original Message-----
From: "Björn (SM0SBL)" <sm0sbl@langelspost.se> Sent: Saturday, 5 June, 2021 06:41 To: DXLab@groups.io Subject: Re: [DXLab] VK CB in Pathfinder Fails Dave: will do when at the computer Phil: I had to restart PathFinder to make it work. -- Björn, SM0SBL
|
|
|
|
Re: VK CB in Pathfinder Fails
Björn (SM0SBL)
Dave: will do when at the computer
Phil: I had to restart PathFinder to make it work. -- Björn, SM0SBL
|
|
|