This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: java.security.Security patch
Andrew Haley wrote:
Marco Trudel writes:
> Marco Trudel wrote:
> > > It looks like GCJ's Security.java wasn't updated when importing
> > > classpath 0.92. This patch does that.
> > > The important thing is that all security providers get installed;
> > > even if the file ".../security/classpath.security" is not found
> > > (static builds ;-))
> > > This fixes javax.crypto to finally work. Mohans static initializer
> > > is no longer needed...
> > >
> > > Hints? Comments?
> > > I have no commiting rights and the copyright assignment papers have
> > > not yet arrived with mail. This might be a problem...
> >
> > The assignment is now set up.
> > Is the patch ok for trunk? If yes, can someone commit it?
>
> Anyone? I would prefer to have svn write access because that probably
> wasn't my last patch. So I don't have to wait until someone has time to
> do the committing work for me...
There's no ChangeLog.
2006-11-11 Marco Trudel <mtrudel@gmx.ch>
* java/security/Security.java
Imported the version from GNU classpath 0.92 (kept GCJ differences).
Is this a fix for static builds, or what?
Yes.
loadProviders() should already have done the right thing.
Not with static builds. There's no security file to parse and load the
providers. So there needs to be a fallback which adds them all.
Because Classpath 0.92 has new providers, they have to be added to the
fallback mechanism.
Marco