From: tb Date: Fri, 4 Feb 2022 07:59:54 +0000 (+0000) Subject: Fix another instance of incorrect capitalization of ChaCha20. X-Git-Url: http://artulab.com/gitweb/?a=commitdiff_plain;h=2c96ffb07232d88bbb63ea8371c25c6b30646dd7;p=openbsd Fix another instance of incorrect capitalization of ChaCha20. pointed out by jmc --- diff --git a/sbin/ipsecctl/ipsec.conf.5 b/sbin/ipsecctl/ipsec.conf.5 index 0162ea63fe7..925f8cbaaa7 100644 --- a/sbin/ipsecctl/ipsec.conf.5 +++ b/sbin/ipsecctl/ipsec.conf.5 @@ -1,4 +1,4 @@ -.\" $OpenBSD: ipsec.conf.5,v 1.162 2021/11/04 04:20:14 yasuoka Exp $ +.\" $OpenBSD: ipsec.conf.5,v 1.163 2022/02/04 07:59:54 tb Exp $ .\" .\" Copyright (c) 2004 Mathieu Sauve-Frankel All rights reserved. .\" @@ -22,7 +22,7 @@ .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\" -.Dd $Mdocdate: November 4 2021 $ +.Dd $Mdocdate: February 4 2022 $ .Dt IPSEC.CONF 5 .Os .Sh NAME @@ -680,7 +680,7 @@ This is because the most significant bit of each byte is used for parity. The keysize of AES-CTR can be 128, 192, or 256 bits. However as well as the key, a 32-bit nonce has to be supplied. Thus 160, 224, or 288 bits of key material, respectively, have to be supplied. -The same applies to AES-GCM, AES-GMAC and Chacha20-Poly1305, +The same applies to AES-GCM, AES-GMAC and ChaCha20-Poly1305, however in the latter case the keysize is 256 bits. .Pp Using AES-GMAC or NULL with ESP will only provide authentication.