[openssl-users] Functions for retrive public key from x509 cert

Christian Adja christian_adja at yahoo.it
Tue Mar 28 09:25:35 UTC 2017

Dear friends,
Someone can tell me what function is called for retrieve public key from x509 cert? in the case of EC public key? 

Best regards. 

    Il Lunedì 27 Marzo 2017 10:26, "openssl-users-request at openssl.org" <openssl-users-request at openssl.org> ha scritto:

 Send openssl-users mailing list submissions to
    openssl-users at openssl.org

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
    openssl-users-request at openssl.org

You can reach the person managing the list at
    openssl-users-owner at openssl.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of openssl-users digest..."

Today's Topics:

  1. SSL cipher list to disable TLS 1.0 & TLS 1.1 (Hema Murthy)
  2. In ssl3_write_bytes, some checks related to hanlding write
      failure are missing (Raja ashok)


Message: 1
Date: Mon, 27 Mar 2017 11:59:16 +0530
From: Hema Murthy <chintuhema at gmail.com>
To: openssl-users at openssl.org
Subject: [openssl-users] SSL cipher list to disable TLS 1.0 & TLS 1.1
    <CACWQscaOQt0zX9jm8ydTPTq9Joym3UtUrHyrfd9ggLds2UdQfg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"


My system is

FreeBSD 10.2

OpenSSL 1.0.2h

lighttpd :lighttpd-1.4.23

Am trying to disable TLS1.0 and TLS1.1 through lighttpd.conf

but am not sure of what is the equivalent cipher list to be used.

I followed the below link and it didnt work for me.

In case of Appweb Server,I was able to successfully disable TLS1.0 & Above
and TLS1.1 & Above using

SSLProtocol = "ALL -SSLV2 -SSLV3 -TLSV1"

SSLProtocol = "ALL -SSLV2 -SSLV3 -TLSV1.1"

But the same cipher is not working for lighttpd.

Am very new to this and do not know how to proceed further.

Would be great and appreciate if anyone can give me pointers on this.

Please help.

Thanks & Regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170327/02b8fb3b/attachment-0001.html>


Message: 2
Date: Mon, 27 Mar 2017 08:25:16 +0000
From: Raja ashok <raja.ashok at huawei.com>
To: "openssl-users at openssl.org" <openssl-users at openssl.org>,
    "openssl-dev at openssl.org" <openssl-dev at openssl.org>
Subject: [openssl-users] In ssl3_write_bytes, some checks related to
    hanlding write failure are missing
Message-ID: <FDFEA8C9B9B6BD4685DCC959079C81F5E19315C4 at blreml509-mbx>
Content-Type: text/plain; charset="gb2312"


I feel there is a check missing in ssl3_write_bytes, in case of handling write failure.

Consider SSL_write is called with 20000 bytes buffer, then internally in ssl3_write_bytes we try to send it as two record (16384 and 3616). If TCP send failed for the second record then we store the states internally (wnum, wpend_tot and wpend_buf) and return back the result.

Later application has to call SSL_write with same buffer, if it calls with different buffer of length 100 byte then we fail that in ssl3_write_bytes using the check (len < tot).

But consider application calls with buffer of size 18000 bytes and SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER is enabled. Then (len < tot) will not succeed as tot is 16384. Then it will call ssl3_write_pending to send the remaining 3616 record. If it succeeds we are incrementing tot, (tot += i). Now tot will have 20000.

Later there is a check (tot == len), this will not succeed. Then directly we are doing n = (len - tot), this will overflow and store a value close to 2^32 in n. Then it will cause out of bound access to the application buffer "buf".

I hope we should have one more check (len < (tot + s->s3->wpend_tot)) before calling ssl3_write_pending.

    if ((len < tot) || (len < (tot + s->s3->wpend_tot))){
        return (-1);

Note : I am referring 1.0.2k version of OpenSSL.



Raja Ashok V K
Huawei Technologies
Bangalore, India
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170327/e8f3d72a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6737 bytes
Desc: image001.jpg
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170327/e8f3d72a/attachment.jpg>


Subject: Digest Footer

openssl-users mailing list
openssl-users at openssl.org


End of openssl-users Digest, Vol 28, Issue 35

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20170328/a6d0bcc5/attachment-0001.html>

More information about the openssl-users mailing list