I really don't think it's dodging the issue to tell the user what they need to
look at rather than giving them a useless-to-them message.The same "go look at
section XXX of manual" would apply to any SSL link.
I'm not going to hold my breath on lobbying the guv'ment either....
The email list had degenerated to insulting people for asking this question and
it gets VERY annoying to see that behavior to the point I'm about ready to
unsubscribe.
Seeing this same question and the rude replies for all eternity does not appeal
to me in the least (or I would imagine to you and Joe where some frustration
has been noted where people don't search the list or read the manual)
de Mike W9MDB
On Thursday, December 13, 2018, 7:04:44 AM CST, Bill Somerville
<[email protected]> wrote:
On 13/12/2018 12:42, Black Michael via wsjt-devel wrote:
> May I suggest that if the LOTW color coding option is not checked (and
> it looks like it defaults to off) that WSJT-X not download the lotw
> user file.
>
> Otherwise this question about the SSL error is going to go on forever
> for every new user that downloads WSJT-X.
>
> Then...when it's enabled pop up a box that says "Please read section
> 3.1 in the Users Guide about the SSL libraries need for this option.
>
> Same thing when an error happens downloading it to cover the bases.
>
> de Mike W9MDB
Mike,
that is dodging the real issue. The OpenSSL libraries are required for
Qt to access *any* secure Internet URL, it doesn't just apply to the
LoTW users data file. By putting off the issue as you suggest then
exactly the problem you cite will happen every time a new Internet
resource we use switches to secure access only. What we are doing now is
trying to get as many WSJT-X Windows users into the same place that
Linux and Mac users are in without having to install an extra package.
The real problem is your Government who insist that they can control the
use of strong cryptography by imposing export restrictions. You need to
lobby them for change, not here. If they changed then we could bundle
OpenSSL libraries in the WSJT-X installer for Windows, Microsoft might
even abandon the proprietary WinInet module and use OpenSSL themselves.
Not holding my breath on that last point though.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
