Tls handshake schnell sicher - Revision history

Slommage: /* Ciphers */

2024-11-27T18:22:08Z

Ciphers

← Older revision		Revision as of 18:22, 27 November 2024
Line 219:		Line 219:
	Nowadays only TLSv1.2 and newer should be used. If backwards compatibility is not necessary, it is even better to offer only TLSv1.3.		Nowadays only TLSv1.2 and newer should be used. If backwards compatibility is not necessary, it is even better to offer only TLSv1.3.
	It is recommended to only use the recommended ciphers from the BSI [https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102.html][https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102-2.html].		It is recommended to only use the recommended ciphers from the BSI [https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102.html][https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102-2.html].
	Additionally we would recommend only ChaCha20 with an adequate key length due to the performance increase ~~on devices without hardware acceleration for AES~~.		Additionally on devices without hardware acceleration for AES we would recommend only ChaCha20 with an adequate key length due to the performance increase.
	In general, it is also preferable to switch to elliptic curves, e.g. using NIST-p256 curve, for keys because this also leads to a measurable impact [[Tls_handshake_schnell_sicher#Performance_considerations \| measurable impact]].		In general, it is also preferable to switch to elliptic curves, e.g. using NIST-p256 curve, for keys because this also leads to a measurable impact [[Tls_handshake_schnell_sicher#Performance_considerations \| measurable impact]].

Slommage: /* Connection Handshake */

2024-10-28T18:24:48Z

Connection Handshake

← Older revision		Revision as of 18:24, 28 October 2024
Line 15:		Line 15:
	# Client-Certificate-Exchange: Client acknowledges validity of certificate		# Client-Certificate-Exchange: Client acknowledges validity of certificate
	# Session-Ticket: Client generates session ticket using one of the following methods:		# Session-Ticket: Client generates session ticket using one of the following methods:
	#:- random data ~~created~~ with public key of the ~~server~~		#:- random data from Client encrypted with public key of the Server, sent to Server, both parties build Session Ticket with random data from both Hello
	#:- random key via Diffie-Hellmann-Key-Exchange		#:- random key via Diffie-Hellmann-Key-Exchange
	In v1.3 this was revised to speed up the handshake, it now is as follows:		In v1.3 this was revised to speed up the handshake, it now is as follows:

Slommage: /* Performance considerations */

2024-10-28T18:14:45Z

Performance considerations

← Older revision		Revision as of 18:14, 28 October 2024
Line 51:		Line 51:
	\|}		\|}

	Other factors that may lead to a performance gain in Unixoid operating systems is kernel TLS (kTLS)[https://docs.kernel.org/networking/tls.html#kernel-tls][https://docs.kernel.org/networking/tls-offload.html] wherein the TLS-workflow is completely offloaded from the userspace program to kernelspace functions. The kernel used has to support this, it is typically available since Linux kernel version 5.1 (AES-256-GCM) or 5.11 (CHACHA20-POLY1305) since FreeBSD 13.0[https://delthas.fr/blog/2023/kernel-tls/] and can be queried via the following command		Other factors that may lead to a performance gain in Unixoid operating systems is kernel TLS (kTLS)[https://docs.kernel.org/networking/tls.html#kernel-tls][https://docs.kernel.org/networking/tls-offload.html] wherein the TLS-workflow is completely offloaded from the userspace program to kernelspace functions. The kernel used has to support this, it is typically available since Linux kernel version 5.1 (AES-256-GCM) or 5.11 (CHACHA20-POLY1305), or since FreeBSD 13.0[https://delthas.fr/blog/2023/kernel-tls/] and can be queried via the following command
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	$ lsmod\|grep tls		$ lsmod\|grep tls

Slommage: /* Enable kTLS */

2024-10-28T18:13:28Z

Enable kTLS

← Older revision		Revision as of 18:13, 28 October 2024
Line 327:		Line 327:

	using <code>apache2</code>:		using <code>apache2</code>:
	: Apache has no kTLS implementation, possibly due to the low impact.		: Apache has no kTLS implementation, possibly due to the low impact. Therefore we just can activate the <code>sendfile()</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])
	Therefore we just can activate the <code>sendfile()</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])

Slommage: /* Enable kTLS */

2024-10-28T18:13:06Z

Enable kTLS

