Ben Bailess:
> Hello:
>
>> When I used to enable to profile by using the aliases above, it would work
>> just fine, but today when I tried it on a fresh sid installation, no dice.
>> I get the following:
>>
>> apparmor="DENIED" operation="open"
>>
Hello:
> When I used to enable to profile by using the aliases above, it would work
> just fine, but today when I tried it on a fresh sid installation, no dice.
> I get the following:
>
> apparmor="DENIED" operation="open"
> profile="/usr/lib/chromium-browser/chromium-browser"
>
When I used to enable to profile by using the aliases above, it would work
just fine, but today when I tried it on a fresh sid installation, no dice.
I get the following:
apparmor="DENIED" operation="open"
profile="/usr/lib/chromium-browser/chromium-browser"
name="/run/NetworkManager/resolv.conf
Hello,
Am Montag, 19. Oktober 2015 schrieb Daniel Richard G.:
> I've never expected that we could get everyone to agree on a common
> set of paths, any more than we can get everyone to agree to drive on
> the same side of the road. But at least we can harmonize things
> between Debian and
Hello,
the aliases are a nice workaround, and the tunable might really solve
the problem, but the better solution is: get rid of the problem ;-)
I'd propose to change the packages so that all distributions use the
same path. That would also mean we don't need funny hacks to adjust the
profile
On Mon, 2015 Oct 19 23:13+0200, Christian Boltz wrote:
> Hello,
>
> the aliases are a nice workaround, and the tunable might really solve
> the problem, but the better solution is: get rid of the problem ;-)
>
> I'd propose to change the packages so that all distributions use the
> same path. That
Hi,
I think the changing paths in this profile should be handled with
a tunable, that maintainers can set accordingly to how Chromium is
packaged for their distribution.
Also, I don't think the profile file name actually matters. Does it?
Cheers,
--
intrigeri
| GnuPG key @
On Mon, 2014 Mar 31 13:30+0200, intrigeri wrote:
I think the changing paths in this profile should be handled with a
tunable, that maintainers can set accordingly to how Chromium is
packaged for their distribution.
Parameterizing the profile would be great, though then it would also be
a
Package: apparmor-profiles
Version: 2.7.103-4
The /etc/apparmor.d/usr.bin.chromium-browser profile appears to have
been taken verbatim from Ubuntu, and unfortunately is not usable with
Debian's packaging of the Chromium browser without a number of
modifications (starting with a file rename):
---
9 matches
Mail list logo
