From: Florian Weimer <fw@deneb.enyo.de>
To: russell@coker.com.au
Cc: Bill Laut <wlsel@verizon.net>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: X-Windows and Client-side Buffer Overruns
Date: Fri, 08 Aug 2003 22:05:52 +0200 [thread overview]
Message-ID: <87adaj3of3.fsf@deneb.enyo.de> (raw)
In-Reply-To: <200308010941.55431.russell@coker.com.au> (Russell Coker's message of "Fri, 1 Aug 2003 09:41:55 +1000")
Russell Coker <russell@coker.com.au> writes:
> I think that you misunderstood my message. I was referring to the
> fact that it is impossible to restrict an application which has X
> access from snooping the windows of other X programs or reading the
> keyboard buffer.
There are some X Security Extensions which restrict access to the root
window, windows of other client connections, and potentially dangerous
interfaces. But I have never seen them in action, and these
restrictions are just an afterthought (added around 1996).
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-08-08 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 19:41 Updated Release Howard Holm
2003-07-11 23:31 ` Christopher J. PeBenito
2003-07-14 11:59 ` Stephen Smalley
2003-07-30 22:03 ` X-Windows and Client-side Buffer Overruns (was Re: Updated Release) Bill Laut
2003-07-31 2:45 ` Tom
2003-07-31 15:26 ` Russell Coker
2003-07-31 15:38 ` Tom
2003-07-31 16:26 ` Bill Laut
2003-07-31 23:41 ` Russell Coker
2003-08-01 17:20 ` Bill Laut
2003-08-08 20:12 ` X-Windows and Client-side Buffer Overruns Florian Weimer
2003-08-08 20:05 ` Florian Weimer [this message]
2003-07-31 2:56 ` Updated Release Bill Laut
2003-07-31 12:20 ` Stephen Smalley
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=87adaj3of3.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=SELinux@tycho.nsa.gov \
--cc=russell@coker.com.au \
--cc=wlsel@verizon.net \
/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.