<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/tls.h, branch OPENBSD_6_8_BASE</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_6_8_BASE'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2020-01-22T06:44:02+00:00</updated>
<entry>
<title>Enable TLS version 1.3 in the default protocols for libtls.</title>
<updated>2020-01-22T06:44:02+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2020-01-22T06:44:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=056ac654c75227a2b7912019eacc8397cc7c0825'/>
<id>urn:sha1:056ac654c75227a2b7912019eacc8397cc7c0825</id>
<content type='text'>
This will as yet not do anything, until we turn it on in the
lower level libraries.

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>Provide tls_conn_cipher_strength().</title>
<updated>2019-11-02T13:37:59+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2019-11-02T13:37:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=914deddb0bc7631f9603d3f22c07d8b3b6031d80'/>
<id>urn:sha1:914deddb0bc7631f9603d3f22c07d8b3b6031d80</id>
<content type='text'>
This returns the strength in bits of the symmetric cipher used for the
connection.

Diff from gilles@

ok tb@
</content>
</entry>
<entry>
<title>expose the default cert file as a function, not a define. it's really</title>
<updated>2018-11-29T14:24:23+00:00</updated>
<author>
<name>tedu</name>
<email></email>
</author>
<published>2018-11-29T14:24:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=6dee83d0efd9b6a0e45f73737efb9078aafbdd15'/>
<id>urn:sha1:6dee83d0efd9b6a0e45f73737efb9078aafbdd15</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>Define TLS_CA_CERT_FILE rather than having every application create their</title>
<updated>2018-11-06T20:34:54+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2018-11-06T20:34:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c572182382f504af52f71f2197c113d5be045376'/>
<id>urn:sha1:c572182382f504af52f71f2197c113d5be045376</id>
<content type='text'>
own define for /etc/ssl/cert.pem.

ok beck@ bluhm@ tb@
</content>
</entry>
<entry>
<title>Bump TLS API version since we've added more functionality.</title>
<updated>2018-02-10T04:58:08+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2018-02-10T04:58:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=e8bcd4e800bae1146a3b5da278f24f6480ffa87b'/>
<id>urn:sha1:e8bcd4e800bae1146a3b5da278f24f6480ffa87b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add support to libtls for client-side TLS session resumption.</title>
<updated>2018-02-10T04:41:24+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2018-02-10T04:41:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7f2c0ca878baa76136bb91e6e42ba28feb243a6b'/>
<id>urn:sha1:7f2c0ca878baa76136bb91e6e42ba28feb243a6b</id>
<content type='text'>
A libtls client can specify a session file descriptor (a regular file
with appropriate ownership and permissions) and libtls will manage reading
and writing of session data across TLS handshakes.

Discussed at length with deraadt@ and tedu@.

Rides previous minor bump.

ok beck@
</content>
</entry>
<entry>
<title>Add a tls_config_set_ecdhecurves() function to libtls, which allows the</title>
<updated>2017-08-10T18:18:30+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-08-10T18:18:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=52c5bafe628bfaf1072a7e4cd721523f818d1bcf'/>
<id>urn:sha1:52c5bafe628bfaf1072a7e4cd721523f818d1bcf</id>
<content type='text'>
names of the elliptic curves that may be used during client and server
key exchange to be specified.

This deprecates tls_config_set_ecdhecurve(), which could only be used to
specify a single supported curve.

ok beck@
</content>
</entry>
<entry>
<title>Add support for providing CRLs to libtls - once a CRL is provided we</title>
<updated>2017-07-06T17:12:22+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-07-06T17:12:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=98d8f250ae4bc4d9b4a4f49d8df340640852319b'/>
<id>urn:sha1:98d8f250ae4bc4d9b4a4f49d8df340640852319b</id>
<content type='text'>
enable CRL checking for the full certificate chain.

Based on a diff from Jack Burton &lt;jack at saosce dot com dot au&gt;, thanks!

Discussed with beck@
</content>
</entry>
<entry>
<title>Provide a tls_unload_file() function, that frees the memory returned from</title>
<updated>2017-05-06T20:57:45+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-05-06T20:57:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7046952f9f5fae47726c165667e46169d74cdfae'/>
<id>urn:sha1:7046952f9f5fae47726c165667e46169d74cdfae</id>
<content type='text'>
a tls_load_file() call, ensuring that it the contents become inaccessible.
This is specifically needed on platforms where the library allocators may
be different from the application allocator.

ok beck@
</content>
</entry>
</feed>
