From 8cfd60b79cfbd9156f84a24b1c0e4a44e4960587 Mon Sep 17 00:00:00 2001 From: Arpit Chakladar Date: Sat, 19 Sep 2026 01:52:07 +0530 Subject: fix(terminal/kitty): stopped using allow_remote_control for kitty allow_remote_control has been a pretty open security flaw in kitty configurations due to its remote code execution potential. The rest of the config doesn't use kitten messaging so disabling it is a no brainer. --- modules/terminal/kitty/default.nix | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/modules/terminal/kitty/default.nix b/modules/terminal/kitty/default.nix index 38f74ac..e7a5fbb 100644 --- a/modules/terminal/kitty/default.nix +++ b/modules/terminal/kitty/default.nix @@ -37,8 +37,7 @@ scrollbar_indicator_opacity = "0.5"; dynamic_background_opacity = false; enable_audio_bell = false; - allow_remote_control = "yes"; - listen_on = "unix:/tmp/kitty"; + allow_remote_control = "no"; shell = lib.mkIf config.terminal.zsh.enable (lib.getExe config.terminal.zsh.package); }; }; -- cgit v1.2.3