Back to bug 2225088
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-07-24 09:51:50 UTC | Pool ID | sst_security_special_projects_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-07-24 09:53:13 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-163097 | |
| Red Hat One Jira (issues.redhat.com) | 2023-07-24 09:53:20 UTC | Link ID | Red Hat Issue Tracker SECENGSP-5307 | |
| Attila Lakatos | 2023-07-24 10:08:03 UTC | Status | NEW | POST |
| Attila Lakatos | 2023-08-07 08:47:13 UTC | Status | POST | MODIFIED |
| Doc Text | Cause: Rsyslog was not able to drop capabilities when executed as a normal user or in a containerized environment. Consequence: Rsyslog exited at startup. Fix: With the fix, if the process does not any capabilities, rsyslog will try to drop them. Result: Rsyslog is able to start even if no capabilities are present. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Attila Lakatos | 2023-08-07 09:02:55 UTC | Doc Text | Cause: Rsyslog was not able to drop capabilities when executed as a normal user or in a containerized environment. Consequence: Rsyslog exited at startup. Fix: With the fix, if the process does not any capabilities, rsyslog will try to drop them. Result: Rsyslog is able to start even if no capabilities are present. | Cause: Rsyslog was not able to drop capabilities when executed as a normal user or in a containerized environment. Consequence: Rsyslog exited at startup. Fix: With the fix, if the process does not any capabilities, rsyslog will not try to drop them. Result: Rsyslog is able to start even if no capabilities are present. |
| AutoMiloš | 2023-08-07 09:36:02 UTC | Fixed In Version | rsyslog-8.2102.0-113.el9_2.1 | |
| Keywords | AutoVerified | |||
| errata-xmlrpc | 2023-08-09 08:13:56 UTC | Status | MODIFIED | ON_QA |
Back to bug 2225088