Unfortunately I cannot reproduce the error, it has not happened before (although I've only used a newer version of Terminator for a few weak).
It shouldn't be any problem with sending encryption keys on a local socket, other processes cannot open socket files in /proc/[pid]/fd/, and I don't think there is any other way for them to read the communication. SCM_CREDENTIALS in combination with readlink over /proc/[pid]/exe can be used for authenticate the process.
All Unix-like OSes should support SCM_RIGHTS and SCM_CREDENTIALS.
Okay, thanks, I will use --no-dbus.
Unfortunately I cannot reproduce the error, it has not happened before (although I've only used a newer version of Terminator for a few weak).
It shouldn't be any problem with sending encryption keys on a local socket, other processes cannot open socket files in /proc/[pid]/fd/, and I don't think there is any other way for them to read the communication. SCM_CREDENTIALS in combination with readlink over /proc/[pid]/exe can be used for authenticate the process.
All Unix-like OSes should support SCM_RIGHTS and SCM_CREDENTIALS.