FYI: Java Enterprise warning: "How to break a Sun box & repair it again"

Question

Hi there,
Because of the news that the Java enterprise will be opened up I decided to replace the version I got on my 03/05 media kit with the one being made available right now. Nothing wrong there but the upgrade can be a little tricky since you're adviced to do this manually. Nothing wrong there but I decided to uninstall the current version (Q1) and then re-install the current one (Q4). Only problem; only after I tried installing the Directory server from the current release and uninstalled it.
This resulted in a little chaos, which was entirely my fault. After entirely uninstalling the Q4 release I tried to remove the Q1 parts. But because the uninstall program (/var/sadm/prod/SUNWentsys4) was already removed I didn't have much alternatives (or so I thought).
So last night I drank a little too much beer and then went on the "cleaning up" rampage. In my drunken mind I figured "remove all Java enterprise components = uninstalling the whole product". While this idea might make sense, it starts to become an horror story when you realize, like I now do, that the Java enterprise system replaces certain packages on your Solaris 10 system. Packages like, for example, SUNWtls, SUNWjss and (don't laugh) SUNWcsl. So what happens if you simply manually pkgrm the lot ? Well, you'll do the math but I'll give you a little hint by saying that SUNWcsl has something to do with PAM :-)
So here I was; behind my nice Blade 100 with CDRom & 512Mb memory (soon to be doubled) but with a PC USB keyboard and optical mouse. Its a little hard to press stop-a using a PC keyboard and I got stuck since I removed some very important packages. Reinstall? I don't think so, we're using Unix here and there is always a way around your misery.
In my case I merely attached a nullmodem cable to the Blade, hooked it onto my Linux workstation, removed keyboard & mouse and started minicom (9600N81). After putting the first install CD (thanks Sun :)) in the drive I booted the system, send a break, booted the CD and exited the installer. Now I was basicly home free since I could mount my system's slices in /tmp/rescue, access the LAN and use pkgadd (pkgadd -d ./ -R /tmp/rescue) to manually re-install the missing packages which disallowed me from logging in. (tip: if you just need a rescue environment quickly just "boot cdrom -s" for single user mode).
And here I am again, back from the wrecked, typing and studying (Java) on my trusted Blade box again. The moral of this story: Don't drink & "quickly" admin a Sun server, its not worth the risk.
I've picked up these hints from several websites but didn't encounter anything like this in these forums. I have to admit not having searched very hard (I only googled and used SunSolve) but I figured that this isn't highly classified info so decided to dump it here too for everyone to see. Just remember that doing something horribly stupid like I did doesn't always mean you have to re-install. You'll learn and gain much more experience by fixing things.

Answer 1

You don't have a problem.
The MS jvm is not present in the computer. If it was, it would show in IE Tools...Advanced list along with the Sun jvm (There would also be an entry for the MS console in the IE View menu - as opposed to the entry that the Sun console places in the IE Tools menu.)
The Sun Control Panel is ignorant of the MS jvm (if it's installed).
I don't use Firefox, but understand that the Control Panel is also ignorant of it; its install/activation is currently done outside of the Control Panel. You can probably find more info at the Firefox site.
The vulnerability existed in both the MS and Sun (and other) jvm's but you are using a fixed version, as this reference lists:
http://www3.ca.com/securityadvisor/vulninfo/Vuln.aspx?ID=6885