async stuff is in master. please open new issue if there are problems with the
implementation.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3528
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
On 06/02/16 04:24, Fedor Indutny via RT wrote:
> On Fri, Feb 5, 2016 at 7:14 PM, Matt Caswell wrote:
>
>>
>>
>> On 05/02/16 22:42, Fedor Indutny wrote:
>>> Matt,
>>>
>>> I have looked through the APIs. Will have to experiment with them
>>> somewhen later to see how well they
On 06/02/16 04:24, Fedor Indutny via RT wrote:
> On Fri, Feb 5, 2016 at 7:14 PM, Matt Caswell wrote:
>
>>
>>
>> On 05/02/16 22:42, Fedor Indutny wrote:
>>> Matt,
>>>
>>> I have looked through the APIs. Will have to experiment with them
>>> somewhen later to see how well they
Matt,
I have looked through the APIs. Will have to experiment with them somewhen
later to see how well they will perform, but from theoretical point of view
I am a bit scared of having 2 fds (and one ucontext) for every job in a
pool. It seems like this could be a bit of burden in event-loop
Matt,
I have looked through the APIs. Will have to experiment with them somewhen
later to see how well they will perform, but from theoretical point of view
I am a bit scared of having 2 fds (and one ucontext) for every job in a
pool. It seems like this could be a bit of burden in event-loop
On 05/02/16 22:42, Fedor Indutny wrote:
> Matt,
>
> I have looked through the APIs. Will have to experiment with them
> somewhen later to see how well they will perform, but from theoretical
> point of view I am a bit scared of having 2 fds (and one ucontext) for
> every job in a pool. It seems
On 05/02/16 22:42, Fedor Indutny wrote:
> Matt,
>
> I have looked through the APIs. Will have to experiment with them
> somewhen later to see how well they will perform, but from theoretical
> point of view I am a bit scared of having 2 fds (and one ucontext) for
> every job in a pool. It seems
On Fri, Feb 5, 2016 at 7:14 PM, Matt Caswell wrote:
>
>
> On 05/02/16 22:42, Fedor Indutny wrote:
> > Matt,
> >
> > I have looked through the APIs. Will have to experiment with them
> > somewhen later to see how well they will perform, but from theoretical
> > point of view I
On Fri, Feb 5, 2016 at 7:14 PM, Matt Caswell wrote:
>
>
> On 05/02/16 22:42, Fedor Indutny wrote:
> > Matt,
> >
> > I have looked through the APIs. Will have to experiment with them
> > somewhen later to see how well they will perform, but from theoretical
> > point of view I
Thank you very much, Matt, Rich.
I will read through these docs tomorrow.
On Thu, Feb 4, 2016 at 4:29 AM, Matt Caswell via RT wrote:
>
>
> On 04/02/16 06:34, Salz, Rich via RT wrote:
> > It’s late and my response was incomplete.
> > The other part has already landed in
Thank you very much, Matt, Rich.
I will read through these docs tomorrow.
On Thu, Feb 4, 2016 at 4:29 AM, Matt Caswell via RT wrote:
>
>
> On 04/02/16 06:34, Salz, Rich via RT wrote:
> > It’s late and my response was incomplete.
> > The other part has already landed in
On 04/02/16 06:34, Salz, Rich via RT wrote:
> It’s late and my response was incomplete.
> The other part has already landed in master, and that's the "async engine"
> support.
See:
https://www.openssl.org/docs/manmaster/crypto/ASYNC_start_job.html
On 04/02/16 06:34, Salz, Rich via RT wrote:
> It’s late and my response was incomplete.
> The other part has already landed in master, and that's the "async engine"
> support.
See:
https://www.openssl.org/docs/manmaster/crypto/ASYNC_start_job.html
our plan for async work is here: https://github.com/openssl/openssl/pull/451
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Rich,
Thank you for response.
There is quite a lengthy discussion on that github PR. Is there any TL;DR
version of it?
That PR's diff doesn't really look similar to changes proposed here, as I
was mostly curious about splitting the state maching to allow deferring
things until the required data
Rich,
Thank you for response.
There is quite a lengthy discussion on that github PR. Is there any TL;DR
version of it?
That PR's diff doesn't really look similar to changes proposed here, as I
was mostly curious about splitting the state maching to allow deferring
things until the required data
It’s late and my response was incomplete.
The other part has already landed in master, and that's the "async engine"
support.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Some fixes.
On Fri, Sep 19, 2014 at 3:27 PM, Fedor Indutny fe...@indutny.com wrote:
Sorry for a noise, here is even better version of this patch.
Without BUF_MEM_grow() calls, which were actually useless,
and with clearer state management.
On Fri, Sep 19, 2014 at 12:30 PM, Fedor Indutny
And an additional follow-up, with docs and refined code.
On Fri, Sep 19, 2014 at 2:48 AM, Fedor Indutny fe...@indutny.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is an example of how it could be used (in my TLS terminator):
Sorry for a noise, here is even better version of this patch.
Without BUF_MEM_grow() calls, which were actually useless,
and with clearer state management.
On Fri, Sep 19, 2014 at 12:30 PM, Fedor Indutny fe...@indutny.com wrote:
And an additional follow-up, with docs and refined code.
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is an example of how it could be used (in my TLS terminator):
https://github.com/indutny/bud/compare/master...feature/async-key-ex
Basically, if you have ever used async SSL API, you should be
aware of things like:
SSL_ERROR_WANT_READ
Here is an additional patch, to expose the type of key that should be used
for a signature.
On Thu, Sep 11, 2014 at 10:59 AM, Fedor Indutny via RT r...@openssl.org
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello devs!
Here is a patch that implements asynchronous RSA key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello devs!
Here is a patch that implements asynchronous RSA key operation
mode for a TLS/SSL implementation in OpenSSL.
Here is some technical info about it:
Support async RSA exchange by providing new SSL_want_rsa_sign(),
SSL_want_rsa_decrypt()
23 matches
Mail list logo