For those, who tried to help me, big hand. I think I found reason. OPENSSL. I had to edit openssl.conf, to get TRUSTEDQSL work.
/etc/pki/tls/openssl.conf, There # Uncomment the sections that start with ## below to enable the legacy provider. # Loading the legacy provider enables support for the following algorithms: # Hashing Algorithms / Message Digests: MD2, MD4, MDC2, WHIRLPOOL, RIPEMD160 # Symmetric Ciphers: Blowfish, CAST, DES, IDEA, RC2, RC4,RC5, SEED # Key Derivation Function (KDF): PBKDF1 # In general it is not recommended to use the above mentioned algorithms for # security critical operations, as they are cryptographically weak or vulnerable # to side-channel attacks and as such have been deprecated. [provider_sect] default = default_sect #legacy = legacy_sect <------- ## [default_sect] activate = 1 ##[legacy_sect] #activate = 1 <---------- If I uncomment marked points, systemd-resolved stops working. BUT Trustedqsl works and I need that working.. So, Now my choise is comment those out and use system-resolved as masked, and use self edited resolv.conf So, my point of vew, problem SOLVED. Another thing is, vhen TQSL corrects program to follow these new OPENSSL rules. Word for other NOOBS, don't give up, even you have about to do that :) Jarmo -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
