# Re: JavaKey question

Gigi Ankeny (Gigi.Ankeny@Eng)
Tue, 18 Nov 1997 10:10:08 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jan Luehe: "Re: missing docs"
- Previous message: Jan Luehe: "Re: Funny export restrictions for downloading JCE 1.2 API Specification"

    Date: Tue, 18 Nov 1997 10:10:08 -0800 (PST)

    From: Gigi Ankeny <Gigi.Ankeny@Eng>

    Subject: Re: JavaKey question

    To: java-security@web2.javasoft.com

Hi,

I see that you are trying to do "javakey -ic Duke Duke.x509".

The problem could be caused by the ftp software, which adds
some extra zeros at the end of the duke certificate.
Duke.x509 shows 506 bytes on my hard drive and I can import
it successfully. Check the size of the one you downloaded
and see if it got changed. Duke.x509 is a binary file and down
loading software could have erroneously processed it as ASCII file.

I am enclosing a copy of Duke.x509 here for you convenience.

If you have further problem, please let me know.

Thanks,

Gigi Ankeny

>
> I am trying to follow the example on the sun site with the Duke.x509
> certificate and install into my identity.db database. As I say I have
> been able to manipulate keys and certificates which have been created
> with the Javakey tool but not when using something which is externally
> created.
>
> I am using 1.1.4 on a PC (sorry) which I downloaded only recently. To
> copy the certificate I am just using standard ftp through netscape 4.
>
> I hope this information is sufficient, if not please dont hesitate to
> contact me.
>

--Pack_of_Dogs_997_000
Content-Type: APPLICATION/octet-stream; name="Duke.x509"; x-unix-mode=0644
Content-Transfer-Encoding: BASE64
Content-Description: Duke.x509
Content-MD5: /crMp39KhoC9rIxSjY7LTg==

MIIB9jCCAbYCAgPpMAkGBSsOAwINBQAwSzELMAkGA1UEBhMCVVMxGTAXBgNV
BAoTEFN1biBNaWNyb1N5c3RlbXMxEjAQBgNVBAsTCUphdmFTb2Z0IDENMAsG
A1UEAxMERHVrZTAaFws5NzAxMTcwMDAwWhcLOTgwMTE2MDAwMFowSzELMAkG
A1UEBhMCVVMxGTAXBgNVBAoTEFN1biBNaWNyb1N5c3RlbXMxEjAQBgNVBAsT
CUphdmFTb2Z0IDENMAsGA1UEAxMERHVrZTCB7jCBpgYFKw4DAgwwgZwCQQD8
poLOjhLKuibvzPcRDlJtsHiwXt7LzR60ogjzrhYXrgHzW5Gkfm32NBPF4S7Q
iZvNEyrNUNmRUb3EPuc3WS4XAhUAli7dzDacuo67Jg7mtqEm2TRuOMUCQGeE
cbJ6nPRO6RpJxRR9samq8kTwWkNNZIaTHS0UJxueNQMLcf1z2heQabMuKTVj
DhwgYjVNDaIKbEFuUL55TKQDQwACQF+kaHc7Cqejwp+QrSM9FGt/su51nZSs
P0pK/+kLOdKjwzwhbLfQNMAQqCenxS8XxXjjpxoe8wlEB6c3Yu1I7l0wCQYF
Kw4DAg0FAAMvADAsAhQnNksXCkRI6QVyK3tLiqeBPePR6QIULo092PR7+2vy
1aAOm4NKWHYei1w=

--Pack_of_Dogs_997_000--

------------- End Forwarded Message -------------

- Next message: Jan Luehe: "Re: missing docs"
- Previous message: Jan Luehe: "Re: Funny export restrictions for downloading JCE 1.2 API Specification"