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.
i am in dire need of upgrading my openssh. my lan shop has pinged my puter with having unsecure ssh and they want me to have 3.7.1p1. i went to the RH site and found 3.1p1-13.i386.rpm for RH7.1(the server i want to upgrade)
now if this will create the same patches as 3.7.1p1 then that is all fine and dandy but my lan shop only worries about numbers. if they don't get 3.7* then i will be locked out of the system until i get the upgrade that they want.
when i try and upgrade my RH9 server i get dependencies problems
update******
i was able to upgrade the rh9 server. all i got to do is upgrade about a few hundred packages for the rh7.1 server that the new openssh depends on. thanks for everything guys/gals. thanks for the help.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
If you really did make install for the openssh source, look to see where it put the binaries. Likely they're in /usr/local/bin rather than the normal location. All you had to do was change your Sys V init script to point to the new binary. On my systems where I built from source, I actually moved all the old binaries to a backup directory and symlinked the old location to the new binaries.
You will of course need to stop and start the service after installing the new binaries that you compiled.
I am having the same problems as the OP. I suppose I could download and compile the latest which is what I will probably do if I can't get the RPM approach to work. My servers are 15 miles away in colo so it's always risky fooling with ssh.
I am currently at openssh 3.1p1 on RH 7.3. I downloaded the 3.7p1 srpm and it seemed to rebuild ok. But when I tried to rpm -Fvh the rpm file, I got complaints about dependencies for a lot of 3.1p - 14 stuff.
I came out of a Solaris environment so I am pretty new with rpms. My guess is that I am overlooking something pretty basic.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Quote:
Originally posted by joesbox update******
i was able to upgrade the rh9 server. all i got to do is upgrade about a few hundred packages for the rh7.1 server that the new openssh depends on. thanks for everything guys/gals. thanks for the help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.