On Sep 2, 2009, at 3:02 PM, Stephen Henson via RT wrote:
> There appear to be several problems with this patch, see inline:
>
>> [seggelm...@fh-muenster.de - Mon Aug 31 17:04:19 2009]:
>>
>> This patch fixes several issues with DTLS cookies.
>>
> [snip]
>>
>
> cookie_secret is defined:
>
>> +unsi
On Sep 3, 2009, at 1:35 PM, Robin Seggelmann via RT wrote:
>
> On Sep 3, 2009, at 10:50 AM, Robin Seggelmann via RT wrote:
>
>>
>> On Sep 2, 2009, at 3:02 PM, Stephen Henson via RT wrote:
>>
>>> There appear to be several problems with this patch, see inline:
>>>
[seggelm...@fh-muenster.de -
On Sep 3, 2009, at 10:50 AM, Robin Seggelmann via RT wrote:
>
> On Sep 2, 2009, at 3:02 PM, Stephen Henson via RT wrote:
>
>> There appear to be several problems with this patch, see inline:
>>
>>> [seggelm...@fh-muenster.de - Mon Aug 31 17:04:19 2009]:
>>>
>>> This patch fixes several issues wit
I've noticed that sending CA chains (of potentially untrusted
certificates), with a client certificate on a per-connection basis is
currently impossible, as per the BUGS section of the
SSL_CTX_set_client_cert_cb(3) page and bug #270 in the request tracker.
This doesn't seem to be a difficult chang
This patch adds the function dtls1_listen(SSL *s, struct sockaddr
*client), as well as the user accessible macro DTLSv1_listen(). It is
intended to be called with an SSL object with a listening socket.
Every ClientHello arriving will be answered with a HelloVerifyRequest
without allocating
When can we expect OpenSSL 1.0.0 to come out of beta? I just need an
approximate period of time - 3 months, 6 months etc.
This information will be quite helpful for me so any input will be greatly
appreciated.
Thanks,
-Dharmendra
