Hi, I'd like to know if there is any chance to get bug 1153 fixed soon ? It seems like a trivial issue, a patch is provided, and it's a pain for us to manually patch every new release -- this was reported as a portable-specific bug, but also affects vanilla openssh. The bug is described at http://bugzilla.mindrot.org/show_bug.cgi?id=1153 Simon -- Simon Vallet Ing?nieur Syst?mes/R?seaux G?noscope / CNRG T?l. : 01 60 87 36 06 E-mail : svallet at genoscope.cns.fr
On Mon, Feb 20, 2006 at 03:49:23PM +0100, Simon Vallet wrote:> I'd like to know if there is any chance to get bug 1153 fixed > soon ? It seems like a trivial issue, a patch is provided, and it's a > pain for us to manually patch every new release -- this was reported > as a portable-specific bug, but also affects vanilla openssh.Well, you haven't explained why it's a bug and should be changed. Under what circumstances is a $DISPLAY of the hostname not the "wanted value"? -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Tue, 21 Feb 2006 10:10:21 -0500 Carson Gaspar <carson at taltos.org> wrote:> > --On Tuesday, February 21, 2006 11:03 AM +0100 Simon Vallet > <svallet at genoscope.cns.fr> wrote: > > > OK -- we have globally the following setup here : an external ssh > > gateway performing X11 forwarding to the internal network -- as this > > machine is multihomed, a call to gethostname() returns (correctly IMO) > > the short name of the gateway, which is the value used to set DISPLAY > > and to add xauth credentials. > > No. gethostname() needs to return the (or a) FQDN of the server. Anything > else is just broken and begging for trouble. This is sysadmin 101.This is not in any way included in any standard, and I personally think that it was a reasonable choice. However, even if this is a debatable topic, it totally misses the point : even when gethostname() returns an FQDN, there is no way to tell in advance if the returned value will fit wanted ("working") usage. And actually, arbitrarily (from an OpenSSH POV) choosing an interface/hostname to use in DISPLAY regardless of the interface the SSH traffic is coming from seems just as "broken" and "begging for trouble". Simon
Apparently Analagous Threads
- [tftp-hpa] [BUG] Bad src address on replies from aliased interfaces
- [PATCH] Add support for ldns
- "Out of memory" error looking up SSHFP records
- [Bug 1153] DISPLAY should be set form the connected IP, not the hostname
- [Bug 1285] provide fallback options /etc/ssh/ssh_config