<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/tls_client.c, 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>2018-03-19T16:34:47+00:00</updated>
<entry>
<title>Automatically handle library initialisation for libtls.</title>
<updated>2018-03-19T16:34:47+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2018-03-19T16:34:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=5fd38b4657cfd0f2e0b0b92fd650c6710e8fbc8b'/>
<id>urn:sha1:5fd38b4657cfd0f2e0b0b92fd650c6710e8fbc8b</id>
<content type='text'>
Now that we have tls_init() under pthread_once(), automatically initialise
libtls from the entry point functions (tls_config(), tls_client() and
tls_server()) - this makes an explicit tls_init() call no longer a
requirement.

ok bcook@ beck@ inoguchi@
</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>Ensure that a client context has been connected before attempting to</title>
<updated>2017-05-07T03:27:06+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-05-07T03:27:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=ec4a0562b4584e6652e9b578546a2ad947ef9d47'/>
<id>urn:sha1:ec4a0562b4584e6652e9b578546a2ad947ef9d47</id>
<content type='text'>
complete a TLS handshake.
</content>
</entry>
<entry>
<title>Rework name verification code so that a match is indicated via an argument,</title>
<updated>2017-04-10T17:11:13+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-04-10T17:11:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2c72bbf2735f97ac7b152b55787c620ee18ae10f'/>
<id>urn:sha1:2c72bbf2735f97ac7b152b55787c620ee18ae10f</id>
<content type='text'>
rather than return codes. More strictly follow RFC 6125, in particular only
check the CN if there are no SAN identifiers present in the certificate
(per section 6.4.4).

Previous behaviour questioned by Daniel Stenberg &lt;daniel at haxx dot se&gt;.

ok beck@ jca@
</content>
</entry>
<entry>
<title>Use a flag to track when we need to call SSL_shutdown(). This avoids an</title>
<updated>2017-01-26T12:56:37+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-01-26T12:56:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b67df6aca845e645c0b047549941d37e2e1cdaab'/>
<id>urn:sha1:b67df6aca845e645c0b047549941d37e2e1cdaab</id>
<content type='text'>
issue where by calling tls_close() on a TLS context that has not attempted
a handshake, results in an unexpected failure.

Reported by Vinay Sajip.

ok beck@
</content>
</entry>
<entry>
<title>If tls_set_cbs() fails an error will already be specified, so do not</title>
<updated>2017-01-12T16:15:58+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-01-12T16:15:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7062a129c961dba77ca2a0afc3147300419a42eb'/>
<id>urn:sha1:7062a129c961dba77ca2a0afc3147300419a42eb</id>
<content type='text'>
replace it with a less specific one.
</content>
</entry>
<entry>
<title>Hook up a certificate verify callback so that we can set user friendly</title>
<updated>2016-12-26T16:20:58+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2016-12-26T16:20:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=101846b59a84b7fc0750f3a4ecdb5adcb903d5be'/>
<id>urn:sha1:101846b59a84b7fc0750f3a4ecdb5adcb903d5be</id>
<content type='text'>
error messages, instead of libssl error strings. This gives us messages
like:

  certificate verification failed: certificate has expired

Instead of:

  14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

This also lets us always enable peer verification since the no verification
case is now handled via the callback.

Tested by tedu@

ok beck@
</content>
</entry>
<entry>
<title>Add OCSP client side support to libtls.</title>
<updated>2016-11-02T15:18:42+00:00</updated>
<author>
<name>beck</name>
<email></email>
</author>
<published>2016-11-02T15:18:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=5418ce1f48164f4ba5618463049fa69568460f4f'/>
<id>urn:sha1:5418ce1f48164f4ba5618463049fa69568460f4f</id>
<content type='text'>
   - Provide access to certificate OCSP URL
   - Provide ability to check a raw OCSP reply against an
     established TLS ctx
   - Check and validate OCSP stapling info in the TLS handshake
     if a stapled OCSP response is provided.`

Add example code to show OCSP URL and stapled info
into netcat.

ok jsing@
</content>
</entry>
<entry>
<title>Maintain consistency with function naming.</title>
<updated>2016-09-04T13:20:56+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2016-09-04T13:20:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=013d67ebf3bda6b9fe3a7add0bd41404d3392054'/>
<id>urn:sha1:013d67ebf3bda6b9fe3a7add0bd41404d3392054</id>
<content type='text'>
</content>
</entry>
</feed>
