Java 7u51 blocks unsigned applets and tightens RIA security AI-researched
Dependency: Java applet security model
Oracle Java 7u51 tightened Rich Internet Application security, blocking unsigned/self-signed applets at higher settings and requiring manifest attributes — breaking many Java-based net artworks even before browsers removed plugins entirely.
Affected Artworks
Riccardo Zanardelli
Java applet embedded in web page. Unsigned/legacy packaging may be blocked under tightened Java security.
John Klima
Java applet realtime visualization. Blocked or warning-gated under 7u51+ security changes.
Victor Liu
Java applet UI. Security prompts/blocks prevent normal access.
Roberto Echen
Java applet. Requires compliant signing/manifest to run under 7u51-era security.
Mark Tribe, Alex Galloway & Martin Wattenberg
Java applet for constellation generation. Security gating and later plugin removal.
Fixes & Mitigations
- Workaround: Re-sign applets with valid code-signing certificates and add required manifest attributes (historically feasible).
- Emulation: Preserve via VM snapshots and local network isolation; document user prompts and security UX.
Java 7u51 introduced stricter requirements (permissions attributes, blocking unsigned applets at higher security), increasing friction for applet-based works. This created a “pre-extinction” even before NPAPI/plugin removal: users saw warnings or outright blocks.
Notes
This event is useful on the timeline because it shows how security policy changes can “kill” works before a formal runtime EOL.