<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/man/tls_read.3, branch OPENBSD_6_7_BASE</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_6_7_BASE</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_6_7_BASE'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2019-07-09T17:58:33+00:00</updated>
<entry>
<title>Group tls_{handshake,read,write,close}() return values documentation.</title>
<updated>2019-07-09T17:58:33+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-07-09T17:58:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=ee433ef57027dc35958a9c56ad878f679d66886b'/>
<id>urn:sha1:ee433ef57027dc35958a9c56ad878f679d66886b</id>
<content type='text'>
Move the documentation for tls_error() down so that both the special return
values for tls_{handshake,read,write,close}() directly follow the standard
return values for the same functions.

Prompted by deraadt@.

ok deraadt@ schwarze@
</content>
</entry>
<entry>
<title>tls_read() &amp; tls_write() return 4 possible values: TLS_WANT_POLLOUT,</title>
<updated>2019-06-20T15:47:44+00:00</updated>
<author>
<name>deraadt</name>
<email></email>
</author>
<published>2019-06-20T15:47:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=9fddbc1119a5bde8e0230cd05995f60c60c3596b'/>
<id>urn:sha1:9fddbc1119a5bde8e0230cd05995f60c60c3596b</id>
<content type='text'>
TLS_WANT_POLLIN, -1, or 0.  After handling the first two, check for -1
rather than vaguely "&lt; 0".
ok jsing
</content>
</entry>
<entry>
<title>fix examples (libtls uses its own error reporting mechanism)</title>
<updated>2019-03-20T14:17:19+00:00</updated>
<author>
<name>espie</name>
<email></email>
</author>
<published>2019-03-20T14:17:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b358acd5505849bc5e54700a8268cf5bb82a96ce'/>
<id>urn:sha1:b358acd5505849bc5e54700a8268cf5bb82a96ce</id>
<content type='text'>
okay tb@
</content>
</entry>
<entry>
<title>document tls_config_error(3) RETURN VALUES, improve what is said</title>
<updated>2017-02-20T13:09:15+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2017-02-20T13:09:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=bed6069126e89ffb93d1298db322577383495227'/>
<id>urn:sha1:bed6069126e89ffb93d1298db322577383495227</id>
<content type='text'>
about tls_error(3), and warn about some traps;
OK jmc@
</content>
</entry>
<entry>
<title>add HISTORY and AUTHORS</title>
<updated>2017-01-28T00:59:36+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2017-01-28T00:59:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=850cb05a7787213159cf03cef8d67cbac122026d'/>
<id>urn:sha1:850cb05a7787213159cf03cef8d67cbac122026d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix Copyright notices; ok beck@ jsing@ tedu@</title>
<updated>2017-01-27T20:19:51+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2017-01-27T20:19:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e1e5222367e10bef8c8288e06b741d766faf6327'/>
<id>urn:sha1:e1e5222367e10bef8c8288e06b741d766faf6327</id>
<content type='text'>
</content>
</entry>
<entry>
<title>split the tls_init(3) that had grown fat to allow healthy future growth;</title>
<updated>2017-01-25T23:53:18+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2017-01-25T23:53:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=d66bfa15e92b2523fa18aec340ecb1cf3eb361ec'/>
<id>urn:sha1:d66bfa15e92b2523fa18aec340ecb1cf3eb361ec</id>
<content type='text'>
suggested by jsing@; "i would just chuck it in" jmc@
</content>
</entry>
</feed>
