5 ms·
One of the things we do at Red Hat is migrate virtual machines off RHEL 5-era Xen to modern KVM, and one of the problems we have is that you can no longer ssh i
by rwmj 6y ago
One of the things we do at Red Hat is migrate virtual machines off RHEL 5-era Xen to modern KVM, and one of the problems we have is that you can no longer ssh into a RHEL 5 machine from a RHEL 8 machine because there's no common set of cyphers available. Currently you can work around this by relaxing the RHEL 8 machine's crypto policy to include "legacy"[1], although I wonder how long that option will be available.
For reference RHEL 5 was released in 2007 and is supported to the end of this year for some customers.
[1] http://libguestfs.org/virt-v2v-input-xen.1.html#ssh-authentication http://libguestfs.org/virt-v2v-input-xen.1.html#ssh-authenti...
- wlll 6y agoIf I was running Redhat machines and had bought support to the end of the year I think I'd expect Redhat to release packages for RHEL 5 that let me SSH to them from RHEL 8 machines.
- quietbritishjim 6y agoDoesn't it defeat the object of using an old, stable edition of an operating system if you keep installing feature updates to it?
- rwmj 6y agoRed Hat does update RHEL with new features, although not RHEL 5 which is now only getting security fixes. In this case there is a workaround (on the RHEL 8 / ssh client end) which is to enable legacy crypto policies. However you have to do this globally at least for all ssh connections (and our recommended command does it globally for the whole machine), and I guess there are reasons why the legacy policies are disabled by default, probably to do with possible MITM attacks against weak cyphers. So the situation isn't exactly ideal. Having said all that it would be up to me to actually fix this and I haven't looked into it in great detail since I don't believe any customers have asked about it. We only found out about it in our internal product QA.
- user5994461 6y agoThe legacy policies are disabled because they are not authorized for usage by regulations (NIST and co). Old large organization are compliance and process oriented. They run security audits that scan machines, finding X version of software that's end of life and Y cipher that's insecure, then raise control breaks to the systems owners to resolve.
- mcherm 6y agoSounds like a need for a separate "legacyssh" client that runs on RHEL 8 and supports the legacy cyphers.
- user5994461 6y agoRHEL 6 is going end of support in November 2020. RHEL 5 has been out of support for quite a while. https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#Product_life_cycle https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#Produ... Of course there are extended extended extended support programs for companies who are willing to pay. RHEL 5 is unusable at this point in time. It can't even run a HTTPS request to other systems because it's doesn't support TLS. It can't compile any software because it's stuck on gcc from more than 10 years ago. My company is upgrading the last machines from RHEL 6 and they're causing quite a bit of issues due to all the packages and operating systems being obsolete. It's reaching a point where it's less trouble to upgrade than to keep running. I can't imagine people still running on RHEL 5 willingly, they must be stuck running old software whom source code was lost.
- rwmj 6y agoRHEL 5 ELS ends Nov 30th 2020 (source: https://access.redhat.com/solutions/690063 https://access.redhat.com/solutions/690063). I agree on your other points though, but for some customers they still want to run RHEL 5 and it may not be a priority for them to do TLS requests or run GCC on new software - if they haven't been doing that on RHEL 5 up til now, why would they start? They often have some old database or bit of software that keep chugging along and would cost money to replicate or replace. We even offer a way to virtualize RHEL 5 servers so you can keep them running on "new" (virtual) hardware. (http://libguestfs.org/virt-p2v.1.html http://libguestfs.org/virt-p2v.1.html)
- user5994461 6y agoSystems have to continue to run and to interface with other systems (that shift over time). There isn't an option to never do a HTTPS request or never compile anything. Should clarify that the end-of-life schedule is coinciding for many platforms: RHEL 5 and RHEL 6, java 7 + 8, windows server 2008 + 2012, python 2. I don't think it's possible for RHEL 5 upgrade to not be an emergency priority at this stage. It's not able to run or to communicate with much of anything else (all platforms dropping SSL is one issue for example). What is the company gonna do when they can't curl and ssh between systems anymore?
- rurban 6y agoKVM is not more modern than Xen, just faster and more insecure. From the modernity point of view, Xen is far more modern, with proper seperation. But even Amazon is going away from Xen. Maybe to make it easier to break out of the hypervisor?
- rwmj 6y agoAmazon haven't used Xen or Qemu/KVM for new VMs for a long time. They have their own proprietary partitioning software (Nitro, using the Linux KVM ioctls), on their own designed hardware.