From d0a798f774735c176ed0d3500ac986957a02660f Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Sun, 16 Mar 2025 21:00:28 +0000 Subject: cryptobyte: fix typo 'octects' into 'octets' for asn1.go This typo ends up into lots of executables that trigger 'codespell'-style linter checks. Change-Id: I2a7e3a6597272ca7c97ebddc54c5eef4cb5cab88 GitHub-Last-Rev: e42f734f00aa575030b72dd1e328d2acefb02625 GitHub-Pull-Request: golang/crypto#310 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/646375 LUCI-TryBot-Result: Go LUCI Reviewed-by: Ian Lance Taylor Reviewed-by: Roland Shoemaker --- cryptobyte/asn1.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cryptobyte/asn1.go b/cryptobyte/asn1.go index 2492f79..d25979d 100644 --- a/cryptobyte/asn1.go +++ b/cryptobyte/asn1.go @@ -234,7 +234,7 @@ func (b *Builder) AddASN1(tag asn1.Tag, f BuilderContinuation) { // Identifiers with the low five bits set indicate high-tag-number format // (two or more octets), which we don't support. if tag&0x1f == 0x1f { - b.err = fmt.Errorf("cryptobyte: high-tag number identifier octects not supported: 0x%x", tag) + b.err = fmt.Errorf("cryptobyte: high-tag number identifier octets not supported: 0x%x", tag) return } b.AddUint8(uint8(tag)) -- cgit v1.3