On Wed, Oct 19, 2022 at 1:47 PM Vitaly Zaitsev via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On 19/10/2022 14:14, Daniel P. Berrangé wrote: > > IOW, the impact of AES on server peformance will vary depending > > on CPU models, NIC models / network switches and whether other > > workloads are competing for CPU time. Admins need to decide > > what tradeoffs are important to them. > > In future, modern web browsers will start rejecting unencrypted HTTP > traffic (except localhost and intranet, ofc). All server owners should > switch to HTTPS as soon as possible. We don't use a browser for general updates, we use an application which can configure libcurl for it's desired requirements. The use of AES is not just required for client side, but on server side too, it takes non inconsiderable amount of compute to saturate a 10G+ link using https, that compute needs to come from somewhere and against most of the mirrors are being provided as a community donation and likely have requirements where if it hits a threshold it likely makes it unviable for that company to provide where they don't get a return (advertising, or something pro-rata) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
