Re: [security-announce] openSUSE-SU-2017:0969-1: important: Security update for apparmor

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [security-announce] openSUSE-SU-2017:0969-1: important: Security update for apparmor

Carlos E. R.-2


On 2017-04-10 15:08, [hidden email] wrote:

>    openSUSE Security Update: Security update for apparmor
> ______________________________________________________________________________
>
> Announcement ID:    openSUSE-SU-2017:0969-1
> Rating:             important
> References:         #1016259 #1017260 #1029696
> Cross-References:   CVE-2017-6507
> Affected Products:
>                     openSUSE Leap 42.2
>                     openSUSE Leap 42.1
> ______________________________________________________________________________
>
>    An update that solves one vulnerability and has two fixes
>    is now available.
You forgot to mention that YaST requires a reboot after installing this
patch.

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [security-announce] openSUSE-SU-2017:0969-1: important: Security update for apparmor

Christian Boltz-7
Hello,

Am Montag, 10. April 2017, 23:24:14 CEST schrieb Carlos E. R.:

> On 2017-04-10 15:08, [hidden email] wrote:
> >    openSUSE Security Update: Security update for apparmor
> >
> > ____________________________________________________________________
> >
> > Announcement ID:    openSUSE-SU-2017:0969-1
> > Rating:             important
> > References:         #1016259 #1017260 #1029696
> > Cross-References:   CVE-2017-6507
> >
> > Affected Products:
> >                     openSUSE Leap 42.2
> >                     openSUSE Leap 42.1

> You forgot to mention that YaST requires a reboot after installing
> this patch.

Well, it depends ;-)

If you are familiar enough with AppArmor so that you can check if all
profiles are loaded (including autogenerated profiles for lxd etc.) *and*
no running process misses its profile, then you don't need to reboot.
(Hint: aa-status is helpful to find this out.)

Otherwise the easy and boring solution is to reboot - it might be
superfluous (see above), but if in doubt, better error out on the safe
side.


Regards,

Christian Boltz
--
http://portal.suse.com/sdb/de/1997/09/maddin_kopieren.html
Der Artikel wird demnächst 7, sollte also in die zweite Klasse
Grundschule gehen, sobald die Ferien vorbei sind...
[Michael Behrens in suse-linux]

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [security-announce] openSUSE-SU-2017:0969-1: important: Security update for apparmor

Carlos E. R.-2
On 2017-04-11 00:52, Christian Boltz wrote:

> Hello,
>
> Am Montag, 10. April 2017, 23:24:14 CEST schrieb Carlos E. R.:
>> On 2017-04-10 15:08, [hidden email] wrote:
>>>    openSUSE Security Update: Security update for apparmor
>>>
>>> ____________________________________________________________________
>>>
>>> Announcement ID:    openSUSE-SU-2017:0969-1
>>> Rating:             important
>>> References:         #1016259 #1017260 #1029696
>>> Cross-References:   CVE-2017-6507
>>>
>>> Affected Products:
>>>                     openSUSE Leap 42.2
>>>                     openSUSE Leap 42.1
>
>> You forgot to mention that YaST requires a reboot after installing
>> this patch.
>
> Well, it depends ;-)
Well, YaST informs the user that a reboot is necessary.
I'm not saying that it is or that it isn't.

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Loading...