https://flow.halvo.me/tags/c-cpp/ Recent content in C-Cpp on Flow With Halvo Hugo en Thu, 29 Jun 2023 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-file-io/ Thu, 29 Jun 2023 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-file-io/ A breezy guide to keeping file operations safe: validate paths, lock down permissions, and never let a privileged process wander into a user’s temp folder. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-concurrency/ Fri, 27 Jan 2023 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-concurrency/ A light‑hearted rant about why a plain‑old <code>mutex</code> is the hero of secure C/C++ concurrency, why <code>goto</code> is still secretly useful, and how to keep your locks short and your bugs shorter. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-set-to-null-after-free/ Wed, 17 Aug 2022 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-set-to-null-after-free/ A breezy, slightly tongue‑in‑cheek look at why setting pointers to <code>NULL</code> right after <code>free</code> (and a few related memory‑management niceties) can save you from nasty use‑after‑free bugs, memory leaks, and the occasional midnight debugging panic. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-2/ Sat, 13 Aug 2022 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-2/ The sequel to the null‑termination saga, now tackling <code>strcat</code>, <code>strncat</code>, <code>strlcat</code>, and friends—plus a quick table to keep your concatenations from turning into catastrophes. https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-1/ Wed, 01 Sep 2021 00:00:00 +0000 https://flow.halvo.me/posts/summations-of-secure-coding-in-c-and-cpp-always-null-terminate-part-1/ A light‑hearted reminder that every character buffer deserves a <code>'\0'</code>—otherwise you’re inviting buffer overflows, stray reads, and a lot of debugging grief.