Re: [PATCH xserver] present: Only requeue for next MSC after flip failure

2016-03-24 Thread Michel Dänzer
On 25.03.2016 04:51, Adam Jackson wrote: > On Thu, 2016-03-24 at 07:22 -0600, Keith Packard wrote: >> Michel Dänzer writes: >>> From: Michel Dänzer >>> >>> This code was added to deal with the driver present hook failing, in >>> which case we need to wait for the next MSC before executing the >>>

Re: [PATCH xserver] present: Only requeue for next MSC after flip failure

2016-03-24 Thread Adam Jackson
On Thu, 2016-03-24 at 07:22 -0600, Keith Packard wrote: > Michel Dänzer writes: > > > > > From: Michel Dänzer > > > > This code was added to deal with the driver present hook failing, in > > which case we need to wait for the next MSC before executing the > > presentation. > > > > However, it

Re: Proposal for Anti-Keystroke Fingerprinting at the Display Server Level

2016-03-24 Thread Jasper St. Pierre
I think this should be done at the application level. If an application is running, it has many other ways to fingerprint your computer, including listing the files in your homedir, checking cpuid, MAC address, etc. The issue here is that there is an application platform that runs untrusted user co

Re: Proposal for Anti-Keystroke Fingerprinting at the Display Server Level

2016-03-24 Thread bancfc
On 2016-03-24 12:45, Pekka Paalanen wrote: Hi, that's interesting. Sounds like you are looking for volunteers to implement what you want, right? Yes please. Unfortunately I don't know C or have the skill to code something like this myself. I skimmed through [3], and I got the impression

Re: [PATCH xserver] present: Only requeue for next MSC after flip failure

2016-03-24 Thread Keith Packard
Michel Dänzer writes: > From: Michel Dänzer > > This code was added to deal with the driver present hook failing, in > which case we need to wait for the next MSC before executing the > presentation. > > However, it could also take effect in cases where the driver incorrectly > thinks the curren

Re: Proposal for Anti-Keystroke Fingerprinting at the Display Server Level

2016-03-24 Thread Pekka Paalanen
On Wed, 23 Mar 2016 23:49:03 +0100 ban...@openmailbox.org wrote: > == Attack Description == > > Keystroke fingerprinting works by measuring how long keys are pressed > and the time between presses. Its very high accuracy poses a serious > threat to anonymous users.[1] > > This tracking technol

Re: [PATCH glx] glx: avoid memory leak when using indirect rendering

2016-03-24 Thread Guilherme Melo
I've finally got some time to rewrite this patch and now the solution makes more sense. I'm sending as an attachment. I also have some tests on a github repository to check this bug. I don't know if it is ok to post the link here though. Guilherme On Tue, Dec 8, 2015 at 4:48 PM Guilherme Melo w

Re: [PATCH xserver] xfree86/modes: Make sure the HW cursor is hidden when it should be

2016-03-24 Thread Michael Thayer
Looks good to me, but I don't feel I'm quite familiar enough with the code to give a full "reviewed-by". Regards, Michael On 24.03.2016 09:34, Michel Dänzer wrote: From: Michel Dänzer When the HW cursor is hidden (e.g. because xf86CursorResetCursor triggers a switch from HW cursor to SW cur

[PATCH xserver] present: Only requeue for next MSC after flip failure

2016-03-24 Thread Michel Dänzer
From: Michel Dänzer This code was added to deal with the driver present hook failing, in which case we need to wait for the next MSC before executing the presentation. However, it could also take effect in cases where the driver incorrectly thinks the current MSC matches the target one (e.g. due

[PATCH xserver] xfree86/modes: Make sure the HW cursor is hidden when it should be

2016-03-24 Thread Michel Dänzer
From: Michel Dänzer When the HW cursor is hidden (e.g. because xf86CursorResetCursor triggers a switch from HW cursor to SW cursor), the driver isn't notified of this for disabled CRTCs. If the HW cursor was shown when the CRTC was disabled, it may still be displayed when the CRTC is enabled agai