Hi,
I would like to use untrusted connections for remote
clients. Currently this does not work for me, because it is
too slow, and I always have to use trusted connections.
So I wonder what it would take to expose some additional
extensions that are required for efficiency to untrusted
clients,
On pátek 6. října 2017 9:40:31 CEST Michel Dänzer wrote:
> On 05/10/17 07:47 PM, Damien Miller wrote:
> FWIW, xserver >= 1.18.4 detects SSH connections via the client's process
> name, treats them as remote and doesn't expose DRI3 on them.
Oh, that's actually workaround that would be sufficient,
On pátek 6. října 2017 4:47:06 CEST Damien Miller wrote:
> Is it too late to make the DRI3 developers adjust their protocol to degrade
> gracefully?
I am not sure, but I think it would be already able to degrade if it was able
to detect error. But from what I observed, after X server
On 05/10/17 07:47 PM, Damien Miller wrote:
> On Wed, 4 Oct 2017, Michal Srb wrote:
>> On středa 4. října 2017 5:53:15 CEST Damien Miller wrote:
>>> On Mon, 2 Oct 2017, Michal Srb wrote:
SSH only needs to change the first byte sent from X client to server
to mark it as remote. SSH already
On Wed, 4 Oct 2017, Michal Srb wrote:
> On středa 4. října 2017 5:53:15 CEST Damien Miller wrote:
> > On Mon, 2 Oct 2017, Michal Srb wrote:
> > > SSH only needs to change the first byte sent from X client to server
> > > to mark it as remote. SSH already modifies the whole first message
> > >
