Mastouille

0 message0 participant0 message aujourd’hui

🚀 Несерьёзный Выдумщик 👨‍🔬Хорошая и <a href="https://habr.com/ru/articles/541190/" rel="nofollow noopener noreferrer" target="_blank">годная статья</a> про безопасность <a href="https://shitpost.poridge.club/tags/Android" rel="nofollow noopener noreferrer" target="_blank">#Android</a> устройств с разблокированным загрузчиком. Детально и подробно, с разных сторон разобран процесс загрузки Android-систем нескольких версий, включая <a href="https://shitpost.poridge.club/tags/LineageOS" rel="nofollow noopener noreferrer" target="_blank">#LineageOS</a> и виды сборок прошивок. Рассмотрен подход к работе <a href="https://shitpost.poridge.club/tags/Magisk" rel="nofollow noopener noreferrer" target="_blank">#Magisk</a> и варианты получения root'а разными средствами с учётом контекстов <a href="https://shitpost.poridge.club/tags/SELinux" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a>, а так же работа через <a href="https://shitpost.poridge.club/tags/adb" rel="nofollow noopener noreferrer" target="_blank">#adb</a> (в каких случаях имеет root'привелегии). Статья большая, но полезная с точки зрения «получить представление» без упрощений, а с техническими деталями. TL;DR Глупо выключать устройство, когда остаётся без присмотра, а описываемый сценарий не касается уже работающего (загруженного полностью, включённого) девайса. Если же устройство неожиданно оказалось выключенным, то нельзя включать и вводить пин\пароль. Сперва надо проверить содержимое разделов (на тот или иной вариант «нагрузки»). Т.е. включать через <code>fastboot</code>, прошивать заново рекавери (<a href="https://shitpost.poridge.club/tags/TWRP" rel="nofollow noopener noreferrer" target="_blank">#TWRP</a> или <a href="https://shitpost.poridge.club/tags/OrangeFox" rel="nofollow noopener noreferrer" target="_blank">#OrangeFox</a>) и прошерстить\восстановить разделы. Очень наглядно видно зачем в ОС нужны такие вещи как mandatory access control (MAC): • <a href="https://shitpost.poridge.club/tags/SELinux" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> (авторство АНБ США), • <a href="https://shitpost.poridge.club/tags/AppArmor" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> (via Novell & Immunix), • российский аналог в AstraLinux. На статью навёл <a href="https://social.openhood.ru/@sun_rise" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sun_rise@social.openhood.ru</a> <a href="https://shitpost.poridge.club/tags/AndroidSecurity" rel="nofollow noopener noreferrer" target="_blank">#AndroidSecurity</a> <a href="https://shitpost.poridge.club/tags/MAC" rel="nofollow noopener noreferrer" target="_blank">#MAC</a> <a href="https://shitpost.poridge.club/tags/security" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://shitpost.poridge.club/tags/privacy" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://mastodon.social/@russian_mastodon" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@russian_mastodon@mastodon.social</a> <a href="https://3zi.ru/@Russia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Russia@3zi.ru</a> <a href="https://social.sley.nl/@rur" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rur@social.sley.nl</a>

openSUSE LinuxFind out what happened in this <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oSC25</a> talk about the switch of <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> as the default MAC system in <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openSUSE</a> Tumbleweed, This talk will explore the shift from <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> and the lessons learned. A must-watch for those following system security! 🐧 <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openSUSE</a> <a href="https://youtu.be/8wBLbhSjDwE?si=1fOBIHkq1KkU5ynV" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/8wBLbhSjDwE?si=1fOBIHkq1KkU5ynV</a>

SolusHeya, folks! We have an update on <a href="https://floss.social/tags/Snap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Snap</a> and <a href="https://floss.social/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> support in <a href="https://floss.social/tags/Solus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solus</a>. We are holding off on our planned Snap support removal for now, as there has been recent progress in upstreaming the AppArmor patch set to the <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> kernel. We still recommend <a href="https://floss.social/tags/Flatpak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flatpak</a>, which has integration in GNOME Software and KDE Discover.Read more about it on our blog: <a href="https://getsol.us/2025/05/05/snapd-update/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://getsol.us/2025/05/05/snapd-update/</a>- Evan

