Hi
On 14.09.2016, at 14:21, Brent Cook wrote:
>
> On 14.09.2016, at 13:37, Brent Cook wrote:
>
> >
> > Once the expectations of the callbacks are finalized, this needs a good
> > explanation in the manual.
>
> [...]
> Generally, what are the expectations of a callback, what should it retur
Hi
On 14.09.2016, at 13:37, Brent Cook wrote:
>
> Once the expectations of the callbacks are finalized, this needs a good
> explanation in the manual.
Ok, how would I do that best?
I admit to have amended the man page by sheer
copy-and-paste-of-very-small-bits™,
so what would you suggest
Hi there
On 05.09.2016, at 15:50, bust...@gmail.com wrote:
> Hey, the typedef came in handy :) Ok bcook@
>
> On Sep 5, 2016, at 11:52 AM, Bob Beck wrote:
>
>> I am in agreement in principle, but please coordinate with bcook@ and/or
>> jsing@ who were possibly doing
>> some related adjustments
, int _fd_read, int _fd_write,
>> const char *_servername);
>> int tls_connect_servername(struct tls *_ctx, const char *_host,
>> const char *_port, const char *_servername);
>> int tls_connect_socket(struct tls *_ctx, int _s, const char *_servername);
>>
b/libtls/tls_bio_cb.c src/lib/libtls/tls_bio_cb.c
new file mode 100644
index 000..f8b24b0
--- /dev/null
+++ src/lib/libtls/tls_bio_cb.c
@@ -0,0 +1,182 @@
+/* $ID$ */
+/*
+ * Copyright (c) 2016 Tobias Pape
+ *
+ * Permission to use, copy, modify, and distribute this software for any
+ * purpose
