make a note that saved session data can be read by any process that runs as the user

This commit is contained in:
Kovid Goyal 2026-10-16 17:21:40 +05:30
parent 01a2aabc56
commit dad7089d10
No known key found for this signature in database
GPG key ID: 06BC317B515ACE7C
2 changed files with 5 additions and 3 deletions

View file

@ -290,7 +290,8 @@ not started again, since they could have been run for their effects, like
The saved state, which includes the scrollback and the environment variables
of every kitty instance, is encrypted, with a separate random key for every
kitty instance, stored in your login keychain. The keys are deleted when the
kitty instance, stored in your login keychain. Note that despite the encryption
any process that runs as you can read the saved session data. The keys are deleted when the
state is restored, so any copies of it left on disk or in backups cannot be
read. kitty never shows any keychain prompts for this. If the keychain needs
user interaction, the state is not saved or not restored. This happens if:

View file

@ -3183,8 +3183,9 @@ If several kitty instances were running, each is restored as a separate kitty in
command line arguments and environment it originally had. Programs that were running in windows,
other than the shell, are not started again. The saved session is used only once, and only when
kitty is started without :option:`kitty --session` or a command to run. The saved state is encrypted,
with a key stored in your login keychain, and is deleted once it has been restored. Currently, this
works only on macOS.
with a key stored in your login keychain, and is deleted once it has been restored. Note that
despite the encryption any process that runs as you can access the stored session data.
Currently, this works only on macOS.
See :ref:`restore_after_logout` for details.
""",
)