On Wed, Mar 9, 2022 at 2:47 PM Richard W.M. Jones <rjones(a)redhat.com> wrote:
Previous tightening of crypto defaults caused problems with us
connecting to older ssh servers.
I am particularly interested / worried about sshd from RHEL 5, 6 & 7
for virt-p2v and virt-v2v conversions. This broke before, requiring
us to advise users to set the global policy for the machine to LEGACY
(thus ironically weakening crypto for everything).
Also I have some ancient network equipment that cannot be upgraded but
needs older ssh protocols. I can't connect to it from Fedora unless I
set the crypto policy to LEGACY.
Anyway I'm wondering if the SHA-1 change will impact ssh further?
IIRC, the only SHA-1 thing that should be left in DEFAULT for SSH
is SHA-1 as HMAC, which doesn't rely on collision resistance.
So, not this round.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure