imsnif/bandwhich

Separate network sniffer to different process to reduce sudo exposure

Open

#76 建立於 2020年1月5日

在 GitHub 查看
 (4 留言) (2 反應) (0 負責人)Rust (7,686 star) (237 fork)batch import
enhancementhelp wanted

描述

Right now bandwhich is built from 153 packages (from the cargo install count). That's a really large attack surface for an app that's going to run under sudo. Could the app be split into two processes? one of which runs as the user and handles the display, the other (with a smaller number of dependencies) as root to access just the network traffic and pass it to the user process.

I'd really like to be able to run the process as me. Then that process tries to sudo the network grabbing process with the required password if sudo requires it.

貢獻者指南

技術棧
rust
領域
clisecurity
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
RustLinux system programmingIPC concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Examine the current architecture in src/ to understand how network sniffing and display are integrated. Look for existing socket based IPC or process forking mechanisms. The comments may discuss alternative approaches, such as using a daemon process. Investigate using Unix domain sockets to pass data from a privileged sniffer process to an unprivileged display process, minimizing sudo exposure.