Sponsored Content
Full Discussion: Java patching
Operating Systems Linux Red Hat Java patching Post 302606127 by bitlord on Friday 9th of March 2012 03:31:07 PM
Old 03-09-2012
Java patching

hello,
I'm a Solaris admin and I was asked to patch some RHEL servers. I'm having trouble trying to figure out the RHEL java version. Can someone help me?

This what I do in Solaris
Code:
java -version
java version "1.5.0_34"
java(TM) 2 Runtime Envirement, Standard Edition (build 1.5.0_34-b03)
Java HotSpot(TM) Server VM (build 1.5.0_34-b03, mixed mode)

This what I see on RHEL
Code:
java -version
java version "1.4.2"
gij (GNU libgcj) version 4.1.2 20080704 (Red Hat 4.1.2-52)

or
Code:
java -version
java version "1.6.0_22"
OpenJDK Runtime Envirement (IcedTea6 1.10.6) (rhel-1.25.1.10.6.e15_8-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b11 mixed mode)

I went to the RHEL site and looked at this page.
https://access.redhat.com/security/cve/CVE-2010-4454
The issue is the version numbers don't match the layout I get from the command line. I can't figure out if my version has been patched to cover the vulnerability. In Solaris The latest update is 1.5.0_34 & 1.6.0_31 (put out in Feb), I would like to have the RHEL servers patched to the same level.

OS
RHEL 5.x, (5)
RHEL 4.x (1)

Can someone help me understand the versioning RHEL is using.
 
jpackage-utils(7)						RPM Java packaging						 jpackage-utils(7)

NAME
jpackage-utils - Utilities, macros and other files for the JPackage Project <http://www.jpackage.org/>: SYNOPSIS
build-classpath build the Java classpath in a portable manner build-jar-repository build a jar repository in a portable manner rebuild-jar-repository rebuild a jar repository in a portable manner (after a jvm change...) build-classpath-directory build the Java classpath from a directory diff-jars show jar content differences jvmjar install jvm extensions create-jar-links create custom jar links clean-binary-files remove binary files from sources check-binary-files check for presence of unexpected binary files DESCRIPTION
The JPackage Project has two primary goals: - To provide a coherent set of Java software packages for Linux, satisfying all quality requirements of other applications. - To establish an efficient and robust policy for Java software packaging and installation. We focus on free and open source software whenever possible. For convenience, we also provide non-free packages without the restricted source code. Our RPMs are generic in that they should work on any RPM based Linux distribution (Mandriva, Red Hat, SuSE, others). Other packaging format suggestions are welcome too. FILES
/use/share/java-utils/java-functions shell script functions library for Java applications /etc/java/jpackage-release string identifying the currently installed JPackage release /etc/java/java.conf system-wide Java configuration file ~/.java/java.conf user's Java configuration /etc/rpm/macros.jpackage RPM macros for Java packagers and developers SEE ALSO
Regular Manual Pages build-classpath(1) build-classpath-directory(1) build-jar-repository(1) check-binary-files(1) clean-binary-files(1) create-jar-links(1) diff-jars(1) find-jar(1) jvmjar(1) rebuild-jar-repository(1) rebuild-security-providers(1) java.conf(5) Documentation Following files are located in your standard documentation directory HEADER.JPP A standard header with license for spec files of JPackage Project clean-binary-files.txt A further documentation for check-binary-files(1), clean-binary-files(1) and create-jar-links(1) commands httpd-javadoc.conf Example JPackage javadoc configuration snippet for Apache jpackage-1.5-policy.xhtml JPackage Java infrastructure design and packaging policy jpackage-utils-policy JPackage packaging (naming) policy AUTHOR
Written by the JPackage Project REPORTING BUGS
Report bugs using JPackage Bugzilla (http://www.jpackage.org/bugzilla/) jpackage-utils 1.7.5 February 2009 jpackage-utils(7)
All times are GMT -4. The time now is 03:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy