From: Russell Coker <russell@coker.com.au>
To: Dominick Grift <dominick.grift@defensec.nl>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: sddm issue and patch not for inclusion
Date: Fri, 29 Jan 2021 01:12:26 +1100 [thread overview]
Message-ID: <10144859.lm3J6uu7uN@liv> (raw)
In-Reply-To: <ypjlmtwti26f.fsf@defensec.nl>
On Friday, 29 January 2021 1:08:56 AM AEDT Dominick Grift wrote:
> > That's a design decision. One could make a convincing argument that it's
> > a
> > good decision.
>
> Not sure whether doing text-relocation on a file you created yourself is
> a good decision. From a security perspective does not seem like very
> good thing to along, The more because xdm is shared between various
> desktop managers.
Oh yes, execmod is bad. I thought your comment was about the use of PAM.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2021-01-28 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:26 sddm issue and patch not for inclusion Russell Coker
2021-01-28 11:33 ` Dominick Grift
2021-01-28 11:36 ` Dominick Grift
2021-01-28 14:00 ` Russell Coker
2021-01-28 14:08 ` Dominick Grift
2021-01-28 14:12 ` Russell Coker [this message]
2021-01-28 14:32 ` Dominick Grift
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=10144859.lm3J6uu7uN@liv \
--to=russell@coker.com.au \
--cc=dominick.grift@defensec.nl \
--cc=selinux-refpolicy@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.