On Sat, Jan 13, at 05:39 Joe Ciccone wrote: > > > > Sshd in order to set up the authentication correctly,uses xauth, > > but is looking for the xauth binary in (/usr/X11R6/bin),which obviously > > is a problem for those who install X in /usr (the majority I guess). > > > > As a result I was receiving errors,such "Can't open display" or > > slowdowns. > > > > I found 3 solutions. > > a. The configure switch "--with-xauth=/usr/bin/xauth" > > b. The following sed, > > sed -i '/_PATH_XAUTH/[EMAIL PROTECTED]/@@' pathnames.h > > c. Specify the location of the xauth binary in sshd_config,eg... > > XAuthLocation /usr/bin/xauth > > > > Can you verify it? > > > I can verify that none of the above is needed. Looking at the > configure.in from openssh-4.5p1 i see. ><SNIP> > This will search your PATH before X11R6 anyway. If you just simply put > xorg_prefix/bin in your path it will work. >
Many Thanks Joe,that was enlightening. Obviously,as Dan said in his answer,the problem it doesn't appear if you build openssh after xauth but before; So it's not a problem of an wrong autodetection as you have prove it. And there are few cases that someone wants to do that. Choosing one of the 2 first aforementioned ways,again as Dan answered,the xauth path still gets into the binary whether you have X installed yet or not. Otherwise the thisd option is the only way to abort errors like these [1] in the foresight-linux bug,if someone doesn't want to rebuild it. Maybe there has to be a simple note in the openssh instructions about this possibility. 1.https://issues.foresightlinux.org/browse/FL-31 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
