<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/man, branch master</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=master</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2025-07-07T10:54:00+00:00</updated>
<entry>
<title>.Lb libtls libssl libcrypto</title>
<updated>2025-07-07T10:54:00+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2025-07-07T10:54:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=800b400429130c255973b130ac2376970630d5e9'/>
<id>urn:sha1:800b400429130c255973b130ac2376970630d5e9</id>
<content type='text'>
OK tb@ and no objection from tedu@
</content>
</entry>
<entry>
<title>Document tls_peer_cert_common_name()</title>
<updated>2024-12-10T08:42:12+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-12-10T08:42:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c94b3b4a953c20b000c195ce5e2ef6683eed6964'/>
<id>urn:sha1:c94b3b4a953c20b000c195ce5e2ef6683eed6964</id>
<content type='text'>
ok beck
</content>
</entry>
<entry>
<title>remove tls_reset(3) from the NAME, SYNOPSIS, and HISTORY sections</title>
<updated>2023-09-18T17:25:15+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2023-09-18T17:25:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b92995f2a1d2dda8c6289e3afb31574b7feec963'/>
<id>urn:sha1:b92995f2a1d2dda8c6289e3afb31574b7feec963</id>
<content type='text'>
because it is documented in the separate tls_client(3) manual page
</content>
</entry>
<entry>
<title>Remove the ability to do tls 1.0 and 1.1 from libtls.</title>
<updated>2023-07-02T06:37:27+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2023-07-02T06:37:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=908a2337ae4c28163a92b9fda969dbdd36bc634b'/>
<id>urn:sha1:908a2337ae4c28163a92b9fda969dbdd36bc634b</id>
<content type='text'>
With this change any requests from configurations to request
versions of tls before tls 1.2 will use tls 1.2. This prepares
us to deprecate tls 1.0 and tls 1.1 support from libssl.

ok tb@
</content>
</entry>
<entry>
<title>contibutions -&gt; contributions</title>
<updated>2022-01-01T02:18:28+00:00</updated>
<author>
<name>jsg</name>
<email></email>
</author>
<published>2022-01-01T02:18:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e0b952fc7cccf4861f154522a0359428d82729e8'/>
<id>urn:sha1:e0b952fc7cccf4861f154522a0359428d82729e8</id>
<content type='text'>
</content>
</entry>
<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>
</feed>
