This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Package-private access checking in GCJ 3.3

From: Tom Tromey <tromey at redhat dot com>
To: Ranjit Mathew <rmathew at hotmail dot com>
Cc: java at gcc dot gnu dot org
Date: Tue, 24 Jun 2003 07:03:32 -0600
Subject: Re: Package-private access checking in GCJ 3.3
References: <3EECA38A.940157DC@hotmail.com><87n0gjqhrl.fsf@fleche.redhat.com><bck2ig$8k2$1@main.gmane.org><3EEE6DB9.D75D072F@hotmail.com><3EF5C00B.8C47F8A3@hotmail.com>
Reply-to: tromey at redhat dot com

>>>>> "Ranjit" == Ranjit Mathew <rmathew@hotmail.com> writes:

Ranjit> In any case, as Tom predicted, this kludge still exposes
Ranjit> a number of illegal accesses to package-private members 
Ranjit> in libgcj.

How very bogus of us.

Let's definitely fix these.  However, one issue to look at is whether
exposing these fields and methods will cause us security problems in
the future.  If so, we may need to take some other action, for
instance moving classes into a different package, or moving accesses
into native code.

Tom

References:
- Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew
- Re: Package-private access checking in GCJ 3.3
  - From: Tom Tromey
- Re: Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew
- Re: Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew
- Re: Package-private access checking in GCJ 3.3
  - From: Ranjit Mathew

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]