I'd like to see some kind of OID-parsing scripting capability --
instead of just describing the OID with its name, put in some kind of
script capability to parse the OID information itself [even if it's
'[OPAQUE]' for some data, such as alternate signatures or encrypted
information included in the
Phil Dibowitz wrote:
(sorry if this is a dup, I never saw my previous email come through)
I was hoping to use otherName to store some information in my
certificates... but it seems it's not all that supported:
[EMAIL PROTECTED] tmp]$ openssl x509 -in test.crt -noout -text
...
On Fri, Jan 06, 2006, Phil Dibowitz wrote:
I lost the reply but Stephen Henson noted:
Currently the otherName component isn't displayed with the X509
print
routines.
You can however include arbitrary otherName data by specifying the
appropriate
ASN1 syntax in the config file.
(sorry if this is a dup, I never saw my previous email come through)
I was hoping to use otherName to store some information in my
certificates... but it seems it's not all that supported:
[EMAIL PROTECTED] tmp]$ openssl x509 -in test.crt -noout -text
...
X509v3 Subject Alternative
On Wed, Dec 21, 2005, Phil Dibowitz wrote:
(sorry if this is a dup, I never saw my previous email come through)
I was hoping to use otherName to store some information in my
certificates... but it seems it's not all that supported:
[EMAIL PROTECTED] tmp]$ openssl x509 -in test.crt -noout
