Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Well, first, this isn't and "application." This is a pair of binaries with associated configuration, library, and key store files. This pair of binaries was was written to allow *nix hosts to connect to a very-Windows-centric Enterprise Scheduling application set. How Windows-centric? The actual file names are arcane gobbledygook conforming to the ancient MS-DOS 8.3 naming convention. Commented Mar 21, 2017 at 20:34
  • So, I have a service manager and an agent. My unit file starts the service manager, and the service manager starts the agent. The agent then complains it can't read its key store file and quits. Prior to my change to init_exec_t I got four sets of the above SELinux messages in the audit log. Afterward I got one set. That looked like progress to me. I'm totally willing to use a better choice. Having said that semanage fcontext -l | grep bin_exec tells me that bin_exec_t and sbin_exec_t don't appear to be valid choices. Commented Mar 21, 2017 at 20:39