5e645a7be7
Apparently on FreeBSD one cannot unlink shared mem if it is not created with write permissions. Adding IWRITE to the permissions when creating the shared memory is harmless. It means any process running as the user can either write to the file or delete it. Deleting was already possible except on FreeBSD. As for writing, it's needed on FreeBSD for shared memory to be useable at all, and since processes running as the user can already completely access all their data, kitty config files, tty pipes, etc. allowing them to write to the SHM used here doesnt grant any significant new capability, since they could just write to ssh.conf in the kitty config folder to get the ssh kitten to do whatever they like. Fixes #5928
= kitty - the fast, feature-rich, cross-platform, GPU based terminal See https://sw.kovidgoyal.net/kitty/[the kitty website]. image:https://github.com/kovidgoyal/kitty/workflows/CI/badge.svg["Build status", link="https://github.com/kovidgoyal/kitty/actions?query=workflow%3ACI"] https://sw.kovidgoyal.net/kitty/faq/[Frequently Asked Questions] To ask other questions about kitty usage, use either the https://github.com/kovidgoyal/kitty/discussions/[discussions on GitHub] or the https://www.reddit.com/r/KittyTerminal[Reddit community] Packaging status in various repositories: image:https://repology.org/badge/vertical-allrepos/kitty.svg["Packaging status", link="https://repology.org/project/kitty/versions"]