On Fri, 2006-03-24 at 04:16 +1100, Raif S. Naffah wrote: > On Thursday 23 March 2006 23:18, Roman Kennke wrote: > > ...A jarsigner can well be > > implemented without JKS and have a Provider plugged in for different > > keystore formats. This would be done via the > > java.security.KeyStore.getInstance() method AFAICS. I think this is > > what Sun's jarsigner also does via the --provider and/or --storetype > > arguments. So my opinion is that we should have a jarsignder > > implementation that uses this API and the same options but a > > different default > > my implementation does that. OK, that is good. Do we actually have any alternative KeyStore format? If yes then we should as Roman says use this as default for now. I will send an email to FSF legal about using a (reimplementation) of the JKS format. Cheers, Mark -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url : http://developer.classpath.org/pipermail/classpath/attachments/20060324/5f3e7b3b/attachment.pgp
