> On Aug 17, 2018, at 10:52 PM, Daurnimator wrote:
>
> I understand the current design; but I'm left wondering why it has an
> additional store member when VERIFY_PARAMS has the field there
> already.
> The design would seem to be much cleaner if all criteria for
> verification are taken from
On 18 August 2018 at 03:18, Viktor Dukhovni wrote:
> On Fri, Aug 17, 2018 at 11:25:01PM +1000, Daurnimator wrote:
>
>> > When looking into https://github.com/wahern/luaossl/issues/140 I was
>> > surprised to learn that an SSL_CTX* (and SSL*) does not use many of
>> > the X509_STORE members.
>
> Th
Just created the PR: https://github.com/openssl/openssl/pull/7000
Thanks again for reporting this!
Nicola Tuveri
On Sat, 18 Aug 2018 at 00:15, Dmitry Belyavsky wrote:
> Dear Nicola,
> On Fri, Aug 17, 2018 at 11:00 PM Nicola wrote:
>
>> You just reproduced it :)
>>>
>>> Output for the file a.p
Dear Nicola,
On Fri, Aug 17, 2018 at 11:00 PM Nicola wrote:
> You just reproduced it :)
>>
>> Output for the file a.pem contains Private key, Public key and Parameter
>> set; the one for tmp.pem does not.
>>
>
> You are right, I was expecting some kind of error, and realized that there
> was some
>
> You just reproduced it :)
>
> Output for the file a.pem contains Private key, Public key and Parameter
> set; the one for tmp.pem does not.
>
You are right, I was expecting some kind of error, and realized that there
was something strange just after hitting the Send button, as usual!
Anyway,
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Eldiario Mexico
> Sent: Friday, August 17, 2018 12:51
> I really need your support , i've been trying to implement Openssl,
> cuase I need verify certifcates althrough OCSP and utilize this
> ceriticates to sign a doc
Hi All,
I am looking for an option in "openssl.cnf" file to control the signature
algorithms supported by an OpenSSL based TLS client application which it
lists in the "Client Hello" message and also the signature algorithm used
for signing the Client "CertificateVerify" message sent to the server
Dear Nicola,
You just reproduced it :)
Output for the file a.pem contains Private key, Public key and Parameter
set; the one for tmp.pem does not.
On Fri, Aug 17, 2018 at 6:42 PM Nicola wrote:
> I can't reproduce the issue, using latest master for both gost and openssl:
>
> /tmpram/gost > expo
On Fri, Aug 17, 2018 at 11:25:01PM +1000, Daurnimator wrote:
> > When looking into https://github.com/wahern/luaossl/issues/140 I was
> > surprised to learn that an SSL_CTX* (and SSL*) does not use many of
> > the X509_STORE members.
There are no plans to change the design. You can set the verif
Good Moorning
I really need your support , i've been trying to implement Openssl, cuase I
need verify certifcates althrough OCSP and utilize this ceriticates to sign
a docoument.
I'm developing on Visual Studio (Visual Basic) but, I can't found the .dll
Files , i dont find the correct way to ut
I can't reproduce the issue, using latest master for both gost and openssl:
/tmpram/gost > export OPENSSL_ENGINES=/tmpram/gost/engine/bin
/tmpram/gost > /tmpram/openssl-111-pre9-dev/bin/openssl pkey -engine gost
-pubout -text -in tmp.pem
engine "gost" set.
Private key:
28A509558DB1969DB89A4CB517D8
Hello,
I use my engine providing gost algorithms (
https://github.com/gost-engine/engine). It seems not to have any relevant
changes between 1.1.0 and current master, but the command
OPENSSL_CONF=engine.conf openssl pkey -pubout -text -in tmp.pem
works ok for 1.1.0 version and does not work for
On 12 July 2018 at 18:49, Daurnimator wrote:
> When looking into https://github.com/wahern/luaossl/issues/140 I was
> surprised to learn that an SSL_CTX* (and SSL*) does not use many of
> the X509_STORE members.
>
> e.g. a store has a X509_VERIFY_PARAMS field, however although an
> SSL_CTX* has a
> Personally, I see this as a showstopper re a release on Tuesday,
> but I think it's on all of us to come to an agreement, that is
> unless we actually do label and fix everything that needs fixing
> 'til Monday evening (Euro time)...
The planned Tuesday release was only another beta, albeit per
14 matches
Mail list logo
