Adding cacerts to jdk15

Greg Lewis glewis at eyesbeyond.com
Tue Feb 22 13:17:36 PST 2005


On Sun, Feb 20, 2005 at 08:22:54AM +1300, Jonathan Chen wrote:
> On Sat, Feb 19, 2005 at 03:22:12PM +0200, Alexey Zelkin wrote:
> 
> [...]
> > We are not adding cacerts for jdk1[34], but *replacing* it (because
> > of security problems).  JDK 1.5.0 was released *after* this problem
> > was found and fixed, so jdk15 is distributing with valid cacerts
> > file and there's no reason to do any manual interventions.
> 
> I have to agree with Micheal. The installed port on i386 comes back
> with an empty cacerts file as well:
> 
> 8:19am> ls -l /usr/local/jdk1.5.0/jre/lib/security/cacerts 
> -rw-r--r--  1 root  wheel  32 Jan 25 22:53 /usr/local/jdk1.5.0/jre/lib/security/cacerts

I suspect this has something to do with patchset 1 not building javaws:

> ls -l deploy/src/javaws/share/config/cacerts j2se/src/share/lib/security/cacerts
-rw-r--r--  1 glewis  staff  7910 Nov  8 15:28 deploy/src/javaws/share/config/cacerts
-rw-r--r--  1 glewis  staff    32 Nov  8 15:28 j2se/src/share/lib/security/cacerts

So, I don't think we need to add a separate file to the port, just install
the correct cacerts file for now, e.g. add something like the following
to the do-install target (untested):

	${INSTALL_DATA} ${WRKDIR}/deploy/src/javaws/share/config/cacerts \
		${PREFIX}/jdk${JDK_VERSION}/jre/lib/security

then once we support javaws (patchset 2 hopefully) this can be removed as
the install process itself will DTRT at that point.

-- 
Greg Lewis                          Email   : glewis at eyesbeyond.com
Eyes Beyond                         Web     : http://www.eyesbeyond.com
Information Technology              FreeBSD : glewis at FreeBSD.org


More information about the freebsd-java mailing list