public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Keith Whitwell <keith@tungstengraphics.com>
To: Keith Packard <keithp@keithp.com>
Cc: "roland@webde" <devzero@web.de>,
cygwin-xfree@cygwin.com, xserver@pdx.freedesktop.org,
dri-devel <dri-devel@lists.sourceforge.net>
Subject: security, cvs, was Re: interface bindings of x-server
Date: Wed, 19 Nov 2003 08:15:00 -0000 [thread overview]
Message-ID: <3FBB269A.9080306@tungstengraphics.com> (raw)
In-Reply-To: <E1AMJiO-0000K0-00@evo.keithp.com>
Keith Packard wrote:
> Around 2 o'clock on Nov 19, "roland@webde" wrote:
>
>
>>Keith, could you put this (being able to specify the interface bindings of
>>the xserver on the commandline) as a feature request on http://
>>www.freedesktop.org/Software/XserverWishlist if you find this feature
>>request useful ? i registerd a wiki account, but logging in doesn`t seem to
>>work for me.
>
>
> I'd like to switch the server so that -nolisten tcp is the default; I
> don't see much sense in having it listen to even 127.0.0.1. But, if you
> wanted to make the list of IP addresses that the server bound to
> configurable, that seems like a good idea.
Yep - network transparency is all well & good, but do you really want
something as complex as the X server sitting there with an open port to the world?
On a related issue, does anyone understand what the actual flaw in pserver CVS
is that allowed the linux backdoor attempt? There's been a lot of talk about
the implications of the attempt, but I haven't heard anyone come out and say
"This is the fault in CVS, here's a patch, everything's ok now".
Is it foolhardy to continue running anoncvs, especially without the checks &
balances which caught the backdoor attempt in linux?
Keith
next prev parent reply other threads:[~2003-11-19 8:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <038f01c3ae12$35ca4a80$2000000a@schlepptopp>
[not found] ` <3FBA82CC.6050500@msu.edu>
2003-11-19 1:53 ` roland@webde
2003-11-19 4:13 ` Keith Packard
2003-11-19 8:15 ` Keith Whitwell [this message]
2003-11-19 8:35 ` [Dri-devel] security, cvs, was " Mike Mestnik
2003-11-19 8:49 ` Keith Packard
2003-11-19 9:22 ` roland@webde
2003-11-19 9:35 ` Keith Packard
2003-11-19 9:52 ` Corinna Vinschen
2003-11-19 19:34 ` Alan Coopersmith
2003-11-19 21:12 ` roland@webde
2003-11-19 23:49 ` Dave Dodge
2003-11-20 0:13 ` Alan Coopersmith
2003-11-20 0:13 ` Keith Packard
2003-11-20 0:32 ` Dave Dodge
2003-11-19 14:01 devzero
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=3FBB269A.9080306@tungstengraphics.com \
--to=keith@tungstengraphics.com \
--cc=cygwin-xfree@cygwin.com \
--cc=devzero@web.de \
--cc=dri-devel@lists.sourceforge.net \
--cc=keithp@keithp.com \
--cc=xserver@pdx.freedesktop.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 read-only IMAP folder(s) and NNTP newsgroup(s).