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 07:02:21PM -0500, 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 kernel upgrades. > > On Sat, Oct 22, 2016 at 6:26 PM, Petrusko <[1]petru...@riseup.net> > wrote: > > [2]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 Kernel > > > > [3]http://dirtycow.ninja/ > -- > Petrusko > PubKey EBE23AE5 > C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5 > _______________________________________________ > tor-relays mailing list > [4]tor-relays@lists.torproject.org > [5]https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > -- > Finding information, passing it along. ~SuperSluether > > References > > 1. mailto:petru...@riseup.net > 2. https://security-tracker.debian.org/tracker/CVE-2016-5195 > 3. http://dirtycow.ninja/ > 4. mailto:tor-relays@lists.torproject.org > 5. https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays -- Jason Jung 7942 B145 5E45 1D53 37C8 1204 8DA4 A1DB CBE6 35AE _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays