Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upQubes /usr/local symlink /rw/usrlocal AppArmor issue #1122
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nrgaway
Aug 17, 2015
I assume you have tested this already. Just wanted to make sure that an alias will not effect the mounting of /rw/usrlocal to /usr/local?
nrgaway
commented
Aug 17, 2015
|
I assume you have tested this already. Just wanted to make sure that an alias will not effect the mounting of |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Aug 17, 2015
Member
Yes, this is tested and working.
Doesn't affect that. Affecting mount should be far outside of AppArmors's scope. (There is no AppArmor profile for mount, if that even would make sense.)
|
Yes, this is tested and working. Doesn't affect that. Affecting |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 26, 2015
Member
I don't know AppArmor at all, but above (together with an idea about
qubes-core-agent) looks good.
BTW some applications had a problem with /home->/rw/home symlink, AFAIR
because realpath $HOME != $HOME. Because of that /home is now
bind-mounted from /rw/home. Do you think we should do the same with
/usr/local? This is the first issue ever caused by that /usr/local
symlink, so maybe not.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
I don't know AppArmor at all, but above (together with an idea about BTW some applications had a problem with /home->/rw/home symlink, AFAIR Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Aug 26, 2015
Member
Do you think we should do the same with
/usr/local?
Yes. For better consistency.
I am not sure I yet have experienced /rw/home related AppArmor symlink issues, but all symlinks should have corresponding alias' configured. I'll include alias /home -> /rw/home/, in my pull request.
Are there any other (bind-) mounted locations or a list of those which probably also should be included?
Yes. For better consistency. I am not sure I yet have experienced /rw/home related AppArmor symlink issues, but all symlinks should have corresponding alias' configured. I'll include Are there any other (bind-) mounted locations or a list of those which probably also should be included? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Aug 26, 2015
Member
On Wed, Aug 26, 2015 at 09:10:39AM -0700, Patrick Schleizer wrote:
Do you think we should do the same with
/usr/local?Yes. For better consistency.
Ok. But since mounting /rw get more and more complex, I think we should
do this only after #979.
I am not sure I yet have experienced /rw/home related AppArmor symlink issues, but all symlinks should have corresponding alias' configured. I'll include
alias /home -> /rw/home/,in my pull request.
I think this is unnecessary, as /home is bind-mounted now.
Are there any other (bind-) mounted locations or a list of those which probably also should be included?
Actually I think bind mounted locations shouldn't be a problem for
AppArmor. Symlinks are.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
On Wed, Aug 26, 2015 at 09:10:39AM -0700, Patrick Schleizer wrote:
Ok. But since mounting /rw get more and more complex, I think we should
I think this is unnecessary, as /home is bind-mounted now.
Actually I think bind mounted locations shouldn't be a problem for Best Regards, |
marmarek
referenced this issue
Aug 26, 2015
Closed
Bind mount /rw/usrlocal -> /usr/local instead of symlink #1150
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Aug 26, 2015
Member
Since,
- my originally proposed (#1122 (comment)) solution using /etc/apparmor.d/tunables/home.d/qubes is only a workaround
- and #1150 is the appropriate fix that you triaged for 3.1 [feels not so far],
what do you think about not implementing / closing this ticket?
|
Since,
what do you think about not implementing / closing this ticket? |
marmarek
added this to the Release 3.1 milestone
Sep 2, 2015
marmarek
added
C: core
C: templates
labels
Sep 2, 2015
marmarek
removed this from the Release 3.1 milestone
Sep 2, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Good idea, one ticket less :) |
adrelanos commentedAug 15, 2015
issue description:
I found a Qubes specific AppArmor issue.
Qubes symlinks
/usr/localto/rw/usrlocaland AppArmor does not like this.Upstream AppArmor won't add symlink support:
https://bugs.launchpad.net/apparmor/+bug/1485055
proposed solution:
I am suggesting to ship a file
/etc/apparmor.d/tunables/home.d/qubeswith the following content:Also some explanatory comment should be added. And perhaps this will needs to be extended over time with more entries. There is also a file
/etc/apparmor.d/tunables/home.d/ubuntualready, so this seems appropriate. In which package? qubes-core-agent, I suppose?If this solution sounds alright to you, I can send a pull request.