From owner-freebsd-x11@freebsd.org Fri May 11 05:35:45 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 20EC6FB7A80 for ; Fri, 11 May 2018 05:35:45 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB72975474; Fri, 11 May 2018 05:35:44 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id C465023D9B; Fri, 11 May 2018 05:35:44 +0000 (UTC) From: Jan Beich To: Niclas Zeising Cc: freebsd-x11@freebsd.org Subject: Re: ssh -X remote does not work due to problem with xauth References: <20180510182928.GA3747@c720-r314251> <20180510192510.GA38033@elch.exwg.net> <20180510194701.GB38033@elch.exwg.net> <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> Date: Fri, 11 May 2018 07:35:41 +0200 In-Reply-To: <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> (Niclas Zeising's message of "Thu, 10 May 2018 21:57:50 +0200") Message-ID: MIME-Version: 1.0 Content-Type: text/plain 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: Fri, 11 May 2018 05:35:45 -0000 Niclas Zeising writes: > 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? See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221984