Scott Neugroschl wrote in :
|Steffen Nurpmeso, Tuesday, September 25, 2018 11:57 AM
|> The RFC 7468 term "parsers SHOULD ignore whitespace and other non-
|>base64 characters" makes me wonder.
|
|The relevant clause is a few sentences up: "Data before the encapsulation \
|boundaries are
> -Ursprüngliche Nachricht-
> In the meantime:
>
>$ perl -ne 'print if (/^-BEGIN/../^-END/);' foo.pem |
>openssl asn1parse
>
> > On Sep 25, 2018, at 1:15 PM, Hubert Kario wrote:
> >
> > then it looks like the parser used in asn1parse -inform pem is non-
> >
Steffen Nurpmeso, Tuesday, September 25, 2018 11:57 AM
> The RFC 7468 term "parsers SHOULD ignore whitespace and other non-
>base64 characters" makes me wonder.
The relevant clause is a few sentences up: "Data before the encapsulation
boundaries are
permitted, and parsers MUST NOT
Viktor Dukhovni wrote in <5d44b1e9-cdb3-49c1-a3e5-4ab0d889c...@dukhovni.org>:
|That particular parser tries to parse an arbitrary single
|PEM-encoded object, rather than a first object of a particular
|type (as with "pkey", "req", "x509", ...). The code for that
|is more specialized, and does
That particular parser tries to parse an arbitrary single
PEM-encoded object, rather than a first object of a particular
type (as with "pkey", "req", "x509", ...). The code for that
is more specialized, and does support leading free-form text.
While it could skip to the first boundary, and a
On Tuesday, 25 September 2018 00:55:16 CEST Viktor Dukhovni wrote:
> > On Sep 24, 2018, at 6:25 PM, Scott Neugroschl wrote:
> >
> > I tried googling, but couldn’t find an answer to this…
> >
> > I came across a certificate that had some text garbage before the
> > BEGIN CERTIFICATE
>On Sept 24, 2018, at 3:55 PM, Viktor Dukhovni wrote:
>> On Sep 24, 2018, at 6:25 PM, Scott Neugroschl > wrote:
>>
>> I tried googling, but couldn’t find an answer to this…
>>
>> I came across a certificate that had some text garbage before the BEGIN
>> CERTIFICATE line.
>>
>> I
> On Sep 24, 2018, at 6:25 PM, Scott Neugroschl wrote:
>
> I tried googling, but couldn’t find an answer to this…
>
> I came across a certificate that had some text garbage before the BEGIN
> CERTIFICATE line.
>
> I know that the cert is defined as the data between the
I tried googling, but couldn't find an answer to this...
I came across a certificate that had some text garbage before the BEGIN
CERTIFICATE line.
I know that the cert is defined as the data between the delimiters. Do the
specs say anything about data before the BEGIN delimiter?
Hi OpenSSL Users
Can someone tell me API using which I can convert certificates from one
format to another? I know that the openssl command can be used for the same
but that is not an option for me...I have to do it in code
Thanks
Rahul
your stuff is here..
http://www.openssl.org/docs/crypto/pem.html
happy reading !
On Mon, May 20, 2013 at 12:20 PM, Rahul Godbole rahulmg1...@gmail.comwrote:
Hi OpenSSL Users
Can someone tell me API using which I can convert certificates from one
format to another? I know that the openssl
Someone know if there is an simple OpenSSL function that say format (PEM or DER) of a
given certificate?
Tnx,
Francesco Dal Bello
__
OpenSSL Project http://www.openssl.org
User Support Mailing
How can I find out the format of a certificate from a C program?
thanks,
--
vijo
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated
Sorry to be little of the topics of the list but my need of information is
urgent. I appology. I do deal with OpenSSL and therefore I know that MANY
experts (or even GURUs) read this list.
I'd need to know, how to create a server certificate in PSE-format? (PKCS12
I ques) I'd need that
As I understand it, the email address is stored in an X509 certificate as
CN=A N Other/Email=email address
My question is, what is permissible as email address? Must it purely
be user@mx , or are comments and angle bracket formations permissible --
e.g. Jack Straw [EMAIL PROTECTED] (Home
In principle impossible, since the PKCS#10 request contains a
signature with the private key of the requestor.
But if you have both, the cert and the corresponding private
key, you can try to play with
openssl x509 -x509toreq -signkey
If you asked about how to do it in C code then look at the
Holger Reif wrote:
In principle impossible, since the PKCS#10 request contains a
signature with the private key of the requestor.
But if you have both, the cert and the corresponding private
key, you can try to play with
openssl x509 -x509toreq -signkey
If you asked about how to do it
17 matches
Mail list logo