Linux G. Fossman<a href="https://framapiaf.org/@debacle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@debacle</a> <a href="https://mastodon.social/@alatiera" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alatiera</a> That's great - I love <a href="https://social.vivaldi.net/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> : ) I do wish, however, that <a href="https://social.vivaldi.net/tags/sandboxing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sandboxing</a> native apps on Debian using <a href="https://social.vivaldi.net/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> was as <a href="https://social.vivaldi.net/tags/noobeasy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#noobeasy</a>* as using <a href="https://social.vivaldi.net/tags/flatpak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#flatpak</a> apps with <a href="https://social.vivaldi.net/tags/Flatseal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flatseal</a>. <a href="https://social.vivaldi.net/tags/noobeasy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#noobeasy</a> <a href="https://social.vivaldi.net/tags/noobsimple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#noobsimple</a> <a href="https://social.vivaldi.net/tags/newword" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#newword</a> <a href="https://social.vivaldi.net/tags/neword" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#neword</a> <a href="https://social.vivaldi.net/tags/did_i_just_invent_a_new_word" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#did_i_just_invent_a_new_word</a>?

varx/techI've seen <a href="https://infosec.exchange/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> used primarily to *harden* the security of an existing program. Is it also reasonable to use it to *sandbox* known-malicious code? Or are other methods required?(I assume you also want ulimit or similar on the side, but that's to prevent resource consumption attacks rather than sandbox escapes.)<a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://infosec.exchange/tags/sandboxing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sandboxing</a>

Linux Magazine<a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opensuse</a> Tumbleweed rolling release moves from AppArmor to SELinux for its underlying security layer <a href="https://www.linux-magazine.com/Online/News/openSUSE-Tumbleweed-Ditches-AppArmor-for-SELinux" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.linux-magazine.com/Online/News/openSUSE-Tumbleweed-Ditches-AppArmor-for-SELinux</a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openSUSE</a> <a href="https://fosstodon.org/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tumbleweed</a> <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/distro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distro</a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://fosstodon.org/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a>

LinuxNews.deNeues von openSUSE <a href="https://linuxnews.de/neues-von-opensuse/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxnews.de/neues-von-opensuse/</a> <a href="https://social.anoxinon.de/tags/opensuse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensuse</a> <a href="https://social.anoxinon.de/tags/sles" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sles</a> <a href="https://social.anoxinon.de/tags/tumbleweed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tumbleweed</a> <a href="https://social.anoxinon.de/tags/apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apparmor</a> <a href="https://social.anoxinon.de/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selinux</a> <a href="https://social.anoxinon.de/tags/uefi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uefi</a>

openSUSE LinuxStarting with snapshot 20250211, <a href="https://fosstodon.org/tags/SELinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> becomes the default <a href="https://fosstodon.org/tags/MAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MAC</a> system for new installs, boosting security! 🔒 <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> is still optional. The first <a href="https://fosstodon.org/tags/boot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#boot</a> might take a little time. <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openSUSE</a> <a href="https://fosstodon.org/tags/Tumbleweed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tumbleweed</a> <a href="https://news.opensuse.org/2025/02/13/tw-plans-to-adopt-selinux-as-default/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://news.opensuse.org/2025/02/13/tw-plans-to-adopt-selinux-as-default/</a>

Tom<a href="https://piou.foolbazar.eu/@joel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@joel</a> I've used <a href="https://mastodon.bsd.cafe/tags/apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apparmor</a> before but it is a real pain to get working. You have to set it in warn mode while you tweak the permissions and it's rounds of trial & error. Only after that you tell it to enforce and it has locked that process down properly. Some apps will undoubtedly be easier than others. I've had to do it on PHP web apps and it was a nightmare.

