On Mon, Sep 23, 2019 at 05:56:17PM +, (KSTROS) - Jayron Alberth Costa
Castro wrote:
> I have already read the documentation, but it only shows how to insert a
> single otherName field and so I have done several tests, without success.
subjectAltName = @altnames
[al
?I have already read the documentation, but it only shows how to insert a
single otherName field and so I have done several tests, without success. :(?
JAYRON ALBERTH COSTA CASTRO
Network Infrastructure Engineer
Kstros Treinamento e Tecnologia Ltda
Cel.: +55 (85) 98162-3076
skype
ucture three structures like otherName and I can't create
> it via openssl command line. I currently use version 1.1.1d and wanted help
> in this regard.
>
> I take the opportunity to know how I can capture the content of fields
> provided via the attributes structure, to assemble the req
Hi friends, I need some help, because I need to create within the
subjectAltName structure three structures like otherName and I can't create it
via openssl command line. I currently use version 1.1.1d and wanted help in
this regard.
I take the opportunity to know how I can capture the content
On 14/08/2017 21:38, Robert Moskowitz wrote:
On 08/14/2017 03:28 PM, Jakob Bohm wrote:
On 14/08/2017 20:55, Robert Moskowitz wrote:
On 08/14/2017 02:04 PM, Salz, Rich via openssl-users wrote:
➢ Is there anyway to display the basic ASN.1 structure here so I can
see
what was stored in
On 08/14/2017 03:28 PM, Jakob Bohm wrote:
On 14/08/2017 20:55, Robert Moskowitz wrote:
On 08/14/2017 02:04 PM, Salz, Rich via openssl-users wrote:
➢ Is there anyway to display the basic ASN.1 structure here so I can
see
what was stored in the cert?
openssl asn1parse
Humpf. I
On 14/08/2017 20:55, Robert Moskowitz wrote:
On 08/14/2017 02:04 PM, Salz, Rich via openssl-users wrote:
➢ Is there anyway to display the basic ASN.1 structure here so I can see
what was stored in the cert?
openssl asn1parse
Humpf. I looked at that a few times and did not see the
On 08/14/2017 02:04 PM, Salz, Rich via openssl-users wrote:
➢ Is there anyway to display the basic ASN.1 structure here so I can see
what was stored in the cert?
openssl asn1parse
Humpf. I looked at that a few times and did not see the obvious. Sigh.
So some progress. using -i
➢ Is there anyway to display the basic ASN.1 structure here so I can see
what was stored in the cert?
openssl asn1parse
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
I am now working on using the othername option. I see it go in, but I
can't display it. All I get is:
X509v3 Subject Alternative Name:
othername:
I seem to recall encountering some way to display this in a google
search, but I have not found that search yet in my
It looks like OpenSSL always shows unsupported for a subjectAltName of
otherName.
The string that was written (both via M2Crypto, and directly at the
commandline via openssl.cnf):
1.2.3.4;UTF8:some other identifier
Dumped (openssl x509 -in test.crt -noout -text):
c3:88
in the certificate].
I haven't got the faintest idea how to implement that in OpenSSL, though. :(
-Kyle H
On 1/6/06, Dr. Stephen Henson [EMAIL PROTECTED] wrote:
On Fri, Jan 06, 2006, Phil Dibowitz wrote:
I lost the reply but Stephen Henson noted:
Currently the otherName component isn't
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
Hello all,
Date: Fri, 2 May 2003 14:12:59 +0200
Dr. Stephen Henson wrote:
However based on that encoding it looks like the correct syntax for the ASN1
form of otherName is:
subjectAltName=otherName:2.5.5.5;UTF8:2.16.528.1.1003.1.4.3.4.2.1-0.1.2.3.4
Steve.
I'm trying on openssl_SNAP0529
On Sat, May 31, 2003, Kikuyo Nagamatsu wrote:
Hello all,
Date: Fri, 2 May 2003 14:12:59 +0200
Dr. Stephen Henson wrote:
However based on that encoding it looks like the correct syntax for the ASN1
form of otherName is:
subjectAltName=otherName:2.5.5.5;UTF8:2.16.528.1.1003.1.4.3.4.2.1
Dr. Stephen Henson wrote:
On Sat, May 31, 2003, Kikuyo Nagamatsu wrote:
Hello all,
Date: Fri, 2 May 2003 14:12:59 +0200
Dr. Stephen Henson wrote:
However based on that encoding it looks like the correct syntax for the ASN1
form of otherName is:
subjectAltName=otherName:2.5.5.5;UTF8
Hi,
Is it possible to give an OID as subjectAltName
eg OtherName=1.3.6.1.4.1.311.20.2.3
Regards,
Geert
__
OpenSSL Project http://www.openssl.org
User Support Mailing List
On Thu, Feb 27, 2003, Geert Van Muylem wrote:
Hi,
Is it possible to give an OID as subjectAltName
eg OtherName=1.3.6.1.4.1.311.20.2.3
The registered ID version (RID) is for a single OID. OtherName is intended to
be catch all for anything else it consists of an OID and *anything* where
but in hex code. I see this : ' other
name: 1.3.6.1.4.1.311.25.1=0A1A010306. '
It's possible to make use DER code or I must modify OpenSSL source code?
You can use dNSName in a config file (see doc/openssl.txt).
For otherName the actual OID you use has to be understood by the other
22 matches
Mail list logo
