From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Waydroid shipped broken
Date: Tue, 17 Jan 2023 03:20:19 +0100 [thread overview]
Message-ID: <20230117022019.JC_2fVfBEBfaMjRaNV9kMtzvASyASjVwS7pN0WhRKM8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41363@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/41363#issuecomment-1384728603
Comment:
I was actually referring to this, which it seems could still be an issue:
https://docs.waydro.id/debugging/known-issues#one-cause-for-this-issues-is-apparmor-the-fix-is-as-follows
If the maintainer of waydroid (you, @JamiKettunen?) can test with AppArmor that would be ideal, otherwise we should not install the Waydroid profiles ... I am not sure that they tested it! Maybe in a separate package for the atypical use case. Most people should understand that Waydroid provides a relatively medium-soft security boundary... still on the same kernel and hypervisor.
Edit: Made an MR for the apparmor profile change https://gitlab.com/apparmor/apparmor/-/merge_requests/969
next prev parent reply other threads:[~2023-01-17 2:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 16:27 [ISSUE] " notramo
2022-12-30 16:43 ` paper42
2022-12-31 19:08 ` JamiKettunen
2023-01-03 21:33 ` notramo
2023-01-03 21:41 ` notramo
2023-01-03 21:55 ` notramo
2023-01-03 21:57 ` notramo
2023-01-03 21:58 ` notramo
2023-01-04 0:43 ` JamiKettunen
2023-01-04 0:47 ` JamiKettunen
2023-01-04 1:15 ` notramo
2023-01-04 1:18 ` notramo
2023-01-04 2:12 ` JamiKettunen
2023-01-16 21:36 ` CameronNemo
2023-01-16 22:07 ` JamiKettunen
2023-01-17 1:33 ` CameronNemo
2023-01-17 2:20 ` CameronNemo [this message]
2023-04-09 4:03 ` HadetTheUndying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230117022019.JC_2fVfBEBfaMjRaNV9kMtzvASyASjVwS7pN0WhRKM8@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).