Hi there, I have looked into this area lately too. 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 /Roman Am Donnerstag, den 23.03.2006, 12:47 +0100 schrieb Audrius Meskauskas: > Maybe one person can look into that code, write the brief draft of the > documentation and then another can implement it using that documentation > only? This would be the possibility to work with formats for that there > is no other specification available apart from the released piece of the > implementing code. > > >> > >>the tool reads and uses private and public cryptographic data from a > >>keystore that is in a proprietary format: "JKS" from Sun. the code i > >>use to do the reading from such a keystore* is available at > >><http://metastatic.org/source/JKS.java>. > >> > >>i'd like a ruling on whether it's ok to import and use this code in GNU > >>Classpath. > >>TIA + cheers; > >>rsn > >> > > > >Unfortunately no. > > > > > (...) > > >Cheers, > > > >Mark > > > > > >
