From: Gary Benson <gbenson@redhat.com>
To: mauve-discuss@sources.redhat.com
Subject: SecurityException throwpoint audit
Date: Mon, 21 Nov 2005 16:58:00 -0000 [thread overview]
Message-ID: <20051121165809.GB12340@redhat.com> (raw)
Hi all,
I've been trying to work out how to test that permissions are checked
at every point they ought to be. There's a table of every such point
here:
http://java.sun.com/j2se/1.4.2/docs/guide/security/permissions.html#PermsAndMethods
Some of these already have tests, but most probably do not. Before I
start creating tests I'm thinking that we need some way to correlate
mauve tests with the throwpoints on this (and future) lists.
How would people feel if I numbered the throwpoints on the above list
and noted them in their corresponding tests in some easily parsable
form (probably in comments like Tags are already). That way whether a
throwpoint is tested (and the location of the test) can be found with
a simple grep.
For simplicity I'd probably number the 1.4.2 list from 1-whatever.
Checks added in 1.5 can be added at the end of the list.
It would be convenient if we made a version of the above list
annotated with the throwpoint numbers, but obviously such a thing
could not be distributed. It should be possible to write a script
that would download and annotate the list for local use.
Does this sound reasonable?
Cheers,
Gary
next reply other threads:[~2005-11-21 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 16:58 Gary Benson [this message]
2005-11-22 16:27 ` Gary Benson
2005-11-25 0:02 ` Mark Wielaard
2005-11-25 19:30 ` Tom Tromey
2005-11-28 14:04 ` Gary Benson
2006-05-17 20:39 Olli Vertanen
2006-05-18 11:40 ` Gary Benson
2006-05-24 12:53 ` Olli Vertanen
2006-06-02 11:55 ` Gary Benson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051121165809.GB12340@redhat.com \
--to=gbenson@redhat.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).