Hi Daniel,
Daniel Richard G. wrote (21 Jun 2014 00:33:38 GMT) :
On Thu, 2014 Jun 12 8:03+0200, Yves-Alexis Perez wrote:
In any case, please provide a working patch against the current
package. I won't do anything more on this until someone actually test
the changes.
# rm -f
On Sat, 2014 Jun 21 09:30+0200, intrigeri wrote:
Two process notes:
1. The problem you've raised on this bug since message #98 is a
different issue than #747252, that was rightfully closed as its
practical consequences were resolved already.
Was the point of this exercise to provide
On Thu, 2014 Jun 12 12:20+0200, intrigeri wrote:
I fail to see what problems this can cause: now that the lightdm-guest-
session profile was removed, AFAICT that abstraction is not included
from any profile anymore, so it's a noop. If I missed anything, please
enlighten me. Thanks in advance
On Thu, 2014 Jun 12 8:03+0200, Yves-Alexis Perez wrote:
Well, I followed intrigeri remark: since guest session is not working
anyway, there's no point in having a broken AppArmor profile for that.
That's not the case for the lightdm_chromium-browser one, is it?
Uh, yes, it is. First of all,
On jeu., 2014-06-12 at 00:49 -0400, Daniel Richard G. wrote:
Yves, you removed /etc/apparmor.d/lightdm-guest-session from the
package (via a debhelper exclusion directive), but you didn't exclude
/etc/apparmor.d/abstractions/lightdm_chromium-browser, which is the
profile that was generating
Hi,
Daniel Richard G. wrote (12 Jun 2014 04:49:20 GMT) :
Yves, you removed /etc/apparmor.d/lightdm-guest-session from the
package (via a debhelper exclusion directive), but you didn't exclude
/etc/apparmor.d/abstractions/lightdm_chromium-browser, which is the
profile that was generating the
Yves, you removed /etc/apparmor.d/lightdm-guest-session from the
package (via a debhelper exclusion directive), but you didn't exclude
/etc/apparmor.d/abstractions/lightdm_chromium-browser, which is the
profile that was generating the error in the first place _
On Fri, 2014 Jun 6 11:22+0200, intrigeri wrote:
Well, that's frustrating :( This is on sid?
Yes.
I haven't seen that error on jessie after commenting out the
new-AppArmor-
syntax bits, so it may still be possible to straighten things out easily
for testing.
(I don't know why sid would be
Hi,
[Dropping Kees from the Cc list: he's happy to maintain the AppArmor
userspace in Debian, but in the beginning of the Jessie dev cycle, he
told me he would rather leave the profiles work to others.]
Daniel Richard G. wrote (07 Jun 2014 08:24:39 GMT) :
I haven't seen that error on jessie
Daniel Richard G. wrote (05 Jun 2014 17:07:01 GMT) :
# apparmor_parser -r /etc/apparmor.d/lightdm-guest-session
profile has merged rule with conflicting x modifiers ERROR processing
regexs for profile /usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-
session, failed to load
Well, that's
Hi,
Yves-Alexis Perez wrote (06 May 2014 22:21:53 GMT) :
I gave it a quick try as part of my work on AppArmor support in
Debian. The attached patch suppresses the parser errors on unknown
ptrace and signal keywords, but then:
# apparmor_parser -r /etc/apparmor.d/lightdm-guest-session
profile has
On jeu., 2014-06-05 at 11:00 +0200, intrigeri wrote:
I'm ok for that, but if someone could actually provide a
working/tested
profile it'd help. I'd rather not upload that stuff twice or thrice
just
to pass one error at a time…
It's unclear to me what working/tested means in this
Hi,
Yves-Alexis Perez wrote (05 Jun 2014 09:32:52 GMT) :
It'd help if the original reporter could state its expectations.
I agree.
tl;dr: dropping this profile from the lightdm package would address
*my* expectations just fine, ease the work to improve Debian's
AppArmor support, and make
On Thu, Jun 5, 2014 at 4:04 PM, intrigeri intrig...@debian.org wrote:
Yves-Alexis Perez wrote (05 Jun 2014 09:32:52 GMT) :
It'd help if the original reporter could state its expectations.
I agree.
tl;dr: dropping this profile from the lightdm package would address
*my* expectations just
On Thu, 2014 Jun 5 11:00+0200, intrigeri wrote:
I gave it a quick try as part of my work on AppArmor support in
Debian. The attached patch suppresses the parser errors on unknown
ptrace and signal keywords, but then:
# apparmor_parser -r /etc/apparmor.d/lightdm-guest-session
profile has
Package: lightdm
Version: 1.10.1-1
Severity: normal
Apparmor fails to start, error message indicates syntax error.
Apparmor error messages are too cryptic to me to understand what is the exact
problem.
Error message:
apparmor[12873]: Starting AppArmor profiles:AppArmor parser error for
On mar., 2014-05-06 at 21:06 +0200, Marek Królikowski wrote:
Apparmor fails to start, error message indicates syntax error.
Apparmor error messages are too cryptic to me to understand what is
the exact problem.
Error message:
apparmor[12873]: Starting AppArmor profiles:AppArmor parser
On Tue, 2014 May 6 21:40+0200, Yves-Alexis Perez wrote:
apparmor[12873]: Starting AppArmor profiles:AppArmor parser error
for /etc/apparmor.d/lightdm-guest-session in
/etc/apparmor.d/abstractions/lightdm_chromium-browser at line 20:
syntax error, unexpected TOK_CONDID, expecting TOK_ID
On mar., 2014-05-06 at 17:33 -0400, Daniel Richard G. wrote:
That said, I'm not seeing an error from lightdm_chromium-browser:20 as
Marek has. As he appears to be running sid (whereas I'm running jessie),
and so should have same/newer versions of everything, I've no idea what
may be going on
On Tue, 2014 May 6 23:39+0200, Yves-Alexis Perez wrote:
Line 20 is:
# Allow ptracing processes in the chromium child profile
ptrace peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
Oh, okay, so it's different in sid. In jessie, it's capability
sys_admin, which otherwise appears
On mar., 2014-05-06 at 17:57 -0400, Daniel Richard G. wrote:
On Tue, 2014 May 6 23:39+0200, Yves-Alexis Perez wrote:
Line 20 is:
# Allow ptracing processes in the chromium child profile
ptrace peer=/usr/lib/lightdm/lightdm-guest-session//chromium,
Oh, okay, so it's different
21 matches
Mail list logo
