diff options
| author | Arpit Chakladar <arpitchakladar@gmail.com> | 2026-09-19 01:52:07 +0530 |
|---|---|---|
| committer | Arpit Chakladar <arpitchakladar@gmail.com> | 2026-09-19 01:52:07 +0530 |
| commit | 8cfd60b79cfbd9156f84a24b1c0e4a44e4960587 (patch) | |
| tree | 41c36466aae36a8cc18151bfaeb1a3fce2cdbe07 /modules/terminal | |
| parent | ade4bc05e36fe71c766deb4649a1a88520b33a6f (diff) | |
| download | home-manager-config-8cfd60b79cfbd9156f84a24b1c0e4a44e4960587.tar.gz home-manager-config-8cfd60b79cfbd9156f84a24b1c0e4a44e4960587.zip | |
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.
Diffstat (limited to 'modules/terminal')
| -rw-r--r-- | modules/terminal/kitty/default.nix | 3 |
1 files changed, 1 insertions, 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); }; }; |