Re: java.security.Security loading providers from ltdl managed symbol tables?

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Erik" == Erik Poupaert <erik.poupaert@freestyler-toolkit.org> writes:

Erik> The JDK1.3 Bouncy Castle overlaps partially, but only with
Erik> interfaces apparently, so no double registration errors get
Erik> triggered.

That's surprising.  I think interfaces should also cause a crash.

Erik> String base = System.getProperty("gnu.classpath.home.url");
Erik> loadProviders(base, System.getProperty("gnu.classpath.vm.shortname"));
Erik> loadProviders(base, "classpath");

Erik> In my impression, none of the natively compiled providers will
Erik> be loaded with the code above. It looks as if only classpath
Erik> (bytecode) classes will be loaded, while the classes available
Erik> through the executable's own symbol tables (or even linked
Erik> shared objects) will fail to be loaded.

I don't think so.  loadProviders looks for a .security file at the
aforementioned URLs; this is a properties-style file that lists all
the security providers.  You should be able to compile and link in
such a .security file: first compile it with --resource, and when you
link, use something like -Dgnu.classpath.home.url=core:/

Tom