This actually sounds like a lovely idea.
See: https://github.com/openssl/openssl/pull/603
Thank you!
On Sat, Jan 30, 2016 at 8:16 PM, Salz, Rich via RT wrote:
> I closed the first ticket, so everything is okay.
> If you want to do GitHub pull requests and just open an RT to refer to
> that, th
This actually sounds like a lovely idea.
See: https://github.com/openssl/openssl/pull/603
Thank you!
On Sat, Jan 30, 2016 at 8:16 PM, Salz, Rich via RT wrote:
> I closed the first ticket, so everything is okay.
> If you want to do GitHub pull requests and just open an RT to refer to
> that, th
I closed the first ticket, so everything is okay.
If you want to do GitHub pull requests and just open an RT to refer to that,
that is also okay.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hello Rich,
Do I need to submit updated patch separately, or was it ok to attach it to
the second email?
Thank you,
Fedor.
On Sat, Jan 30, 2016 at 7:14 PM, Rich Salz via RT wrote:
> cancelling as OP suggests.
> --
> Rich Salz, OpenSSL dev team; rs...@openssl.org
>
>
__
Hello Rich,
Do I need to submit updated patch separately, or was it ok to attach it to
the second email?
Thank you,
Fedor.
On Sat, Jan 30, 2016 at 7:14 PM, Rich Salz via RT wrote:
> cancelling as OP suggests.
> --
> Rich Salz, OpenSSL dev team; rs...@openssl.org
>
>
___
cancelling as OP suggests.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
When connecting to pool of diverse servers (both TLS1.0 and TLS1.2), a
following scenario may happen:
1. Connect to TLS1.2 server, receive new session
2. Store this session
3. Attempt to reuse it later when connecting to server
4. Connect to different server from the pool, which speaks onl