From owner-freebsd-x11@freebsd.org Thu May 10 20:10:06 2018 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FCA6FD5653 for ; Thu, 10 May 2018 20:10:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from smh-06.1blu.de (smh-06.1blu.de [178.254.0.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E4BF2730A9 for ; Thu, 10 May 2018 20:10:05 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [172.16.29.5] (helo=sh4-5.1blu.de) by smh-06.1blu.de with esmtp (Exim 4.86_2) (envelope-from ) id 1fGrsz-0006V9-Jp for freebsd-x11@freebsd.org; Thu, 10 May 2018 22:09:57 +0200 Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.86_2) (envelope-from ) id 1fGrsz-0007XK-Fb for freebsd-x11@freebsd.org; Thu, 10 May 2018 22:09:57 +0200 Date: Thu, 10 May 2018 22:09:57 +0200 From: Matthias Apitz To: freebsd-x11@freebsd.org Subject: Re: ssh -X remote does not work due to problem with xauth Message-ID: <20180510200957.GA21218@sh4-5.1blu.de> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-x11@freebsd.org References: <20180510182928.GA3747@c720-r314251> <20180510192510.GA38033@elch.exwg.net> <20180510194701.GB38033@elch.exwg.net> <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 20:10:06 -0000 El día Thursday, May 10, 2018 a las 09:57:50PM +0200, Niclas Zeising escribió: > On 05/10/18 21:47, Christoph Moench-Tegeder wrote: > >## Christoph Moench-Tegeder (cmt@burggraben.net): > > > >>I haven't yet checked what causes these differing defaults. > > > >Well, now that I thought about it: most Linux distributions build their > >X server with "--enable-xcsecurity" in the configure flags. FreeBSD > >does not set that flag, as far as I can see. Next question: why? > > > > Hi! > It could be because of backwards compatibility, or, because at least I > wasn't really aware of that flag. Is it for xserver or some other package? > If you have time, please try it out and see what happens. Usually you can > add it to CONFIGURE_ARGS= in the ports makefile and recompile the port. I'm > occupied elsewhere currently, but if I remember I'll look into it as well. > Regards I did a quick check by running 'make configure' in ports/x11-servers/xorg-server and --enable-xcsecurity is not used; I will recompile it with enabled and report back. matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub