Handle SIGPIPE

Fix `SIGPIPE` being ignored, which would cause the `mullvad-cli` to
panic if it received a `PIPE` signal (e.g. it was piped into `echo`).

Author: MarkusPettersson98

CHANGELOG.md

@@ -32,6 +32,8 @@ Line wrap the file at 100 chars.                                              Th
 - Remove "Any" option for tunnel protocol. The default is now WireGuard.
 
 ### Fixed
+- Fix `mullvad-cli` panicking if it tried to write to a closed pipe on Linux and macOS.
+
 #### macOS
 - Fix routing issue caused by upgrading `tun`.
 

Cargo.lock

@@ -29,6 +29,7 @@ talpid-types = { path = "../talpid-types" }
 
 mullvad-management-interface = { path = "../mullvad-management-interface" }
 tokio = { workspace = true, features =  ["macros", "rt-multi-thread", "fs"] }
+sigpipe = "0.1"
 serde = { workspace = true }
 serde_json = { workspace = true }
 

mullvad-cli/Cargo.toml

@@ -152,6 +152,12 @@ enum Cli {
 
 #[tokio::main]
 async fn main() -> Result<()> {
+    // Handle SIGPIPE
+    // https://stackoverflow.com/questions/65755853/simple-word-count-rust-program-outputs-valid-stdout-but-panicks-when-piped-to-he/65760807
+    // https://github.com/rust-lang/rust/issues/119980
+    // https://github.com/typst/typst/pull/5444
+    sigpipe::reset();
+
     match Cli::parse() {
         Cli::Account(cmd) => cmd.handle().await,
         Cli::Bridge(cmd) => cmd.handle().await,