@danigrosu Not exactly Apache server. But from some different client it properly responded with "SERVER HELLO" . Thanks On Mon, Apr 18, 2016 at 6:22 PM, <openssl-users-request at openssl.org> wrote: > Send openssl-users mailing list submissions to > openssl-users at openssl.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mta.openssl.org/mailman/listinfo/openssl-users > 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. API question; v3_asid/v3_addr (Salz, Rich) > 2. 1.1.0-pre4: openssl speed chacha (c^) > 3. Unable to load/add a dynamic engine (danigrosu) > 4. Regarding TLS 1.3 (James) > 5. Re: Regarding TLS 1.3 (Matt Caswell) > 6. ssl connect failed (james sqawz) > 7. Re: ssl connect failed (danigrosu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Apr 2016 16:57:56 +0000 > From: "Salz, Rich" <rsalz at akamai.com> > To: "openssl-dev at openssl.org" <openssl-dev at openssl.org>, > "openssl-users at openssl.org" <openssl-users at openssl.org> > Subject: [openssl-users] API question; v3_asid/v3_addr > Message-ID: > < > f583e20aef574e55a5761812440daec9 at usma1ex-dag1mb1.msg.corp.akamai.com> > Content-Type: text/plain; charset="us-ascii" > > Do you use the v3_asid_xxx or v3_addr_xxx API's? Please let me know. > > (They are not going away, we just need to know if they're internal-only or > if people are using them.) > > -- > Senior Architect, Akamai Technologies > IM: richsalz at jabber.at Twitter: RichSalz > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mta.openssl.org/pipermail/openssl-users/attachments/20160414/052eaa82/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Fri, 15 Apr 2016 15:29:16 +0100 > From: "c^" <c at gryning.com> > To: openssl-users at openssl.org > Subject: [openssl-users] 1.1.0-pre4: openssl speed chacha > Message-ID: > <CAK-1ke=KRi2DCji7TwQeJVf6mrkrheu6FQerLpwWW-T3m= > 6a+A at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi there, > > I don't seem to be able to benchmark chacha, nor does it appear in the list > when I test all. > Is this expected? > > I can see it in 'openssl ciphers -V "ALL"' and also negotiate from a > client. > > Thanks > CraigT > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mta.openssl.org/pipermail/openssl-users/attachments/20160415/70647e35/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Sun, 17 Apr 2016 01:26:29 -0700 (MST) > From: danigrosu <dni.grosu at gmail.com> > To: openssl-users at openssl.org > Subject: [openssl-users] Unable to load/add a dynamic engine > Message-ID: <1460881589415-65563.post at n7.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi. I am using the OpenSSL 1.0.1f and I built a RSA engine using CUDA code. > I want to load this engine dynamically, i.e. when I type /# openssl > engine/, > I want > to see my engine id on the list, but all I see is this: > /(rsax) RSAX engine support > (dynamic) Dynamic engine loading support/ where the rsax is builtin > > I have modified the openssl.cnf file by adding the following lines: > /openssl_conf = openssl_def > [openssl_def] > engines = engine_section > > [engine_section] > foo = gpu_section > > [gpu_section] > dynamic_path = > /usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/librsax_gpu.so > engine_id = rsax_gpu > default_algorithms = RSA > init = 1 / > > I tried this: /# openssl speed rsa512 -engine rsax_gpu/ and everything went > well. > > Please tell me why I can't load dynamically the engine? > > > > -- > View this message in context: > http://openssl.6102.n7.nabble.com/Unable-to-load-add-a-dynamic-engine-tp65563.html > Sent from the OpenSSL - User mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 4 > Date: Mon, 18 Apr 2016 11:02:40 +0530 > From: James <james.arivazhagan at gmail.com> > To: openssl-users at openssl.org > Subject: [openssl-users] Regarding TLS 1.3 > Message-ID: > < > CAJLNLpfAhWa7QuxwUBug4WTnw0U1izuCODyXHZ36gB22_M+c7Q at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi there, > In the below link I could see TLS 1.3 support will be added in future > releases > https://www.openssl.org/policies/roadmap.html > > I think the support is not yet added. From when it will be added > > regards, > James Arivazhagan Ponnusamy > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mta.openssl.org/pipermail/openssl-users/attachments/20160418/4278b096/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Mon, 18 Apr 2016 08:56:13 +0100 > From: Matt Caswell <matt at openssl.org> > To: openssl-users at openssl.org > Subject: Re: [openssl-users] Regarding TLS 1.3 > Message-ID: <5714931D.6080302 at openssl.org> > Content-Type: text/plain; charset=windows-1252 > > > > On 18/04/16 06:32, James wrote: > > Hi there, > > In the below link I could see TLS 1.3 support will be added in future > > releases > > https://www.openssl.org/policies/roadmap.html > > > > I think the support is not yet added. From when it will be added > > TLS1.3 will not be in the next release which is currently in beta (i.e. > 1.1.0). I hope that it will be in the release after that but we have not > yet got a timescale for that. > > Matt > > > > ------------------------------ > > Message: 6 > Date: Mon, 18 Apr 2016 18:16:50 +0530 > From: james sqawz <james.sqawz at gmail.com> > To: openssl-users at openssl.org > Subject: [openssl-users] ssl connect failed > Message-ID: > <CANz_a= > rU5rhnEQGm0uG4g1GJNn7-XnZiUWSG7xDk6WdCBowtzA at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > Thanks for the providing the forum for discussion on TLS/OPENSSL related > issue. > > I am very new to openssl. > > Currently I am trying to implement HTTP over TLS.(TLS Version 1.2) > For that purpose I send connect request to the server,but connection is > getting failed. > > Following fields are abscent in my ssl packet. > > Extension: server name present > Extension:application layer protocol negotiation > > Apart from that I did not set path of Server Certificate. > > Shall these impact my connect request. > Can somebody help. > > Thanks > James > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mta.openssl.org/pipermail/openssl-users/attachments/20160418/b8bef704/attachment-0001.html > > > > ------------------------------ > > Message: 7 > Date: Mon, 18 Apr 2016 04:50:49 -0700 (MST) > From: danigrosu <dni.grosu at gmail.com> > To: openssl-users at openssl.org > Subject: Re: [openssl-users] ssl connect failed > Message-ID: > <CAGYz= > CygqnxFgQ9t+7BSJff038VTCphDpJRYzqn-0gcz9QGSkw at mail.gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi. > > Are you using the Apache server? > > On 18 April 2016 at 14:46, james sqawz [via OpenSSL] < > ml-node+s6102n65566h85 at n7.nabble.com> wrote: > > > Hi all, > > > > Thanks for the providing the forum for discussion on TLS/OPENSSL related > > issue. > > > > I am very new to openssl. > > > > Currently I am trying to implement HTTP over TLS.(TLS Version 1.2) > > For that purpose I send connect request to the server,but connection is > > getting failed. > > > > Following fields are abscent in my ssl packet. > > > > Extension: server name present > > Extension:application layer protocol negotiation > > > > Apart from that I did not set path of Server Certificate. > > > > Shall these impact my connect request. > > Can somebody help. > > > > Thanks > > James > > > > -- > > openssl-users mailing list > > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > > > > > > ------------------------------ > > If you reply to this email, your message will be added to the discussion > > below: > > http://openssl.6102.n7.nabble.com/ssl-connect-failed-tp65566.html > > To unsubscribe from OpenSSL - User, click here > > < > http://openssl.6102.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3&code=ZG5pLmdyb3N1QGdtYWlsLmNvbXwzfC0xOTcxNTAwNzE2 > > > > . > > NAML > > < > http://openssl.6102.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > > -- > View this message in context: > http://openssl.6102.n7.nabble.com/ssl-connect-failed-tp65566p65567.html > Sent from the OpenSSL - User mailing list archive at Nabble.com. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://mta.openssl.org/pipermail/openssl-users/attachments/20160418/ffeb33cb/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > openssl-users mailing list > openssl-users at openssl.org > https://mta.openssl.org/mailman/listinfo/openssl-users > > > ------------------------------ > > End of openssl-users Digest, Vol 17, Issue 24 > ********************************************* > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160418/a6ace247/attachment.html>
