Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.security > #39
| From | "towardajavastandard" <towardajavastandard@THRWHITE.remove-dii-this> |
|---|---|
| Subject | Protecting packages |
| Message-ID | <1193401885.908882.51290@k79g2000hse.googlegroups.com> (permalink) |
| Newsgroups | comp.lang.java.security |
| Date | 2011-04-27 16:07 +0000 |
| Organization | TDS.net |
To: comp.lang.java.security To people writing production software: Do you actually prevent package access by adding certain packages to the package.access property of the java.security file, as described here: http://java.sun.com/developer/JDCTechTips/2001/tt0130.html Or do you prefer sealing jar files? ----- Your response will help in developing a java secure coding standard. --- * Synchronet * The Whitehouse BBS --- whitehouse.hulds.com --- check it out free usenet! --- Synchronet 3.15a-Win32 NewsLink 1.92 Time Warp of the Future BBS - telnet://time.synchro.net:24
Back to comp.lang.java.security | Previous | Next | Find similar
Protecting packages "towardajavastandard" <towardajavastandard@THRWHITE.remove-dii-this> - 2011-04-27 16:07 +0000
csiph-web