Cryptography provider

[Joerg Brunsmann]

--- Tom Tromey <tromey@redhat.com> wrote: 

> Mark> I thought that all java.security problems in Classpath/libgcj
> Mark> were fixed now. What is the remaining known problem in this
> Mark> area?
> 
> PR 7416.  At startup we reference a file called "GNU libgcj.security".
> The fix is to add the VM shortname feature we talked about a couple
> weeks ago.

The code in java/security/Security.java looks like:

  static
  {
    loadProviders(System.getProperty("java.home"),
		  System.getProperty("java.vm.name"));
    loadProviders(System.getProperty("gnu.classpath.home"), "classpath");
  }
  ...
  private static void loadProviders(String dir, String vendor)
  {
    ...
    String separator = System.getProperty("file.separator");
    String secfilestr = (dir +
			 separator + "lib" +
			 separator + "security" +
			 separator + vendor + ".security");
    ...

1. What's the rationale for loading two different provider files?
2. Why doesn't the 'libgcj.security' file define a provider?
3. What's the rationale for loading two different provider files
   if one file doesn't define a provider?
4. Is the limited classpath provider used from other libgcj/classpath
   code? If not, it might be a good idea to remove the code and give
   the user a hint to install another fully implemented provider?

Jörg

__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Weihnachts-Einkäufe ohne Stress! http://shopping.yahoo.de