<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libtls/tls_server.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>2019-05-13T22:36:01+00:00</updated>
<entry>
<title>Acquire mutex before incrementing the refcount. Fixes COV-186144</title>
<updated>2019-05-13T22:36:01+00:00</updated>
<author>
<name>bcook</name>
<email></email>
</author>
<published>2019-05-13T22:36:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c9ed4a76707f17c97f0f1c670382b32d6045c638'/>
<id>urn:sha1:c9ed4a76707f17c97f0f1c670382b32d6045c638</id>
<content type='text'>
ok tb@
</content>
</entry>
<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>Split keypair handling out into its own file - it had already appeared</title>
<updated>2018-02-08T05:56:49+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2018-02-08T05:56:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=8a01a8361d1add29153f53a3721130f62d3d4389'/>
<id>urn:sha1:8a01a8361d1add29153f53a3721130f62d3d4389</id>
<content type='text'>
in multiple locations.

ok beck@
</content>
</entry>
<entry>
<title>Keep track of which keypair is in use by a TLS context.</title>
<updated>2017-09-20T17:05:17+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-09-20T17:05:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=cb877fda6d4f301551f4f41cbe708b7a31217fba'/>
<id>urn:sha1:cb877fda6d4f301551f4f41cbe708b7a31217fba</id>
<content type='text'>
This fixes a bug where by a TLS server with SNI would always only return
the OCSP staple for the default keypair, rather than returning the OCSP
staple associated with the keypair that was selected via SNI.

Issue reported by William Graeber and confirmed by Andreas Bartelt.

Fix tested by William Graeber and Andreas Bartelt - thanks!
</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>RFC 6066 states that IP literals are not permitted in "HostName" for a</title>
<updated>2017-07-05T15:38:35+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-07-05T15:38:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=23f8730872473ece83a0897191d237776311af34'/>
<id>urn:sha1:23f8730872473ece83a0897191d237776311af34</id>
<content type='text'>
TLS Server Name extension, however seemingly several clients (including
Python, Ruby and Safari) violate the RFC. Given that this is a fairly
widespread issue, if we receive a TLS Server Name extension that contains
an IP literal, pretend that we did not receive the extension rather than
causing a handshake failure.

Issue raised by jsg@

ok jsg@
</content>
</entry>
<entry>
<title>Use the tls_password_cb() callback with all PEM_read_bio_*() calls, so that</title>
<updated>2017-06-22T18:03:57+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-06-22T18:03:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c9b1852dc910671bb8042219d73820d7a47138dd'/>
<id>urn:sha1:c9b1852dc910671bb8042219d73820d7a47138dd</id>
<content type='text'>
we can prevent libcrypto from going behind our back and trying to read
passwords from standard input (which we may not be permitted to do).

Found by jsg@ with httpd and password protected keys.
</content>
</entry>
<entry>
<title>Use the standard `rv' idiom in tls_keypair_load_cert(), rather than</title>
<updated>2017-06-22T17:34:25+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-06-22T17:34:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=258d6d4823852894a9046304508dc4d9f5c44d38'/>
<id>urn:sha1:258d6d4823852894a9046304508dc4d9f5c44d38</id>
<content type='text'>
duplicating clean up code.
</content>
</entry>
<entry>
<title>Perform reference counting for tls_config. This allows tls_config_free() to</title>
<updated>2017-05-06T20:59:28+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2017-05-06T20:59:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7fed4741c75d7419f23867acd8c3a1bdc866b716'/>
<id>urn:sha1:7fed4741c75d7419f23867acd8c3a1bdc866b716</id>
<content type='text'>
be called as soon as it has been passed to the final tls_configure() call,
simplifying lifetime tracking for the application.

Requested some time ago by tedu@.

ok beck@
</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>
</feed>
