From owner-freebsd-x11@freebsd.org Thu May 10 19:58:07 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 138E3FD510F for ; Thu, 10 May 2018 19:58:07 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A3B88701C5 for ; Thu, 10 May 2018 19:58:06 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40hkY83JPpzDhG5 for ; Thu, 10 May 2018 19:58:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1525982283; bh=q0ele3uf8WiQBcIG2fzTtS4x ua4zGf0G7H4HlxQgXJA=; b=otW0UtQFUiec9G0Yz6oFoZhFhX4oTby5ufhBGpDh k5PdTbhGKpFBt4vhhxShzMVQE9ZIe6A9RXTxdj5w8DNNAhxmdihFLSA6Im9R9kZ+ H+fBBwAByxeMFsI4me3+WLDey3g/Iio4fGBSUPGz2ljWI83rnrgs+GZyTfTPiEcv /Dg= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id gqVmUN6xC5v5 for ; Thu, 10 May 2018 19:58:03 +0000 (UTC) Received: from garnet.daemonic.se (host-90-236-116-88.mobileonline.telia.com [90.236.116.88]) by mail.daemonic.se (Postfix) with ESMTPSA id 40hkY72pzLzDhBg for ; Thu, 10 May 2018 19:58:03 +0000 (UTC) Subject: Re: ssh -X remote does not work due to problem with xauth To: freebsd-x11@freebsd.org References: <20180510182928.GA3747@c720-r314251> <20180510192510.GA38033@elch.exwg.net> <20180510194701.GB38033@elch.exwg.net> From: Niclas Zeising Message-ID: <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> Date: Thu, 10 May 2018 21:57:50 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20180510194701.GB38033@elch.exwg.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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 19:58:07 -0000 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 -- Niclas