Sure, Sorry for the noise.
and Thanks Steve.
is the API introduced recently openssl 1.0.1f does not seem to have it?
if so, any plan to backport it?
On Fri, Sep 25, 2015 at 7:39 PM, Matt Caswell via RT wrote:
> Closing this ticket. Please use the API suggested by Steve.
>
In a bid to use openssl's non blocking mode with bio pair, we are calling
SSL_do_handshake to perform handshake and we would like to do callback
based on role of SSL.
and Seems that OpenSSL does not expose any APi for doing the same.
The attached patch adds a new API, which returns the
Thanks Rich
On Fri, Aug 28, 2015 at 12:03 AM, Rich Salz via RT r...@openssl.org wrote:
According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.
--
Warm Regards
--Dev
OpenPegasus Developer
I'm one of those
Is anybody interested to have a look at 3678. It has a patch attached also.
--
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi all
Please check if the man page correction for BIO_new_bio_pair.
The earlier one was hard to understand and had to scratch hair for a long
time
Also it corrects syntax error in BIO_new_bio_pair.
--
Warm Regards
--Dev
OpenPegasus Developer
I'm one of those people that think Thomas Edison
Thanks foe the info,
It was trivial issue and good to know if it has been resolved.
Have no more concern
On Tue, Jul 1, 2014 at 10:31 PM, Rich Salz via RT r...@openssl.org wrote:
According to our records, your request has been resolved. If you have any
further questions or concerns, please
While going through man SSL_CTX_set_options, came across following thing.
NOTES
The behaviour of the SSL library can be changed by setting several
options. The options are coded as bitmasks and can be combined by
alogical or operation(|).
whereas the symbol shown is that of bitwise OR.
Oops misses the patch to attach.
Attaching the change as patch
On Sat, Jan 25, 2014 at 3:45 PM, The default queue via RT
r...@openssl.orgwrote:
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
[PATCH] Correct a