From fb14e1e7ddf2e96d93ed799f0fbf48d2d2cca8ca Mon Sep 17 00:00:00 2001 From: Winni Neessen Date: Wed, 16 Oct 2024 10:38:13 +0200 Subject: [PATCH] Fix typos in auth mechanism comments Corrected multiple instances of "mechansim" to "mechanism" in the comments describing SASL authentication methods to improve readability and maintain code quality. --- auth.go | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/auth.go b/auth.go index a088274..7888819 100644 --- a/auth.go +++ b/auth.go @@ -35,7 +35,7 @@ const ( // IETF draft. The IETF draft is more lax than the MS spec, therefore we follow the I-D, which // automatically matches the MS spec. // - // Since the "LOGIN" SASL authentication mechansim transmits the username and password in + // Since the "LOGIN" SASL authentication mechanism transmits the username and password in // plaintext over the internet connection, we only allow this mechanism over a TLS secured // connection. // @@ -51,7 +51,7 @@ const ( // SMTPAuthPlain is the "PLAIN" authentication mechanism as described in RFC 4616. // - // Since the "PLAIN" SASL authentication mechansim transmits the username and password in + // Since the "PLAIN" SASL authentication mechanism transmits the username and password in // plaintext over the internet connection, we only allow this mechanism over a TLS secured // connection. // @@ -76,7 +76,7 @@ const ( // // SCRAM-SHA-X-PLUS authentication require TLS channel bindings to protect against MitM attacks and // to guarantee that the integrity of the transport layer is preserved throughout the authentication - // process. Therefore we only allow this mechansim over a TLS secured connection. + // process. Therefore we only allow this mechanism over a TLS secured connection. // // SCRAM-SHA-1-PLUS is still considered secure for certain applications, particularly when used as part // of a challenge-response authentication mechanism (as we use it). However, it is generally @@ -95,7 +95,7 @@ const ( // // SCRAM-SHA-X-PLUS authentication require TLS channel bindings to protect against MitM attacks and // to guarantee that the integrity of the transport layer is preserved throughout the authentication - // process. Therefore we only allow this mechansim over a TLS secured connection. + // process. Therefore we only allow this mechanism over a TLS secured connection. // // https://datatracker.ietf.org/doc/html/rfc7677 SMTPAuthSCRAMSHA256PLUS SMTPAuthType = "SCRAM-SHA-256-PLUS"