Dav Coleman wrote:
>On Thu, 19 Aug 2004 11:16:21 +0100, Sean Radford
><sra...@ae...> wrote:
>
>
>>Dav Coleman wrote:
>>
>>
>>
>>>Is there any reason why CertStore is not Serializable, and why
>>>IssuerCertSelector is unsupported?
>>>
>>>
>>>
>>(Sorry for the delay in a response - very busy at my end)
>>
>>CertStore is not Serializable as it follows the JCE, is not remoteable,
>>and if it was then all the certificates that it contains would be
>>serialized... not a good thing with loads of certificates. Why would you
>>like it so?
>>
>>It does not currently support IssuerCertSelector, purely as this
>>selector was an afterthought (from my recollection) and so has not been
>>implemented as yet. Am I correct Sameer?
>>
>>
>>
>
>Well I'm still trying to figure out a way to store the keystore and
>certstore to the filesystem between application sessions. What I've
>done right now is make MyCertStore that is basically jsdsi.CertStore
>but Serializable and I'm storing the KeyPairs in a HashMap. Which is
>fine for now, I have 80% of the rest of a demo app to work on.
>
>I tried using the Sexp* writeReadable() stuff for the CertStore but I
>could figure out how to write out a certificate in that manner and
>then read it back in properly. I was getting bogged down in trying to
>figure that out and just gave up in order to actually get something
>working.
>
>
>
Have you looked at jsdsi.SexpMarshallingTest? That may help you.
Basically though, all you need is the jsdsi.sexp.ObjInputStream and the
corresponding ObjOutputStream. That works for all jsdsi.Obj classes, so
then its just a matter of dealing with the private key.
Regards,
Sean
--
Dr. Sean Radford, MBBS, MSc
sra...@ae...
http://www.aegeus-technology.com/
|
