From: Joshua Brindle <brindle@quarksecurity.com>
To: John Chludzinski <john.chludzinski@vivaldi.net>
Cc: Selinux <selinux@tycho.nsa.gov>
Subject: Re: XWindows and CLIP?
Date: Thu, 02 Jun 2016 17:51:35 -0400 [thread overview]
Message-ID: <5750AA67.9030806@quarksecurity.com> (raw)
In-Reply-To: <1223101c554790d34307b1736bbca1fa@mail.vivaldi.net>
John Chludzinski wrote:
> What are the issues with XWindows and CLIP? Why is CLIP XWindow-less?
CLIP strives to be a minimal system suited to secure solutions and does
not come with software not necessary for such systems (e.g., cross
domain solutions).
> Is there something inherently unsecure with the XWindow client/server
> model?
Xorg manages interactions between programs running under X itself and is
therefore an object manager (similar to how an RDBMS is an object
manager that manages rows and tables).
There is work to extend SELinux controls to Xorg (XACE) but without
using XACE and X SELinux policy you cannot meaningfully manage
information flow between X applications uses SELinux.
prev parent reply other threads:[~2016-06-02 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 21:29 XWindows and CLIP? John Chludzinski
2016-06-02 21:51 ` Joshua Brindle [this message]
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=5750AA67.9030806@quarksecurity.com \
--to=brindle@quarksecurity.com \
--cc=john.chludzinski@vivaldi.net \
--cc=selinux@tycho.nsa.gov \
/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.