From: Alberto Leiva Popper <ydahhrk@gmail.com>
Date: Mon, 26 Jun 2023 21:47:30 +0000 (-0600)
Subject: Remove a bunch of uprofessional jargon
X-Git-Tag: 1.6.0~81
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4c1dba27917715550fb2e6367ff20fa4efe89ac3;p=thirdparty%2FFORT-validator.git

Remove a bunch of uprofessional jargon
---

diff --git a/configure.ac b/configure.ac
index c7e7870c..4ed333c8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -40,8 +40,8 @@ AM_CONDITIONAL([BACKTRACE_ENABLED], [test "x$have_backtrace" != "xno"])
 # By the way: Apparently PKG_CHECK_MODULES is poor practice now. I can't tell;
 # it's always the same guy complaining about it in Stack Overflow.
 # (Main one: https://stackoverflow.com/questions/10220946)
-# But I couldn't make check work with AC_SEARCH_LIBS, and (probably due to
-# typical obscure bullshit autotools reasoning) I have no idea why.
+# But I couldn't make check work with AC_SEARCH_LIBS, probably because of some
+# obscure autotools reasoning.
 PKG_CHECK_MODULES([JANSSON], [jansson])
 PKG_CHECK_MODULES([CURL], [libcurl])
 PKG_CHECK_MODULES([XML2], [libxml-2.0])
diff --git a/src/crypto/base64.c b/src/crypto/base64.c
index f839bc78..a3c21e24 100644
--- a/src/crypto/base64.c
+++ b/src/crypto/base64.c
@@ -46,7 +46,7 @@ base64_decode(BIO *in, unsigned char *out, bool has_nl, size_t out_len,
 	unsigned long error;
 
 	/*
-	 * BTW: The libcrypto API was clearly designed by fucking idiots.
+	 * BTW: The libcrypto API is perplexing.
 	 * Peeking at the error stack is the only way I found to figure out
 	 * whether some of the functions error'd.
 	 * But since it's not documented that it's supposed to work this way,
diff --git a/src/extension.c b/src/extension.c
index d8bd58ed..bc8b43d7 100644
--- a/src/extension.c
+++ b/src/extension.c
@@ -274,8 +274,8 @@ validate_public_key_hash(X509 *cert, ASN1_OCTET_STRING *hash)
 	 * Bottom line, I don't know. But better be safe than sorry, so here's
 	 * the validation.
 	 *
-	 * Shit. I feel like I'm losing so much performance because the RFCs
-	 * are so wishy-washy about what is our realm and what is not.
+	 * I feel like I'm losing so much performance because the RFCs are so
+	 * wishy-washy about what is our realm and what is not.
 	 */
 
 	/* Get the SPK (ask libcrypto) */
diff --git a/src/line_file.c b/src/line_file.c
index ffce6c27..bb959e26 100644
--- a/src/line_file.c
+++ b/src/line_file.c
@@ -74,10 +74,9 @@ lfile_read(struct line_file *lfile, char **result)
 	 * - If the file is empty, or all that's left is an empty line, it
 	 *   (confusingly) returns -1. errno will be 0, feof() should return
 	 *   1, ferror() should return 0.
-	 * - The fact that it returns the newline in the buffer is puzzling,
-	 *   because who the fuck wants that nonsense. You will want to remove
-	 *   it, BUT DON'T SWEAT IT IF IT'S NOT THERE, because the last line of
-	 *   the file might not be newline-terminated.
+	 * - It includes the newline in the result, which is puzzling. You will
+	 *   want to remove it, BUT DON'T SWEAT IT IF IT'S NOT THERE, because
+	 *   the last line of the file might not be newline-terminated.
 	 * - The string WILL be NULL-terminated, but the NULL chara will not be
 	 *   included in the returned length. BUT IT'S THERE. Don't worry about
 	 *   writing past the allocated space on the last line.
diff --git a/src/log.c b/src/log.c
index bb3466e3..42b33c66 100644
--- a/src/log.c
+++ b/src/log.c
@@ -188,8 +188,8 @@ register_signal_handlers(void)
 	 * > happen
 	 * (Documentation of CURLOPT_NOSIGNAL)
 	 *
-	 * All SIGPIPE means is "the peer closed the connection for some reason,
-	 * fuck you."
+	 * All SIGPIPE means is "the peer closed the connection for some
+	 * reason."
 	 * Which is a normal I/O error, and should be handled by the normal
 	 * error propagation logic, not by a signal handler.
 	 * So, ignore SIGPIPE.
diff --git a/src/object/certificate.c b/src/object/certificate.c
index c6f61efd..e8e668f9 100644
--- a/src/object/certificate.c
+++ b/src/object/certificate.c
@@ -726,8 +726,8 @@ certificate_validate_signature(X509 *cert, ANY_t *signedData,
 	 *
 	 * The first one sounded less efficient but more straightforward, but
 	 * I couldn't pull it off because there's some memory bug with asn1c's
-	 * encoding function that core dumps the fuck out of everything. It's
-	 * caused by undefined behavior that triggers who knows where.
+	 * encoding function that crashes everything. It's caused by undefined
+	 * behavior that triggers who knows where.
 	 *
 	 * There's another problem with that approach: If we DER-encode the
 	 * signedAttrs, we have no guarantee that the signature will match