[cups-devel] [UNKN] STR #4618: Using host name in /etc/cups/cupsd.conf Listen directive could make cupsd listen on the wrong IP

Michael Sweet noreply at cups.org
Tue Apr 14 20:13:30 PDT 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Unresolved]

> Yup—hence my suggestion to depend on “network”, which may not solve
all the problems but some—for sure. Can it cause any new problems?

Yes, because we can't bind to an interface. Network addresses change...

As for changing the documentation for Listen, quite frankly this has never
been an issue. For most users the only value they ever use is "Listen
localhost:631", which binds cupsd to the loopback interface (and in fact we
have hardcoded lookups for "localhost" to bypass common DNS issues). When
sharing is enabled we switch to "Port 631".

Using "Listen hostname" with a dynamically assigned address is just not
done...

Link: https://www.cups.org/str.php?L4618
Version: -feature
Fix Version: None
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVLddaAAoJENujp6sI12IjG8kP/RdQgcg8U26PvJwH9LGrvyHM
qYQyjzl8g1pR5YcK//zu+CbGs80jkIEK5qknqcR3YxLpPIXF1DgArb8IfQZRdwpM
T8VMh0xwqCpyU0w2wp+gENKLg0CGMDWfe09bxrytVvMM16gvYRCh/afQox7PKzD2
0rNUSNox6ieSdpwHsuZkRBluu8RvDs6LVhLvJJx9cPr3xPfrkkozdpvREqW2oN6n
4uRE+9uaSu3dufo+tiDot8t7CfG3hsxW7JiqcXPk2tA0GZytYyR68wa2BUI9Xzc0
PU5aKer+qbjNswqhfEPp1HMrmrxWaFwnIH4qgKGtwQM+T05XrA7TI9eirGzSV/mt
RxxqVRBO9WfgIb7B069N4QiC81eN4LoVrlquXYHUHFsOKUzoosI1S6NlmCMgWwid
JVg22X0JlRq9wGO518OAFDFPwlc3507iDD7zZhBWwACYOU3AdgszrLD1s/SW5LTL
UrxLBFxkFC4dzDnx6i/DqmxbmSBppJBblDVbRaqinh4iJ9O/Nu8OJ+ukuSX7uDkl
T1fAeCVH/Q/YZGvdQiDYex/tWoFHENO+X38vSLFYtOrspkv/rQGx5nUhT3cChpIA
3mE8sPbIGBYcZWDNBaHN3MXeAAVRv2lZ97kr+kr2gEaYuugW35Ll6fgg0Wur78Il
iDo6L8g3VFkF6cKhgVFU
=ApEV
-----END PGP SIGNATURE-----




More information about the cups mailing list