Date: Thu, 10 May 2018 22:09:22 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: freebsd-x11@freebsd.org Subject: Re: ssh -X remote does not work due to problem with xauth Message-ID: <20180510200922.GD38033@elch.exwg.net> In-Reply-To: <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se> References: <20180510182928.GA3747@c720-r314251> <20180510192510.GA38033@elch.exwg.net> <20180510194701.GB38033@elch.exwg.net> <466cd23b-344a-8d8a-d936-3ac38edff4a8@daemonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
## Niclas Zeising (zeising+freebsd@daemonic.se): > > 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. I'd say "everyone else uses that flag, so we should, too". And that flag isn't really new, e.g. Redhat re-enabled it in 2013: https://access.redhat.com/errata/RHSA-2013:1620 > Is it for xserver or some other package? That would be x11-servers/xorg-server, yes. > 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. I'll try that tomorrow or saturday. Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180510200922.GD38033>