| Summary: | dbus-daemon-launch-helper: log to syslog on failure | ||
|---|---|---|---|
| Product: | dbus | Reporter: | Simon McVittie <smcv> |
| Component: | core | Assignee: | D-Bus Maintainers <dbus> |
| Status: | RESOLVED MOVED | QA Contact: | D-Bus Maintainers <dbus> |
| Severity: | enhancement | ||
| Priority: | low | Keywords: | patch |
| Version: | 1.8 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | dbus-daemon-launch-helper: on failure, log it to system log before exiting | ||
|
Description
Simon McVittie
2014-10-16 19:27:59 UTC
Created attachment 107946 [details] [review] dbus-daemon-launch-helper: on failure, log it to system log before exiting The communication channel between the launch helper and the dbus-daemon is rather limited, so any extra hints are welcome. --- We should probably introduce a new log level that isn't AUTHPRIV so it goes to the normal syslog instead of auth.log, or use LOG_INFO, or something. Thoughts? Note that this is in security-sensitive (setuid) code. If we couldn't safely call openlog() and syslog() in security-sensitive code, I suspect a lot of privileged processes would already be doomed, notably sudo... but it does increase the attack surface. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/115. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.