srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/tests/test_privileges.cpp
diff options
context:
space:
mode:
authorsrdusr <[email protected]>2024-05-27 22:00:00 +0200
committersrdusr <[email protected]>2024-05-27 22:00:00 +0200
commitb565d7d9c47ca1ec5af0effd828431ee96027d60 (patch)
treefbe0c9c897e78f507443507354d5b1d8fb851099 /tests/test_privileges.cpp
parentfbedc55d5aa861c381701c9f913b34ee7ab57ec4 (diff)
downloadpacketeer-b565d7d9c47ca1ec5af0effd828431ee96027d60.tar.gz
packeteer-b565d7d9c47ca1ec5af0effd828431ee96027d60.zip
Rename project from wireframe to packeteer
Decided on the name after weighing alternatives in NAMES.md: packeteer (packet + -eer, "one who wields packets") fit the project's actual scope better than the wire/frame pun once it had grown into full L2-L7 dissection, reassembly, checksums, privilege dropping, and dual TUI/GUI frontends. No existing packet-capture project uses the name; the one real-world collision (Packeteer, Inc., a networking company acquired and folded into Blue Coat/Symantec by 2008) is long defunct. Mechanical rename throughout: CMake project/target names, the wireframe:: namespace and include/wireframe/ directory (git mv, history preserved), every #include path, CLI/GUI help text, and the project's own working directory. NAMES.md rewritten to record the decision instead of leaving stale self-referential etymology behind from the blind rename pass. Verified after every step: full rebuild (all four targets, no warnings) and the full test suite (128/128 cases, 366/366 assertions) both from a fresh reconfigure and again after the directory move.
Diffstat (limited to 'tests/test_privileges.cpp')
-rw-r--r--tests/test_privileges.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/test_privileges.cpp b/tests/test_privileges.cpp
index 287d654..99951b8 100644
--- a/tests/test_privileges.cpp
+++ b/tests/test_privileges.cpp
@@ -1,7 +1,7 @@
#include <doctest/doctest.h>
#include <unistd.h>
-#include "wireframe/privileges.hpp"
+#include "packeteer/privileges.hpp"
// The actual drop sequence (setuid/setgid) can only be meaningfully
// exercised by literally running as root, which a unit test shouldn't
@@ -14,5 +14,5 @@
// touch privileges it doesn't have.
TEST_CASE("drop_privileges_if_root is a no-op when not running as root") {
if (geteuid() == 0) return; // this test only makes sense unprivileged
- CHECK_FALSE(wireframe::drop_privileges_if_root().has_value());
+ CHECK_FALSE(packeteer::drop_privileges_if_root().has_value());
}