Recently I noticed a similar problem: I couldn't import a certificate to Key Manager
(but the request was generated in the Key Manager, not with OpenSSL). The problem
symptom was incorrect password too.
The solution was to open the certificate in Notepad (or other ASCII application) and
dele
Recently I noticed a similar problem: I couldn't import a certificate to Key Manager
(but the request was generated in the Key Manager, not with OpenSSL). The problem
symptom was incorrect password too.
The solution was to open the certificate in Notepad (or other ASCII application) and
delete
have to talk to them in person
and, fortunately, I got The License To Kill... :-) I mean to do some minor
changes.
> It is even questionable whether you should add extensions
> about key usage or else.
Once again, thanks for your note
Ivan Dolezal
VSB-Technical University of Ostrava
__
Hello,
my question is very stupid, but I wasn't able to find the answer in
mail-archive.com:
Suppose that a user generates a certificate request, but enrolls partially
incorrect information in it (let's say (s)he filled the OU in other format
than how I'd like it to be; for example "Dept. 87
Thanks for a lot of material to read.
I'd like to repeat my question about importing CA certificate off-line. I
though openssl pkcs12 -export -in usercert.pem -inkey userkey.pem -certfile
cacert.pem -out user.p12 would work fine, but it didn't. When I tried to
add -chain, it told me that the cha
rederick Hirsch and Martin Ouwehand's work
enough. I found out that reading OpenSSL man pages isn't very helping once
when you need some theoretical knowledge. Is there some "intermediate"
literature that you would recommend me so you&
this file with small script as x-x509-user-cert to Netscape, I
CAN send signed e-mail.
What's wrong with my PKCS#12 file? Any idea, what else could be wrong?
===> Thanks in advance! <===
Ivan Dolezal
