<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/lib/libtls/man, branch jd/queueboosts</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/lib/libtls/man?h=jd%2Fqueueboosts</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/lib/libtls/man?h=jd%2Fqueueboosts'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-01-22T06:46:34Z</updated>
<entry>
<title>Note in the man page that the default protocols list includes 1.3</title>
<updated>2020-01-22T06:46:34Z</updated>
<author>
<name>beck</name>
<email>beck@openbsd.org</email>
</author>
<published>2020-01-22T06:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6f8363eed5c17b06e568c6b564b5de5fb5806988'/>
<id>urn:sha1:6f8363eed5c17b06e568c6b564b5de5fb5806988</id>
<content type='text'>
ok jsing@
</content>
</entry>
<entry>
<title>Add support for TLSv1.3 as a protocol to libtls.</title>
<updated>2020-01-20T08:39:21Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2020-01-20T08:39:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=4c47943547690ae663117419af1d1408754483fd'/>
<id>urn:sha1:4c47943547690ae663117419af1d1408754483fd</id>
<content type='text'>
This makes tls_config_parse_protocols() recognise and handle "tlsv1.3".
If TLSv1.3 is enabled libtls will also request libssl to enable it.

ok beck@ tb@
</content>
</entry>
<entry>
<title>Document tls_conn_cipher_strength().</title>
<updated>2019-11-02T13:43:14Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-11-02T13:43:14Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8e0c768258d4632c51876b4397034bc3152bf8db'/>
<id>urn:sha1:8e0c768258d4632c51876b4397034bc3152bf8db</id>
<content type='text'>
ok schwarze@
</content>
</entry>
<entry>
<title>Group tls_{handshake,read,write,close}() return values documentation.</title>
<updated>2019-07-09T17:58:33Z</updated>
<author>
<name>jsing</name>
<email>jsing@openbsd.org</email>
</author>
<published>2019-07-09T17:58:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5719c9cb982c64f3c0ad4d33b93e1830a06d9c68'/>
<id>urn:sha1:5719c9cb982c64f3c0ad4d33b93e1830a06d9c68</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:44Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-06-20T15:47:44Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=fe1f7dfa9438a02ac3cf846b995d81cf559db7f5'/>
<id>urn:sha1:fe1f7dfa9438a02ac3cf846b995d81cf559db7f5</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:19Z</updated>
<author>
<name>espie</name>
<email>espie@openbsd.org</email>
</author>
<published>2019-03-20T14:17:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5030b68b5dc9572c8575b9b6c2bee71b90256b70'/>
<id>urn:sha1:5030b68b5dc9572c8575b9b6c2bee71b90256b70</id>
<content type='text'>
okay tb@
</content>
</entry>
<entry>
<title>Delete a note taken during the rev. 1.1 man page splite</title>
<updated>2018-12-14T20:18:27Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2018-12-14T20:18:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=11e8be6bfe9c53b0e71ed09ca3a3e7edc6a446ec'/>
<id>urn:sha1:11e8be6bfe9c53b0e71ed09ca3a3e7edc6a446ec</id>
<content type='text'>
that should have been deleted before commit.
The cross reference is already present below SEE ALSO.
Glitch noticed by jsing@.
</content>
</entry>
<entry>
<title>expose the default cert file as a function, not a define. it's really</title>
<updated>2018-11-29T14:24:23Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2018-11-29T14:24:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f6b75673f6c960a9743bfd16c1e52dd100265c68'/>
<id>urn:sha1:f6b75673f6c960a9743bfd16c1e52dd100265c68</id>
<content type='text'>
an internal detail of the library, so the string should live inside it,
not in the application code.
ok jsing
</content>
</entry>
<entry>
<title>typo in argument type, from Mario dot Andres dot Campos at gmail dot com</title>
<updated>2018-08-21T00:35:55Z</updated>
<author>
<name>schwarze</name>
<email>schwarze@openbsd.org</email>
</author>
<published>2018-08-21T00:35:55Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5a0149f06d8092c6efcd67e1c6fcae2679080d62'/>
<id>urn:sha1:5a0149f06d8092c6efcd67e1c6fcae2679080d62</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use the same order in NAME, SYNOPSIS, DESCRIPTION, and RETURN VALUES to</title>
<updated>2018-07-24T02:01:34Z</updated>
<author>
<name>tb</name>
<email>tb@openbsd.org</email>
</author>
<published>2018-07-24T02:01:34Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c8cb7e6068f247a1ce3fb16dc32aab592208b818'/>
<id>urn:sha1:c8cb7e6068f247a1ce3fb16dc32aab592208b818</id>
<content type='text'>
improve readability and ease of maintenance.

Positive feedback jmc
Detailed suggestion &amp; ok schwarze
</content>
</entry>
</feed>
