** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
I'll check the current status
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
Title:
Apparmor profile in 22.04 jammy - fails to start when printing enabled
There is another ongoing apparmor sru for jammy[1] that is using the
same version number. That one has been uploaded already for some time
and the bug shows it's making progress. I'm not going to ask this change
here to be included in that one, because it's further in the SRU process
than this one
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Changed in: apparmor (Ubuntu Jammy)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
** Changed in: apparmor (Ubuntu)
Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack
(ahasenack)
--
You received this bug notification
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
Users who have:
a) opted in to confining samba with apparmor (by installing
apparmor-profiles); and
b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;
will experience an error in starting the smbd service in jammy:
** Description changed:
[Impact]
- Path to samba-bgqd is wrong on 22.04.
- Changing from /usr/lib*/samba/samba-bgqd into
/usr/lib/@{multiarch}/samba/samba-bgqd to align different architectures.
- The @{multiarch} was initialized at the code before.
- Before fixing it might confuse users
Removing the samba task as there is nothing to do there for jammy.
** No longer affects: samba (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
** Description changed:
+ [Impact]
+
+ Path to samba-bgqd is wrong on 22.04.
+ Changing from /usr/lib*/samba/samba-bgqd into
/usr/lib/@{multiarch}/samba/samba-bgqd to align different architectures.
+ The @{multiarch} was initialized at the code before.
+ Before fixing it might confuse users
Updated bug description with:
Moreover, the dmesg output failed and it has showed that the 'k' flag is
required for the *.tdb files within /etc/apparmor.d/abstractions/samba.
It is required to close that bug in professional way, because the flag
is also affected by samba-bgqd.
** Description
** Description changed:
See bug here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1191532
Fix was backported, but the path to samba-bgqd is wrong on 22.04.
Currently apparmor profile has it like this:
/usr/lib*/samba/samba-bgqd
When in fact 22.04 has it on
Waiting for a review of MP
** Changed in: apparmor (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
Title:
** Merge proposal linked:
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/apparmor/+git/apparmor/+merge/427973
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
>From an SRU perspective bug 1703821 is similar to this, except for
dovecot in Bionic. In both cases, a workaround is trivially available
since a user can safely modify the profile directly in /etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hm, I see, it's obviously not just samba-bgqd. Hmm...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
Title:
Apparmor profile in 22.04 jammy - fails to start when
I see your point, and I find the one about "fixing it the Kinetic way"
especially convincing, it may save us headaches in the future, and may
help with backports. My concern is that other packages or scripts users
wrote and tested on Jammy systems refer to the "wrong" path
The other argument I have against fixing this in apparmor, is that this
fix is for jammy only. It's not present in kinetic. But the samba fix
(correct path for that binary) is in jammy.
Then the question boils down to which update will cause the less amount
of disruption for users...
a)
That being said, it's also likely that all desktop users have some samba
library installed :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1979879
Title:
Apparmor
Initially I was also in favor of changing the apparmor profile instead
of the samba packaging, but after I saw Michał's MP (with this
approach), I'm kind of changing my mind, and here is my reasoning:
With the change to apparmor, all ubuntu users, regardless if they use
samba or not, will get the
** Merge proposal linked:
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/apparmor/+git/apparmor/+merge/427682
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
I am about to create a branch of it and send the MP.
I have simply used grep to check where /usr/lib*/samba/samba-bgqd occurs when I
did checkout to the ubuntu/jammy and I've seen that these files where it occurs
are in apparmor profile. I have changed apparmor profile to adapt it to the
actual
** Changed in: apparmor (Ubuntu)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
** Changed in: apparmor (Ubuntu Jammy)
Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)
--
You received this bug notification because you are a member of Ubuntu
27 matches
Mail list logo