boredsquirrel<a href="https://floss.social/@kde" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kde@floss.social</a> <a href="https://lemmy.kde.social/c/kde" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kde@lemmy.kde.social</a> Thx for the info, then it is like that.Here is the goal proposal<a href="https://phabricator.kde.org/T17370" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://phabricator.kde.org/T17370</a>Tbh, <a href="https://tux.social/tags/bubblewrap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bubblewrap</a> would need to be fixed drastically to be as secure as the <a href="https://tux.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://tux.social/tags/sandbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sandbox</a>. And (I am not sure yet) I think even <a href="https://tux.social/tags/Snaps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Snaps</a> are more secure (on <a href="https://tux.social/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu</a> with <a href="https://tux.social/tags/Apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apparmor</a> patches) than <a href="https://tux.social/tags/Flatpak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flatpak</a> with the current system.As far as I understood, sandboxing needs to happen in <a href="https://tux.social/tags/userspace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#userspace</a>, with tools like <a href="https://tux.social/tags/fuse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fuse</a> doing the work while being restricted by <a href="https://tux.social/tags/MAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MAC</a> like <a href="https://tux.social/tags/SELinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> or Apparmor.

AscendorHere, <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> people: <a href="https://social.tchncs.de/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> or <a href="https://social.tchncs.de/tags/SELinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SELinux</a> - what would you prefer (and for what reasons)?

Zygmunt KrynickiI'm working on running <a href="https://fosstodon.org/tags/apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apparmor</a> end-to-end tests upstream, so that there are fewer regressions and better compatibility across different distributions and kernels.I've been posting about it at <a href="https://lists.ubuntu.com/archives/apparmor/2024-November/013407.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lists.ubuntu.com/archives/apparmor/2024-November/013407.html</a> and I've also opened an initial pull request at <a href="https://gitlab.com/apparmor/apparmor/-/merge_requests/1432" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/apparmor/apparmor/-/merge_requests/1432</a>I am very happy to have time to work on improving upstream state of the art for everyone using apparmor :-)

Programmer 832-529 🍅I've uploaded the <a href="https://social.dropbear.xyz/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://social.dropbear.xyz/tags/WordPress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WordPress</a> release 6.7 packages last night. I've re-jigged the auto update code so it doesn't complain; if you're using the package you're using Debian updates. Also the <a href="https://social.dropbear.xyz/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> profile will probably need tweaking as it looks like there is another directory.

GrimmauldI am currently working on <a href="https://mastodon.grimmauld.de/tags/apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apparmor</a> support for <a href="https://mastodon.grimmauld.de/tags/nixos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nixos</a> making profile definitions declared in the apparmor.d project available and functional.You can read up on my initial approach at <a href="https://hedgedoc.grimmauld.de/s/hWcvJEniW#" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hedgedoc.grimmauld.de/s/hWcvJEniW#</a>. I am not done yet! Pull Requests into nixpkgs will come after 24.11 branch-of. In the meantime, progress will be shared here on mastodon.

jbz🔓 The Insecurity of Debian ｢ In a SELinux environment, a compromised container faces substantial hurdles in accessing or affecting the host system or other containers, thanks to the dual barriers of type enforcement and MCS labels ｣<a href="https://unix.foo/posts/insecurity-of-debian/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://unix.foo/posts/insecurity-of-debian/</a><a href="https://indieweb.social/tags/debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#debian</a> <a href="https://indieweb.social/tags/redhat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redhat</a> <a href="https://indieweb.social/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selinux</a> <a href="https://indieweb.social/tags/apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apparmor</a>

fenixCome autorizzare l’esecuzione di un <a href="https://mastodon.uno/tags/AppImage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppImage</a> sul desktop in modo che <a href="https://mastodon.uno/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> non la blocchi.<a href="https://vitforlinux.wordpress.com/2024/07/18/come-autorizzare-lesecuzione-di-un-appimage-sul-desktop-in-modo-che-apparmor-non-la-blocchi/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://vitforlinux.wordpress.com/2024/07/18/come-autorizzare-lesecuzione-di-un-appimage-sul-desktop-in-modo-che-apparmor-non-la-blocchi/</a><a href="https://mastodon.uno/tags/UnoLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnoLinux</a> <a href="https://mastodon.uno/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

