=== chris14_ is now known as chris14 | ||
=== JanC is now known as Guest8007 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest7254 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest2780 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest191 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest803 | ||
=== JanC_ is now known as JanC | ||
=== cpaelzer_ is now known as cpaelzer | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest1127 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest7146 | ||
=== JanC is now known as Guest5659 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest6929 | ||
=== JanC_ is now known as JanC | ||
=== JanC is now known as Guest3813 | ||
=== JanC_ is now known as JanC | ||
=== JanC_ is now known as JanC | ||
ahasenack | I noticed some apparmor profiles that have include directies, no longer prefix them with # | 18:02 |
---|---|---|
ahasenack | i.e., | 18:02 |
ahasenack | #include <abstractions/base> | 18:02 |
ahasenack | became | 18:02 |
ahasenack | include <abstractions/base> | 18:02 |
ahasenack | can I just "do" that, or do I need to declare "abi <ani/3.0>," before? I've seen that abi declaration too | 18:02 |
ahasenack | or are these unrelated | 18:03 |
ahasenack | this is for lunar+ | 18:03 |
sdeziel | ahasenack: according to https://gitlab.com/apparmor/apparmor/-/merge_requests/553, the non "#" version has been supported since around apparmor 2.3 | 18:11 |
-ubottu:#ubuntu-security- Merge 553 in apparmor/apparmor "abstractions: remove '#' from 'include if exists'" [Merged] | 18:11 | |
sdeziel | so that goes back to before 14.04 :) | 18:11 |
ahasenack | thanks for checking :) | 18:13 |
georgiag | ahasenack: we also want to deprecate the use of # for include https://gitlab.com/apparmor/apparmor/-/merge_requests/903 | 18:13 |
-ubottu:#ubuntu-security- Merge 903 in apparmor/apparmor "parser: begin deprecation process for #include" [Merged] | 18:13 | |
ahasenack | I suppose both forms can coexist | 18:13 |
ahasenack | georgiag: yeah, I never understood why that was the case, #include actually doing something, but #comment not :) | 18:13 |
sdeziel | oh, good to know it's been deprecated, I guess I'll have to run a bunch of sed ;) | 18:17 |
ahasenack | we should also, in ubuntu | 18:28 |
ItzSwirlz | hey sec team, i see you guys are hard at work today! If you have time can you guys take a poke at LP #1998060 | 19:31 |
-ubottu:#ubuntu-security- Launchpad bug 1998060 in nemo (Ubuntu Kinetic) "CVE-2022-37290: Pasted zip archive/invalid file causes NPD" [Undecided, In Progress] https://launchpad.net/bugs/1998060 | 19:31 | |
tsimonq2 | Is anyone actively working on the vim 2023 CVEs or would it be helpful for me to prep stable releases when I do the Lunar upload? | 20:24 |
sarnold | hey tsimonq2 :) I don't think anyone is working on any vim packages at the moment, I don't think that work would collide | 20:37 |
tsimonq2 | Hey sarnold :) sounds good! | 21:09 |
sarnold | thanks tsimonq2 :) | 21:10 |
tsimonq2 | Happy to help :D | 21:18 |
laiello | I'm trying to get IMA and EVM working in an Ubuntu sandbox environment (22.04) but after installing `ima-evm-utils`, the `ima_policy` executable and the `/etc/ima/ima-policy` file that should have been installed aren't present. Is it possible I'm looking at outdated reference documentation on what the correct package name(s) are? | 23:00 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!