Bug 2759 - xfs font server doesn't serve fonts via TCP
Summary: xfs font server doesn't serve fonts via TCP
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: XFree86
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
: 3174 3315 3501 10212 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 1999-05-12 12:22 UTC by Krzysztof Halasa
Modified: 2008-05-01 15:37 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-06-26 19:31:39 UTC

Attachments (Terms of Use)

Description Krzysztof Halasa 1999-05-12 12:22:44 UTC
X11 font server from XFree86 in RedHat 6.0 doesn't work with
TCP. It's been intentionally (temporarily?) disabled with a
patch file, but I believe some better solution should be
implemented, which enables users to have a remote font

Comment 1 parse 1999-05-12 14:50:59 UTC
This is a _high_ priority for me!  I wonder why it was intentionally
disabled?  I do a lot of work turning 486's into X terminals... I'd
like to see this fixed.  For now, I'm using an older xfs binary from
Mandrake 5.3.

Comment 2 David Lawrence 1999-05-13 21:24:59 UTC
This has been assigned to a developer for further review.

Comment 3 Chris Evans 1999-05-14 13:46:59 UTC
It was intentionally disabled because of _extreme_ security risk. What
specifically breaks for you?

The default should certainly remain XFS only listening locally.

Comment 4 ard 1999-05-15 22:39:59 UTC
What specifically breaks:
Running an i486 headless, and having an X-terminal with only 23 fonts.
A "lot of programs" break because they cannot find their desired
fonts... (bad programming :( ). Gnome does a good job of not using
available fonts.

Comment 5 pavel_roskin 1999-05-25 15:40:59 UTC
Even "xfs -port 7100" doesn't work as expected, and there are no error
messages about tcp disabled.
I can accept disabling tcp by default, but how do I turn it on?

Comment 6 parse 1999-05-25 18:38:59 UTC
I spoke with Mike Fulbright at Linux Expo, and promised I'd send a
patch, which I have.  I also forwarded a copy to dkl.  The
original patch was really trivial, and so is mine; except that with
mine, supplying '-port 7100' will make it work.

Comment 7 Krzysztof Halasa 1999-05-25 22:57:59 UTC
I think using port directive in xfs config file should also make it
work with TCP. Just changing the default 7100 port to -1 should do the
job - xfs wouldn't normally listen for TCP connections, but specifying
-port xxx in command line or port xxx in .../xfs/config would enable
We should patch the man page too.

Comment 8 Chris Evans 1999-05-29 12:37:59 UTC
As long as default remains XFS _doesn't_ listen on TCP - it has
security issues. I will get round to fixing them sometime :-))

Comment 9 Jeff Johnson 1999-06-03 14:47:59 UTC
*** Bug 3174 has been marked as a duplicate of this bug. ***

RH 5.2 xfs listens on UNIX port 7100 AND tcp port 7100 by
default. It also accepts the -port argument to change this.

RH 6 doc says the xfs in RH 6 will listen on tcp 7100 by

It does not. It ONLY listens on UNIX port -1 !!!!

(information confirmed by netstat -at and netstat -ax, the
former revealing nothing relating to xfs even when xfs is
plainly running, the latter revealing a UNIX protocol port
at: /tmp/.font-unix/fs-1)

Neither does it accept the -port argument (well, it accepts
it, but it ignores it)

Instructions on page 4 Installation guide suggest putting
"Fontpath "tcp/localhost:7100" in XF86Config. This does not
work (for the above reasons). Only

	"Fontpath "unix/:-1"


------- Additional Comments From dkl  06/01/99 18:26 -------

*** Bug 2514 has been marked as a duplicate of this bug. ***

