<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/man, branch libressl-v3.4.1</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v3.4.1</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v3.4.1'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2021-06-22T20:01:19+00:00</updated>
<entry>
<title>zap wonky commas;</title>
<updated>2021-06-22T20:01:19+00:00</updated>
<author>
<name>jmc</name>
<email></email>
</author>
<published>2021-06-22T20:01:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=3650508f3facd1163d6549d6fab59a6f81db17d2'/>
<id>urn:sha1:3650508f3facd1163d6549d6fab59a6f81db17d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Clarify tls_config_set_*_file() file I/O semantics</title>
<updated>2021-06-22T17:59:48+00:00</updated>
<author>
<name>kn</name>
<email></email>
</author>
<published>2021-06-22T17:59:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7464c3881edf2f952d355d3ed4e23a63ef9051fa'/>
<id>urn:sha1:7464c3881edf2f952d355d3ed4e23a63ef9051fa</id>
<content type='text'>
tls_config_set_*_file(3) do not just set the file paths like
tls_config_set_*_path(3) do, they do load the given file(s) into memory
directly using tls_config_load_file().

This distinction is important because it means a later tls_connect(3)
will not do any file I/O (at least wrt. those files), which is relevant when
for example pleding without "[rwc]path" after loading files into memory and
before doing tls_connect(3).

The manual's current wording made me use the following due to above way of
pledging a program:
	tls_load_file()
	tls_config_set_ca_mem()
	tls_unload_file()

While in fact a single tls_config_set_ca_file() call does the same.

tls_config.c r1.26 (Aug 2016) change the code but forgot to amend the manual
as noted by tb, thanks.

Feedback OK tb
</content>
</entry>
<entry>
<title>Tweak previous:</title>
<updated>2021-01-02T19:58:44+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2021-01-02T19:58:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c0a13098b65e31155a7ddfa3514859fcc685e498'/>
<id>urn:sha1:c0a13098b65e31155a7ddfa3514859fcc685e498</id>
<content type='text'>
* Do not abuse .Bl -tag for lists without bodies, use .Bl -item instead.
* In tagged lists, put bodies into bodies, not into heads.
* Add a few missing macros.
* Drop some useless quoting.
</content>
</entry>
<entry>
<title>Make list of DHE parameters more prominent</title>
<updated>2021-01-02T19:15:04+00:00</updated>
<author>
<name>kn</name>
<email></email>
</author>
<published>2021-01-02T19:15:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=1810ecb83b1849023a93ebdb181e2054f991f1b4'/>
<id>urn:sha1:1810ecb83b1849023a93ebdb181e2054f991f1b4</id>
<content type='text'>
Follow the previous commit and complete the manual page for consistency;
better readable and tags for free.

OK tb
</content>
</entry>
<entry>
<title>Make the list of supported protocols more prominent</title>
<updated>2020-12-30T13:38:13+00:00</updated>
<author>
<name>kn</name>
<email></email>
</author>
<published>2020-12-30T13:38:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e510ae695c6796e2c5638d83018f97c4f02b460f'/>
<id>urn:sha1:e510ae695c6796e2c5638d83018f97c4f02b460f</id>
<content type='text'>
Manuals like httpd.conf(5) refer to this for valid protocol strings, but
elements inlined into sentences are hard find to spot.

Use a list as already done elsewhere in this manual.

OK jmc on earlier version
Feeback OK tb
</content>
</entry>
<entry>
<title>Note in the man page that the default protocols list includes 1.3</title>
<updated>2020-01-22T06:46:34+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2020-01-22T06:46:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=70165c1ccc36585328dc1800b0b9d35a6e4ddd76'/>
<id>urn:sha1:70165c1ccc36585328dc1800b0b9d35a6e4ddd76</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:21+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2020-01-20T08:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=4964c87c6ff167d81b09c143dff53c224a573ccb'/>
<id>urn:sha1:4964c87c6ff167d81b09c143dff53c224a573ccb</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:14+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-11-02T13:43:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7b65da8eb0a399e1e221439826be2ec486036a70'/>
<id>urn:sha1:7b65da8eb0a399e1e221439826be2ec486036a70</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: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>
</feed>
