how to create a software wrapper for trojan

The only problem I have experienced does not apply to setuid-to-/root/ binaries either, it was so that I did not understand all of unix user ids and forgot to set the real user ID, saved user ID and their group ID equivalents, this meant that a program that /drops/ privileges can still gain them back. The only problem I have heard of with setuid wrappers is that they can overwrite themselves with a trojan if they exploited, but this is not relevant for setuid-to-/root/ binaries as any exploit on a process running as root means you're screwed anyway. However, I've been told this approach is frowned upon Since the indicator is in python, I could have a binary with setuid bit set written in C. I assume it can be trusted as it comes pre-installed with the distro, unlike some quickly hacked up setuid wrapper or daemon. If the intended audience does not have 'CLIphobia', sudo could be really great here if 'each time' is within 15 minutes.īut from a security point of view, I'd recommend pkexec. Run command with pkexec each time ( which I kind of want to avoid for the sake of user experience )

It's a trade off between security and usability. There's not really one correct answer to this question.

How to create a software wrapper for trojan