Hello everybody,
 
I'm new in this list and I have a question, maybe a newbie question for most of the users, but I'm in a big trouble and need help on this matter. This is the problem:
 
I have to add 3 new OIDs to my issued certificates, so I added them in the openssl.cnf config file this way:
 
in the new oids section I have this:
 
direccion = 2.5.4.9
nit = 1.3.6.1.4.1.4710.1.3.2
cedula = 1.3.6.1.4.1.4710.1.3.1
 
In the policy match section I have this:
 
direccion  = optional
cedula   = optional
nit    = optional
 
 
In the [ req_distinguished_name ] section I have this:
 
direccion   = Direccion
cedula    = Cedula
nit    = Nit
 
 
I guess this is ok, but after issuing my certificate, I'm getting undesired characters in the values of these new OIDs for example, this certificate has the 3 new OIDs I need, when I open the certificate in Windows (the OS we need to use) I get this output in the subject:
 

Número de serie = 9

1.3.6.1.4.1.4710.1.3.2 = 1      <-------------------------------The 2 first characters are garbage

1.3.6.1.4.1.4710.1.3.1 = 1      <-------------------------------The 2 first characters are garbage

STREET = cra 23                   <-------------------------------The 2 first characters are garbage

CN = Prueba 1 cert

OU = Internet

O = Ubiquando

L = Bogota

S = Cundinamarca

 
What should I do to avoid these annoying characters in the value of my special OIDs??
 
Am I doing something wrong when I add the OIDs?
 
In the [ req_distinguished_name ] section I have also done this:
 
direccion   = UTF8:Direccion
cedula    = UTF8:Cedula
nit    = UTF8:Nit
 
But this doesn't change this strange behaviour.
What do you recommend me? is it posible for the requests I receive in PEM that contain latin characters like á, ñ, etc.
The request are being generated with openssl and the -utf8 option
 
I'm attaching my openssl.cnf file
 
Thanks a lot for any help,
Johnny
 
 



Correo Yahoo!
Comprueba qué es nuevo, aquí
http://correo.yahoo.es

Attachment: openssl.cnf
Description: 3327650371-openssl.cnf

Reply via email to