Hi,
I have one relay on CentOS 6 and one on CentOS 7. The one running CentOS 7
hasn't had the 0.2.8.8 update yet and so is still running 0.2.8.7. The one
running CentOS 6 has had the latest update.
Is there a problem with getting CentOS 7 packages out?
How much of a problem is this? Both now
https://security-tracker.debian.org/tracker/CVE-2016-5195
Remember,
to know your current debian linux kernel : uname -a
If your kernel is not up to date :
apt-get update && apt-get dist-upgrade && reboot
I :
> Dirty COW (CVE-2016-5195) is a privilege escalation vulnerability in the
> Linux Ker
Would it be acceptable to configure unattended-upgrades to automatically
reboot the system when required? I already have it configured to check for
and install all updates to Ubuntu and Tor once a day, but I still need to
manually reboot to apply kernel upgrades.
On Sat, Oct 22, 2016 at 6:26 PM, P
I don't think it would be a terrible idea but it is always possible that
your server will fail to reboot after a kernel upgrade. This leaves it
offline without a general idea of why it is offline. I do use
unattended-upgrades to automatically restart most services though.
On Sat, Oct 22, 2016 at
On 10/22/2016 08:02 PM, Tristan wrote:
> Would it be acceptable to configure unattended-upgrades to automatically
> reboot the system when required? I already have it configured to check
> for and install all updates to Ubuntu and Tor once a day, but I still
> need to manually reboot to apply kerne
Hate to tell you this, but both problems are still a reality whether the
machine reboots automatically or not. If I manually reboot for a kernel
update that breaks network access, I still won't have SSH. And if I reboot
manually after every kernel update, my stability will still suffer.
On Oct 22,
