srdusr
aboutsummaryrefslogtreecommitdiffstats
path: root/PLAN.md
diff options
context:
space:
mode:
Diffstat (limited to 'PLAN.md')
-rw-r--r--PLAN.md25
1 files changed, 23 insertions, 2 deletions
diff --git a/PLAN.md b/PLAN.md
index d874f69..28b80e3 100644
--- a/PLAN.md
+++ b/PLAN.md
@@ -146,8 +146,29 @@ configured once before `ctrl+r` starts an attack and apply for that run
only - matching Burp, which doesn't retroactively re-grep already-fired
requests if you change the options mid-attack.
-Still open from "worth considering": CA install UX per OS, multiple
-proxy listeners and upstream proxy chaining. Neither is started yet.
+Shipped since: CA install UX per OS (`mitmuxd -install-ca`) - generates
+the CA if needed, prints copy-pasteable install steps for the detected
+platform, and exits without starting the proxy. Deliberately
+instructions-only, never auto-executing: trust-store tooling varies
+enough across Linux distros that guessing wrong and running the wrong
+command unattended is worse than asking, and installing a root CA is a
+system-wide trust change that affects every TLS connection on the
+machine, not just mitmux's own traffic - the user running the printed
+command themselves keeps them in control of that. On Linux, detects
+`trust` (p11-kit - Arch, and Fedora also ships it)/`update-ca-trust`
+(RHEL/Fedora/CentOS)/`update-ca-certificates` (Debian/Ubuntu/Gentoo)
+via PATH lookup and picks whichever is actually present, plus separate
+`certutil` (NSS) instructions for Firefox/Chrome's own certificate
+store, which doesn't always follow the system trust store on Linux.
+macOS (`security add-trusted-cert`) and Windows (`certutil -addstore` /
+`Import-Certificate`) instructions are implemented but, unlike the
+Linux path, not verified live - no macOS/Windows machine was available
+to test against; only the command text itself (sourced from each
+platform's standard, documented tooling) is confirmed correct by
+inspection.
+
+Still open from "worth considering": multiple proxy listeners and
+upstream proxy chaining. Not started yet.
Skipped deliberately (from the research, matches this tool's stated
scope): active/passive vulnerability scanning, plugin marketplace,