> > I beleive we need to go through our Coding Standards document,
> > purge some items (since they do not apply to modern JVMs) and
> > incorporate ideas from this list of documents:
> >
> > Twelve rules for developing more secure Java code
> > -------------------------------------------------
> > http://www.javaworld.com/javaworld/jw-12-1998/jw-12-securityrules_p.html
>
> While I belive that the rules are appropriate for some
> situations, I do not
> think that they approach the type of security needed in Avalon from the
> right angle.
The Leo's are in agreement here. While the article is kinda correct, they're
not especially valid with regards to an OS project (IIRC).
> I assume that there are people on this list with more experience in this
> field, so what do you say?
not much experience here either, but this sounds pretty right to me =)
> /LS
LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
