One last thing. tls_read and tls_write respectively return
TLS_READ_AGAIN and TLS_WRITE_AGAIN as well as the documented 0 and -1.
You might consider returning a value that represents EOF rather then
just putting the string into an error message and returning -1 from
tls_read. It would help in eff
On Fri, 2015-02-20 at 15:05 -0500, Ted Unangst wrote:
> Greg Martin wrote:
> >
> > I'd have to say no. There are structures used but not documented and the
> > one line description of some of the functions could be open to
> > interpretation. Sample usage is never amiss in my estimation.
>
> I'd
On Fri, 2015-02-20 at 15:05 -0500, Ted Unangst wrote:
> Greg Martin wrote:
> >
> > I'd have to say no. There are structures used but not documented and the
> > one line description of some of the functions could be open to
> > interpretation. Sample usage is never amiss in my estimation.
>
> I'd
Greg Martin wrote:
> On Fri, 2015-02-20 at 15:05 -0500, Ted Unangst wrote:
> > Greg Martin wrote:
> > >
> > > I'd have to say no. There are structures used but not documented and the
> > > one line description of some of the functions could be open to
> > > interpretation. Sample usage is never am
On Fri, 2015-02-20 at 15:05 -0500, Ted Unangst wrote:
> Greg Martin wrote:
> >
> > I'd have to say no. There are structures used but not documented and the
> > one line description of some of the functions could be open to
> > interpretation. Sample usage is never amiss in my estimation.
>
> I'd
> I'd have to say no. There are structures used but not documented and the
> one line description of some of the functions could be open to
> interpretation. Sample usage is never amiss in my estimation.
If we are thinking of the same structures they are not supposed to be
documented. Notice even
Greg Martin wrote:
>
> I'd have to say no. There are structures used but not documented and the
> one line description of some of the functions could be open to
> interpretation. Sample usage is never amiss in my estimation.
I'd appreciate knowing what you found missing. I know it's pretty barren
On Fri, 2015-02-20 at 12:25 -0600, Constantine A. Murenin wrote:
> On 20 February 2015 at 10:36, Greg Martin wrote:
> > Hi,
> > I just build libressl on Linux 3.13.0-44-generic. I haven't installed it
> > yet but it was a clean build.
> >
> > I'm interested in trying libssl but the only documentat
> On Feb 20, 2015, at 10:36 AM, Greg Martin wrote:
>
> Hi,
> I just build libressl on Linux 3.13.0-44-generic. I haven't installed it
> yet but it was a clean build.
>
> I'm interested in trying libssl but the only documentation I've found is
> a single manpage (tls_int). Are there some example
libtls? What are you trying to do with it? There are several
examples in the OpenBSD source code (relayd, ftp), but if you are
compiling for linux, maybe you aren't an obsd user with the code
handy.
I incorporated it into links+ (links2):
https://github.com/trondd555/links-plus/blob/master/conne
On 20 February 2015 at 10:36, Greg Martin wrote:
> Hi,
> I just build libressl on Linux 3.13.0-44-generic. I haven't installed it
> yet but it was a clean build.
>
> I'm interested in trying libssl but the only documentation I've found is
> a single manpage (tls_int). Are there some example progra
Hi,
I just build libressl on Linux 3.13.0-44-generic. I haven't installed it
yet but it was a clean build.
I'm interested in trying libssl but the only documentation I've found is
a single manpage (tls_int). Are there some example programs somewhere or
more comprehensive documentation?
Thanks,
Gr
12 matches
Mail list logo
