-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tqsl/lotw #492
Comments
Sorry, but this is not a QLog report, but a TQSL dialog window. QLog only uses the external TQSL program. If an error occurs in this external utility, it is necessary to contact the TQSL developer(s). |
I just quickly found a similar problem in some other project. It may be a problem that the new Fedora disabled the SHA1 hash function. If that doesn't mean anything to you, it's something that's used to sign QSOs. Unfortunately, according to this guide https://lotw.arrl.org/lotw-help/developer-tq8/?lang=en TQSL uses this deprecated function when generating the QSO signature. it is mentioned here that |
And next description on FedoraWiki: https://fedoraproject.org/wiki/SHA1SignaturesGuidance |
hi ladislav, thanks for the help, it was not easy for me to solve the
problem, a nice challenge on fedora linux 41, I managed to activate the
SHA1 which fedora /rehl had deactivated, now in output data qlog---->lotw
happens. see you soon and thanks again for the info.flavio
Il giorno sab 2 nov 2024 alle ore 15:19 Ladislav ***@***.***>
ha scritto:
… And next description on FedoraWiki:
https://fedoraproject.org/wiki/SHA1SignaturesGuidance
—
Reply to this email directly, view it on GitHub
<#492 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEBFR5MSGMCSR3UZUVX5V3DZ6TNNJAVCNFSM6AAAAABRBU76OSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGAYDKNZSHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
flavio. It is not an Fedora issue. It is a big issue of TQSL. The use of SHA1 hash has long been marked as obsolete. Distributions have been warning a long time that this hash is outdated and will be disabled soon. And with the Fedora, that time has come. The important thing is that the workaround helped you. |
Ok, thanks for the clarification ladislav ,yes I thought it was fedora,
lotw has been having some problems lately, but we're moving forward thanks
again and see you soon. regards
Il giorno lun 4 nov 2024 alle ore 08:45 Ladislav ***@***.***>
ha scritto:
… flavio. It is not an Fedora issue. It is a big issue of TQSL. The use of
SHA1 hash has long been marked as obsolete. Distributions have been warning
a long time that this hash is outdated and will be disabled soon. And with
the Fedora, that time has come.
The important thing is that the workaround helped you.
—
Reply to this email directly, view it on GitHub
<#492 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEBFR5I5PRUUC2QBYHMNM6DZ64QZ3AVCNFSM6AAAAABRBU76OSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUGAYTIMZVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
good morning ladislav, a new problem, since I updated fedora 40 to 41 there seems to be this problem with sending qso data to lotw I tried to update tqsl without positive results, maybe the new wayland graphical server that fedora uses? with the previous fedora 40 and wayland tqsl had no problems, maybe openssl reading on error message, any positive ideas?. bye and thanks as always for help. 73 by ik3ocd flavio
The text was updated successfully, but these errors were encountered: