public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "gandalf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager
Date: Thu, 16 Dec 2010 19:48:00 -0000	[thread overview]
Message-ID: <bug-46774-8172-smrFQ2PTRc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46774-8172@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

--- Comment #2 from gandalf at gcc dot gnu.org <gandalf at gcc dot gnu.org> 2010-12-16 19:48:12 UTC ---
Author: gandalf
Date: Thu Dec 16 19:48:07 2010
New Revision: 167952

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167952
Log:
PR libgcj/46774: Create dynamic ProtectionDomain instances which check the
system policy.

2010-12-13  Andrew John Hughes  <ahughes@redhat.com>

    PR libgcj/46774
    * libjava/java/security/VMAccessController.java:
    (DEFAULT_CONTEXT): Create ProtectionDomain with
    four argument constructor (arguments are the same
    as those implied by the two argument constructor).
    (getContext()): Create ProtectionDomain instances
    with four argument constructor using a null Principal
    array (as before) but including the classloader, which
    was always null before.


Modified:
    trunk/libjava/ChangeLog
    trunk/libjava/classpath/lib/java/security/VMAccessController.class
    trunk/libjava/java/security/VMAccessController.java


  parent reply	other threads:[~2010-12-16 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  0:35 [Bug libgcj/46774] New: " gnu_andrew at member dot fsf.org
2010-12-03  0:35 ` [Bug libgcj/46774] " gnu_andrew at member dot fsf.org
2010-12-16 19:48 ` gandalf at gcc dot gnu.org [this message]
2010-12-20 18:20 ` gandalf at gcc dot gnu.org
2010-12-20 18:32 ` gnu_andrew at member dot fsf.org

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=bug-46774-8172-smrFQ2PTRc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).