OMG! Ubuntu!Ubuntu Fast-Tracks AppArmor Fix for Flatpak Apps Failing to Start in UbuntuThe recent update to AppArmor to fix issues with 3rd-party apps unable to run on Ubuntu 24.04 LTS due to its security hardening inadvertently prevents a fleet of popular Flatpak apps from running. The Telegram Desktop, KeePassXC, and Steam clients are among Flatpak apps affected, some throwing an apparmor="DENIED" error apparently due to the AppArmor profile for the Bubblewrap sandboxing tool (used by many Linux apps) in the prior update. To be clear: snap, DEB, and binary versions of the software above aren’t affected, only Flatpaks. But good news: Ubuntu’s developers got to work to identify the cause, aided by :sys_more_orange: <a href="https://hello.2heng.xin/tags/News" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#News</a> <a href="https://hello.2heng.xin/tags/Apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apparmor</a> <a href="https://hello.2heng.xin/tags/Bugs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bugs</a> <a href="https://hello.2heng.xin/tags/FlatpakApps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FlatpakApps</a> <a href="https://hello.2heng.xin/tags/Ubuntu24_04Lts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu24_04Lts</a> :sys_omgubuntu: <a href="https://www.omgubuntu.co.uk/2024/07/ubuntu-apparmor-fix-for-telegram-flatpak" rel="nofollow noopener noreferrer" target="_blank">https://www.omgubuntu.co.uk/2024/07/ubuntu-apparmor-fix-for-telegram-flatpak</a>

Thorsten Leemhuis (acct. 1/4)TIL: <a href="https://fosstodon.org/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu</a> apparently carries a "huge" <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> patchset in their <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel</a>:"'To start with, the patchset is huge; it is upwards of 60 separate patches, making it a significant maintenance burden. Since the set is maintained and updated by <a href="https://fosstodon.org/tags/Canonical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canonical</a>, we can only update to a new kernel after they’ve updated all of those patches, which sometimes takes a long time, or even doesn’t happen at all, as with the 6.9 kernel series.'"<a href="https://getsol.us/2024/07/15/dropping-apparmor-kernel-patches/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://getsol.us/2024/07/15/dropping-apparmor-kernel-patches/</a> <a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LinuxKernel</a>

Solus :solus:Heya folks! We just made a new blog post about kernel AppArmor patches and Snap support. Check it out on our website: <a href="https://getsol.us/2024/07/15/dropping-apparmor-kernel-patches/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://getsol.us/2024/07/15/dropping-apparmor-kernel-patches/</a><a href="https://fosstodon.org/tags/Solus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Solus</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/AppArmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AppArmor</a> <a href="https://fosstodon.org/tags/Snap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Snap</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>- Evan

OMG! Ubuntu!AppArmor Update Coming to Fix Broken Apps in Ubuntu 24.04If you’ve been experiencing issues getting some apps to run or work properly in Ubuntu 24.04 LTS it may be down to the distro using AppArmor to restrict the creation of user namespaces. This change (which I touched on in my article look at what’s new in Ubuntu 24.04 LTS) is there to bolster security. After all, no-one wants icky apps free to do icky things, unchecked. But the change means AppArmor policies are (somewhat expectedly) preventing some apps from running at all, and breaking features in other apps if they rely on components AppArmor isn’t configured to allow. When :sys_more_orange: <a href="https://hello.2heng.xin/tags/News" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#News</a> <a href="https://hello.2heng.xin/tags/Apparmor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apparmor</a> <a href="https://hello.2heng.xin/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://hello.2heng.xin/tags/Ubuntu24_04Lts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu24_04Lts</a> :sys_omgubuntu: <a href="https://www.omgubuntu.co.uk/2024/06/apparmor-update-fix-coming-ubuntu" rel="nofollow noopener noreferrer" target="_blank">https://www.omgubuntu.co.uk/2024/06/apparmor-update-fix-coming-ubuntu</a>

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#apparmor