Besides other changes, this update mitigates this vulnerability: https://access.redhat.com/security/cve/CVE-2015-3243
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2015-11039Please login to add feedback.
| 0 | 0 | Test Case rsyslog |
This update has been submitted for testing by theinric.
Taskotron: depcheck test PASSED on i386. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/102957/steps/runtask/logs/stdio (results are informative only)
Taskotron: depcheck test PASSED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/102957/steps/runtask/logs/stdio (results are informative only)
This update is currently being pushed to the Fedora 22 testing updates repository.
This update has been pushed to testing
This update fixes bug 1224538 for me. I can't comment on the logrotate issue because I haven't been running this update for long enough.
LGTM =)
Critical path update approved
This update has reached the stable karma threshold and will be pushed to the stable updates repository
Taskotron: upgradepath test PASSED on noarch. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/105852/steps/runtask/logs/stdio (results are informative only)
This update is currently being pushed to the Fedora 22 stable updates repository.
Before installing this update /var/log/secure was empty and updates were being written to the rolled secure-20150714 logfile. After installing this update I have some old content in /var/log/secure (with timestamps from yesterday) but new logs are still going to /var/log/secure-20150714, so the logs aren't even in date order now!
This update has been pushed to stable