|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
Limited mainly to untrusted applets
Submitted by metatech on Fri, 09/02/2011 - 10:13.
Tags:
Back to:
www.javaworld.com/javaworld/jw-12-1998/jw-12-securityrules.html.
Although the article does not mention it explicitly, these recommndations are primarily aimed for applications running as untrusted applets in a browser. Trusted applets or applications using the normal system classpath (Java desktop applications or Java EE applications) can anyway use the Java reflection API to bypass most of those restrictions (by calling for instance "setAccessible").