On Fri, 2 Jul 2021 11:27:07 -0700 stan via test <test@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Fri, 02 Jul 2021 09:45:54 -0700 > Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > > > The first thing to check is to run `update-crypto-policies --set > > LEGACY`. If it works then, the issue is that the server is only > > offering an SSL version and/or cipher suite that is insecure by > > reasonably current standards (Fedora's default policy, 'DEFAULT'). > > In that case it should be possible to figure out what the server > > needs and come up with a more limited policy carve-out that will > > allow the server to keep working with the smallest possible > > reduction in security for other connections; leaving the level at > > LEGACY isn't great if you can avoid it. > > Thanks! This is exactly the kind of help I was looking for. I'm on > the legacy system that works right now, but will do this when I start > rawhide later for updates and continued tuning to make it comfortable. This was the problem. I think that I will try to get my ISP to update their crypto software to handle more secure algorithms, if I can. Probably a long shot. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
