Hi
For one of my application I am trying to port
"RSA_verify()"(crypto/rsa/rsa_sign.c) function from openssl for verification of
the signature.
While compilation I am not able to find the definition of "d2i_X509_SIG()" and
"X509_SIG_free()" functions which is called from the "int_rsa_verify()".
Hi Richard,
CC =
/u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/gcc
CXX =
/u/build/build1/engtools/linux/2.6.18-8.el5/x86_64/gcc/versions/4.3.2/bin/g++
I was using these for openssl 1.1.0h and it compiled with this option "
enable-ec_nistp_64_gcc_128"
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 malfunction
For my testing I want to explore the behaviors of policies, policy constraints,
and policy mappings. I have figured out how to request and issue certs with
custom policy OIDs, but I haven't yet seen a method of granting an intermediate
cert with policy mappings. Can openssl do this? How? Th
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 well
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 lin
>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