In section (Enhanced font support) of the
installation guide (I am looking at the electronic version
from the rhl-install-guide-en-6.0-2 rpm) you give
instructions for using the new font server instead of a
conventional fontpath.
Those direction say to use "tcp/localhost:7100" in the
fontpath.  However, the version of xfs in
XFree86-xfs- has intentionally had TCP
functionality removed (XFree86-
modification of file
XFree86-  The
correct instruction would be to use "unix/:-1" in the

Comment 10 Jeff Johnson 1999-06-07 22:32:59 UTC
*** Bug 3315 has been marked as a duplicate of this bug. ***

The version in xfs in XFree86- does not appear to
listen for incoming connections.
Copying xfs from a similar system running
XFree86-  and running it allows telnet connections
to be made to port 7100 and a LISTEN entry shows up in
netstat -a

However, if  xfs from -49 is used then although an strace
reveals it to be waiting at a select, netstat -a makes no
mention of a service listening on 7100 and telnet
7100 yields connnection refused. The configuration file used
is the same in both cases.

Comment 11 Preston Brown 1999-06-11 18:22:59 UTC
*** Bug 2779 has been marked as a duplicate of this bug. ***

I always install everything.  The only things I remove
after is all of the foriegn language doc.  I have two
issues with X11.
One:  The Xconfigurator shows me a 32bbp 1620 x 1024  i do
not want this but the options I get to choose from are 8 16
and 24.  I would love to say 32bbp but only 1024 x 768.
I can not figure out to fix this manually.
Two:  After the install I noticed that terminal windows
woud look very bad with crazy snow apperaing all over the
windows when I would execute commands in the windows.  I
could clearit by minimizing the window and then opening
again.  I realized what the issue was when Xwindows quits.
I get a message saying it can not load the right font?
Let me know if I can give you more information.

------- Additional Comments From notting  05/13/99 10:17 -------
try running 'chkfontpath --add /usr/X11R6/lib/X11/fonts/75dpi' and
then '/etc/rc.d/init.d/xfs restart'.

Comment 12 Jeff Johnson 1999-06-16 18:09:59 UTC
*** Bug 3501 has been marked as a duplicate of this bug. ***

the xfs man page says that xfs opens TCP port 7100
by default.  however, commands which attempt to use
that port (xset, fsinfo, fslsinfo) fail indicating
that xfs isn't listening.  "lsof -p <xfs process>"

# lsof -p 2120
xfs     2120  xfs  cwd    DIR        3,5    1024     2 /
xfs     2120  xfs  rtd    DIR        3,5    1024     2 /
xfs     2120  xfs  txt    REG        3,5  391872 49207
xfs     2120  xfs  mem    REG        3,5  342206 28736
xfs     2120  xfs  mem    REG        3,5  538944 28748
xfs     2120  xfs  mem    REG        3,5 4016683 28741
xfs     2120  xfs  mem    REG        3,5  251436 28772
xfs     2120  xfs  mem    REG        3,5  364235 28749
xfs     2120  xfs  mem    REG        3,5  243964 28766
xfs     2120  xfs    0u   CHR        1,3          2051
xfs     2120  xfs    1u   CHR        1,3          2051
xfs     2120  xfs    2u   CHR        1,3          2051
xfs     2120  xfs    3r  FIFO        0,0         33619 pipe
xfs     2120  xfs    4r  FIFO        0,0         33621 pipe
xfs     2120  xfs    5u   CHR      136,0             2
xfs     2120  xfs    6r  FIFO        0,0         33804 pipe
xfs     2120  xfs    7u  sock        0,0         33814 can't
identify protocol
xfs     2120  xfs    8u  unix 0xccdbe8c0         33815
xfs     2120  xfs   10r  FIFO        0,0         33798 pipe
xfs     2120  xfs   12u   CHR      136,0             2
xfs     2120  xfs   21w  FIFO        0,0         33798 pipe

which suggests that it has created a socket but not
bound a protocol (like TCP) nor a protocol endpoint
(like 7100) to it?

Comment 13 Bill Nottingham 1999-06-17 14:55:59 UTC
Fixed in errata XFree86-*-52 release. The default is still
not to serve via TCP, but you can now enable it if you want
to take the security risk/need this functionality...

Comment 14 rossigee 1999-10-19 18:27:59 UTC
IMO, this has still not been fixed, even using a recent RawHide RPM
(XFree86-xfs-3.3.5-1.6.0). I would expect the default
/etc/X11/fs/config file to contain a 'port 0' (or similar) to disable
the TCP socket bind. To re-enable the port, I would expect to just
uncomment that line (leaving xfs to assume port 7100 as default).

Instead, I find that the /etc/rc.d/init.d/xfs script contains a
softcoded switch to disable the TCP socket bind :

	echo -n "Starting X Font Server: "
	rm -fr /tmp/.font-unix
	daemon xfs -droppriv -daemon -port -1

Now I need to re-edit the script each time I upgrade the package. Am I
missing something?

Ross Golder <rossigee>

Comment 15 Preston Brown 2000-06-26 19:31:00 UTC
*** Bug 10212 has been marked as a duplicate of this bug. ***

Comment 16 Preston Brown 2000-07-13 18:53:38 UTC
XFree86 4.0.1 and later will not specify a -port option in the xfs init script,
so the default port will be used.  A new config file option "no-listen" has been
added, and the default is "no-listen tcp", so we will remain secure.

Upgraded systems are encouraged to include this option in their xfs config

Note You need to log in before you can comment on or make changes to this bug.