<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/regress/lib/libssl/shutdown, branch libressl-v3.9.2</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v3.9.2</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v3.9.2'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2024-01-30T14:46:46+00:00</updated>
<entry>
<title>Add a shutdown sequence regress test.</title>
<updated>2024-01-30T14:46:46+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2024-01-30T14:46:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=58b71efb8cd73a807ec46c267e6e92a1f728420c'/>
<id>urn:sha1:58b71efb8cd73a807ec46c267e6e92a1f728420c</id>
<content type='text'>
Some software relies on SSL_shutdown() returning 0 (indicating close-notify
sent) before returning 1 on a subsequent call (indicating close-notify sent
and received). It is worth noting that there is no guarantee that this will
occur in normal operation, as the peer could send a close-notify prior to
SSL_shutdown() being called.

This is currently failing for TLSv1.3.
</content>
</entry>
<entry>
<title>Enable for TLSv1.3 now that shutdown behaviour matches the legacy stack.</title>
<updated>2024-01-27T14:35:13+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2024-01-27T14:35:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c8d20b6287dfe3ed671896311b9b2372794b52d3'/>
<id>urn:sha1:c8d20b6287dfe3ed671896311b9b2372794b52d3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add regress test coverage for SSL_shutdown().</title>
<updated>2024-01-19T08:29:08+00:00</updated>
<author>
<name>jsing</name>
<email></email>
</author>
<published>2024-01-19T08:29:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=3d9800133cfe170c9c442d27469ee41fbc756d0f'/>
<id>urn:sha1:3d9800133cfe170c9c442d27469ee41fbc756d0f</id>
<content type='text'>
This tests and codifies the behaviour of SSL_shutdown() with respect to
SSL_quiet_shutdown() and SSL_set_shutdown(). For now, only the legacy stack
(TLSv1.2) is tested, as there are currently some subtle differences with
the TLSv1.3 stack.
</content>
</entry>
</feed>
