Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!news.albasani.net!.POSTED!not-for-mail
From: Andreas Kohlbach <ank@spamfence.net>
Newsgroups: comp.os.linux.misc
Subject: Re: Wikileaks Vault7 release--Linux vulnerabilities
Date: Sun, 12 Mar 2017 14:21:11 -0400
Organization: albasani.net
Lines: 20
Message-ID: <87d1dml5k8.fsf@usenet.ankman.de>
References: <ebd4396c-80bb-4f5c-9a23-ce7c4032d32b@googlegroups.com> <alpine.LNX.2.02.1703081604540.29335@darkstar.example.org> <8737emqk2i.fsf@usenet.ankman.de> <87fuimayix.fsf@LkoBDZeT.terraraq.uk> <alpine.LNX.2.02.1703091740050.31879@darkstar.example.org> <87k27xc81f.fsf@usenet.ankman.de> <oa08jj$oti$2@dont-email.me> <87bmt768p5.fsf@usenet.ankman.de> <oa1svj02tl1@news7.newsguy.com>
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: news.albasani.net PKYqnapSJYRZAO56zdbB6ZQl8CuYcE9+mTF5FZzYI6WU7Kzko8yvL1EPQsl0fOT7Bv3GuQtJg/RZjA7zDq0ByA==
NNTP-Posting-Date: Sun, 12 Mar 2017 18:21:12 +0000 (UTC)
Injection-Info: news.albasani.net; logging-data="JuhiB6XjZqf7IW4Ch7UJQ9CZGITgC+SprCJp/sqBmdGPTRq0SbDrQMM2BWZRt6vcodc9856duybeSOGwQG94JGRQLmcQHdYU6Fzw0aAJC0vweG1dW4T4EAJ/XP3qUP0Y"; mail-complaints-to="abuse@albasani.net"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
X-Face: '#R~-oJz-_!iXhczPJ;=w1(`5-uQ2$0qHB7KKDV,]VoAC!P?swaa#m|eB<DkOt*XH=~9C[g S^w)b,)1q,{P\7Z3H,N(^m.YKuYM//B{X:PvbDk.|:g:$wVr*3*)[K6F+k\z-s32+oB]YJPy11wuGGz'bQAk~1.b1[;M{^A2@bboIENBB:Wd:<Fm~r7OuiJA1g}7KC-T'>Du+
Cancel-Lock: sha1:ANh8baCv1rWpYinCyLioaoCe9vg= sha1:WQ+uES/1goMfdli5u/47YE49TSU=
X-Face-What-Is-It: Capture Bee from Galaga
Xref: csiph.com comp.os.linux.misc:19509

On Sat, 11 Mar 2017 17:16:19 -0500, Jean-David Beyer wrote:
>
> On 03/11/2017 12:10 PM, Andreas Kohlbach wrote:
>> I also had Windows in mind. In my opinion Linux distributions should
>> handle it the same way - just update without bugging the user other than
>> if there is an update which might not be wanted.
>
> I disagree. My distro runs SELinux by default. Even the super-user
> cannot modify some files unless he has the correct permissions. So even
> if the black hats cracked my computer and even if they got the superuser
> password, they would need to defeat the SELinux defense mechanisms besides.

What I wanted to say is have the system handle it without any user
interaction. You just create a new (root) cron table entry and call some
aptitude (or what ever updater a distribution has) there. Works for me
since years in Debian.
-- 
Andreas
You know you are a redneck if
you use the term "over yonder" more than once a month.