From owner-freebsd-ports@FreeBSD.ORG Tue May 22 19:25:55 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECADF16A421 for ; Tue, 22 May 2007 19:25:55 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id DD94C13C45A for ; Tue, 22 May 2007 19:25:55 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 70F141A3C19; Tue, 22 May 2007 12:26:55 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BEE9752683; Tue, 22 May 2007 15:25:54 -0400 (EDT) Date: Tue, 22 May 2007 15:25:54 -0400 From: Kris Kennaway To: Benjamin Lutz Message-ID: <20070522192553.GA99518@xor.obsecurity.org> References: <200705222120.42407.mail@maxlor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200705222120.42407.mail@maxlor.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-ports@freebsd.org Subject: Re: ssh X11 forwarding and X.org 7.2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 19:25:56 -0000 On Tue, May 22, 2007 at 09:20:38PM +0200, Benjamin Lutz wrote: > Hello, > > Since X.org is no longer located in /usr/X11R6, ssh X11 forwarding is > broken since ssh no longer finds xauth. Only if you didn't follow the directions (hint: /usr/X11R6 should be a symlink ;-) > This can be fixed by manually > setting XAuthLocation in sshd_config. But could some committer also > change the paths in /usr/src/crypto/openssh accordingly so the new > location becomes the default? Thanks! This and other things should be fixed over time, but there are thousands of them in ports (including some binary applications that would require a new build from the vendors) so it will be a multi-year effort at best, and in practise probably something we'll have to carry around forever. Kris