← Older revision		Revision as of 18:13, 28 October 2024
Line 327:		Line 327:

	using <code>apache2</code>:		using <code>apache2</code>:
	Apache has no kTLS implementation, possibly due to the low impact.		: Apache has no kTLS implementation, possibly due to the low impact.
	Therefore we just can activate the <code>sendfile()</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])		Therefore we just can activate the <code>sendfile()</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])


	using <code>lighttpd</code>:		using <code>lighttpd</code>:
	:Add <syntaxhighlight lang="ini" inline>ssl.openssl.ssl-conf-cmd += ("Options" => "-KTLS")</syntaxhighlight>[https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_SSL#kTLS] to the configuration.		: Add <syntaxhighlight lang="ini" inline>ssl.openssl.ssl-conf-cmd += ("Options" => "-KTLS")</syntaxhighlight>[https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_SSL#kTLS] to the configuration.

	In general, you should be able to verify the changes using a benchmarking tool like [https://httpd.apache.org/docs/2.4/programs/ab.html <code>ab</code>] or [https://github.com/httperf/httperf <code>httperf</code>] or by taking a look into <code>/proc/net/tls_stat</code>.		In general, you should be able to verify the changes using a benchmarking tool like [https://httpd.apache.org/docs/2.4/programs/ab.html <code>ab</code>] or [https://github.com/httperf/httperf <code>httperf</code>] or by taking a look into <code>/proc/net/tls_stat</code>.

Slommage: /* useful links */

2024-10-28T18:12:37Z

useful links

← Older revision		Revision as of 18:12, 28 October 2024
Line 328:		Line 328:
	using <code>apache2</code>:		using <code>apache2</code>:
	Apache has no kTLS implementation, possibly due to the low impact.		Apache has no kTLS implementation, possibly due to the low impact.
	Therefore we just can activate the <code>sendfile()~~</code> mechanism by adding <code>EnableSendfile On~~</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])		Therefore we just can activate the <code>sendfile()</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])

Slommage: /* Enable kTLS */

2024-10-28T18:12:12Z

Enable kTLS

← Older revision		Revision as of 18:12, 28 October 2024
Line 328:		Line 328:
	using <code>apache2</code>:		using <code>apache2</code>:
	Apache has no kTLS implementation, possibly due to the low impact.		Apache has no kTLS implementation, possibly due to the low impact.
	Therefore we just can activate the <code>sendfile()</code> mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])		Therefore we just can activate the <code>sendfile()</code> mechanism by adding <code>EnableSendfile On</code>[https://man7.org/linux/man-pages/man2/sendfile.2.html] to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])

Slommage: /* for those, who are interested */

2024-10-28T18:11:30Z

for those, who are interested

← Older revision		Revision as of 18:11, 28 October 2024
Line 328:		Line 328:
	using <code>apache2</code>:		using <code>apache2</code>:
	Apache has no kTLS implementation, possibly due to the low impact.		Apache has no kTLS implementation, possibly due to the low impact.
	Therefore we just can activate the `sendfile()` mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])		Therefore we just can activate the <code>sendfile()</code> mechanism by adding <code>EnableSendfile On</code> to your config. (see the [https://httpd.apache.org/docs/current/en/mod/core.html#enablesendfile doc])

Slommage: /* Connection Handshake */

2024-10-28T13:29:08Z

Connection Handshake

← Older revision		Revision as of 13:29, 28 October 2024
Line 14:		Line 14:
	# Server-Certificate-Exchange: Server sends its certificate along with certificate chain (also sends valid OCSP-response if OCSP-stapling is configured)		# Server-Certificate-Exchange: Server sends its certificate along with certificate chain (also sends valid OCSP-response if OCSP-stapling is configured)
	# Client-Certificate-Exchange: Client acknowledges validity of certificate		# Client-Certificate-Exchange: Client acknowledges validity of certificate
	# Session-Ticket: Client generates session ticket using on of the following methods:		# Session-Ticket: Client generates session ticket using one of the following methods:
	#:- random data created with public key of the server		#:- random data created with public key of the server
	#:- random key via Diffie-Hellmann-Key-Exchange		#:- random key via Diffie-Hellmann-Key-Exchange

Oertzenf: /* Ciphers */

2024-10-28T13:24:05Z

Ciphers

← Older revision		Revision as of 13:24, 28 October 2024
Line 232:		Line 232:
	A option is to offload the TLS-handling to linux kernel. We do not recommend it because it did [[Tls_handshake_schnell_sicher#Performance_considerations \| not lead to speed improvements ]].		A option is to offload the TLS-handling to linux kernel. We do not recommend it because it did [[Tls_handshake_schnell_sicher#Performance_considerations \| not lead to speed improvements ]].
	In the case that a TLS-aware [https://www.nvidia.com/en-us/networking/ethernet/connectx-6-dx/ network card] is available, it seems best to offload the TLS handling to the dedicated hardware.		In the case that a TLS-aware [https://www.nvidia.com/en-us/networking/ethernet/connectx-6-dx/ network card] is available, it seems best to offload the TLS handling to the dedicated hardware.


			In general, it is preferable to provide users with the shortest, but complete key chain for your certificate to save time during verification.

	=== Exemplary configuarition ===		=== Exemplary configuarition ===