Educause Security Discussion mailing list archives

Re: Java vs. Banner


From: Sara Rodgers <skr5 () LEHIGH EDU>
Date: Thu, 21 Feb 2013 16:52:12 -0500

We are recommending that all users update to the most recent version of
Java 7 and for our Banner form users to add the runtime parameter string
(-Djava.vendor="Sun Microsystems Inc.") to make forms think it is running
an older version of Java. The only downside we have found is that the tab
key does not function on the initial login screen, but will function
normally once logged into INB.

Are others using this or have you found issues with this recommendation?

Thanks,
Sara


On Thu, Feb 21, 2013 at 1:08 PM, David Curry <david.curry () newschool edu>wrote:

As those of you at schools using Banner know, Ellucian has still not
certified Banner to run on Java 7; Java 6 (including the browser plug-in)
must be installed on end users' desktops. Java 6, of course, has reached
the end of its public update period, which means any future updates after
the end of this month will come through Ellucian rather than Oracle (or so
they tell us).

Aside from the increased difficulty of trying to keep a down-rev version
of Java installed on systems used by Banner users, especially since our
users have admin rights and are therefore free to update Java when they
want and will do so if another application asks them to, we are of course
concerned that maintaining a down-rev version of the Java plug-in will
expose these systems to increased risk of compromise because of security
vulnerabilities. This is particularly worrying because, of course, the
people who use Banner are also the people who work with lots of personally
identifiable information.

Java 7 support from Ellucian doesn't appear to be imminent, so we believe
we need to find a medium-term solution to this problem that lets our Banner
users continue to use Java 6, but does not expose them to increased risk by
allowing them to use a browser containing the Java 6 plug-in to access the
Internet. We have some preliminary thoughts on ways to address the issue,
ranging from "use this browser to access Banner and that browser to access
the Internet" (which doesn't come with a very high assurance level) to
installing Windows XP Compatibility Mode on all Banner users' machines and
running Banner+Java 6 in a virtual machine (a lot of work to implement).

Before we go one way or the other, we thought we'd ask the list -- what is
your school doing in response to the whole Java vs. Banner thing?

Thanks,
--Dave


--

*DAVID A. CURRY, CISSP* • DIRECTOR OF INFORMATION SECURITY

*THE NEW SCHOOL* • 55 W. 13TH STREET • NEW YORK, NY 10011

+1 212 229-5300 x4728 • david.curry () newschool edu




-- 

Sara K. Rodgers
Manager, Security and Identity Management
Library and Technology Services
Lehigh University
Bethlehem, PA 18015610-758-2008

Current thread: