Hi cdensha,
you're right. The XProtect update (the plist in this case) is not updated via a SoftwareUpdate. It updates via a launchdeamon or semething when the system starts up. I don't know exactly at the moment, haven't looked for.
I don't want to brake the update process of XProtect, as it could be useful to protect the system to run any maliciuos software.
To get the WebPlugin working again, you could try to run a script via a launchdaemon as root.
at the moment, we (our Company Site) do not need the runtime, only the webplugin so i managed it via a script launched by a launchdeamon:
Script located in /scripts/java-workaround.sh
Code:
---
#!/bin/bash
#changing XProtect.meta.plist to allow only the latest java WebPlugin Version
defaults write /System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/XProtect.meta. plist JavaWebComponentVersionMinimum "1.6.0_37-b06-434"
---
launchdeamon located in /Library/LaunchDeamons/com.own.java-workaround.plist
Code:
---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST
1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>JavaWorkaround</string>
<key>ProgramArguments</key>
<array>
<string>/scripts/java-workaround.sh</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>UserName</key>
<string>ROOT</string>
<key>GroupName</key>
<string>WHEEL</string>
<key>StartInterval</key>
<integer>60</integer>
</dict>
</plist>
---
The launchdeamon executes the script every 60 seconds, because sometimes the lauchdeamon executed the script before the XProtect.meta.plist was downloaded from apple, so the download has overwritten the workaround. So i decided to run it every 60 seconds to overwrite the download again 😉
With the script, i only set the WebPlugin minimum Version to the latest from Apple available one. The Runtime is still blocked, so you won't be able to run java executables like jar-files etc.
Hope that helps...
Regards,
Shirkan