Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When doing an upgrade of an existing version, you should normally use the -U (upgrade) or -F (freshen) options. Normally rpm -Uvh packagename works best. I certainly wouldn't recommend use the nodeps (no dependency checking) option. Kind of defeats one of major purposes of using rpms in the first place.
As far as doing system backups, it really depends on what you want to backup in the first place and the resources you have available (could be anything from tunnelled rsync to a dedicated server, to a tape drive, to just backing up user files on a local dvd burner).
That's why you should always do dependency checking with rpm. SSHd has a number of dependencies that are required to function correctly. libc.so.X is one of those requirements (you can see the full list of requirements by doing (rpm -q -R packagename). libc.so.X is usually provided by the glibc package. So you will need to upgrade to a compatible version of glibc. A note of warning though, glibc is used by a large number of programs and you can seriously break a lot of things if you upgrade glibc. This is especially true if you need to upgrade to a substantially differnet version of glibc. You can download the new version of glibc and see whether that generates a large number of dependency errors as well. If it doesn't generate any dependency errors, then you can go ahead and upgrade glibc.
Usually redhat supplies compatible versions of sshd (often these are patched versions) for the various versions of Redhat. Though now that support has been discontinued, I'm not sure if those are still available.
It might help if you told us what linux distro/version you are using and why you want to upgrade sshd as well as what versions of sshd (openssh-server) and glibc you have (you can find these by: rpm -qa | grep packagename)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.