Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 09-20-2003, 01:17 PM   #1
Registered: Jul 2001
Location: Utah
Distribution: RedHat v7.3, OpenBSD 3.3, FreeBSD 5.0
Posts: 327

Rep: Reputation: 30
How to map Red Hat RPM patch level => software version?


How can I determine which version of a particular package my Red Hat system is running based on the patch level of a particular RPM?

For instance, on *BSD systems and other GNU/Linux systems that I administer, I generally find a package that has been fully updated parallel to the vendor's package version. Take for example OpenSSH; the current version from the vendor is 3.7.1. On my slackware 9 box, I am running 3.7.1 and therfore I know that my openssh version is up to date. I can also telnet to port tcp/22 on the server and see the banner report 3.7.1 to me. On my OpenBSD 3.3 box, I have updated openssh via CVS and rebuilt it, and now telnet'ing to the tcp/22 reveals that I am running 3.7.1

However on Red Hat, I am running some convoluted patch version of the 3.1 (openssh-server-3.1p1-10, to be exact.) Now I realize that this is 3.1p1 patched up to patch level 10, but telnet'ing to this port says I am running 3.1, and I can't quite map the patch level to the vendor's release version to determine if this box is up to date. 2 months down the road from now, how will I know which vulnerabiliities I am patched against given the patch level?

How can I work this out?
Old 09-20-2003, 03:01 PM   #2
Registered: May 2001
Posts: 29,360
Blog Entries: 55

Rep: Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547Reputation: 3547
openssh-server-3.1p1-10, to be exact.
Can I first ask you what compelling reasons you have to keep a way old version of SSH loaded? Even if you can't check out the patch level, there's no excuse for updating: building the rpm's from the current OpenSSH/portable tarball is a no-brainer.
Don't mix up your priorities.
Old 09-20-2003, 03:55 PM   #3
Registered: Jul 2001
Location: Utah
Distribution: RedHat v7.3, OpenBSD 3.3, FreeBSD 5.0
Posts: 327

Original Poster
Rep: Reputation: 30
My inclination is to do just that, and in the past that's precisely what I've done. It seems that sometimes though, Red Hat is a little ahead in producing updated binary RPMs than the obsd team is in producing a src RPM.

The other reason is in keeping things in order with up2date; for instance, new 3.1.x-x rpms will not apply over a built-from-source 3.6.1 RPM because it sees the higher version as being newer. So for standardizing on up2date as a method of updating the system, one is still left in the same rut.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Solarais version and patch level? itsjustme Solaris / OpenSolaris 12 11-13-2003 04:01 PM
Best Version of Red Hat? qcoder Red Hat 5 10-24-2003 11:19 AM
Red Hat Time Zone map johnraphone Red Hat 1 09-25-2003 03:45 AM
trivial newbie-level login question (Red Hat) glock27linux Linux - General 3 04-09-2003 04:55 AM
Best Red Hat version? cliffyman Linux - General 6 11-07-2001 10:44 AM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 10:05 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration