Re: DRM security flaws and security levels.

2014-04-14 Thread Rob Clark
On Mon, Apr 14, 2014 at 8:56 AM, Thomas Hellstrom wrote: > On 04/14/2014 02:41 PM, One Thousand Gnomes wrote: >>> throw out all GPU memory on master drop and block ioctls requiring >>> authentication until master becomes active again. >> If you have a per driver method then the driver can

Re: DRM security flaws and security levels.

2014-04-14 Thread Thomas Hellstrom
On 04/14/2014 02:41 PM, One Thousand Gnomes wrote: >> throw out all GPU memory on master drop and block ioctls requiring >> authentication until master becomes active again. > If you have a per driver method then the driver can implement whatever is > optimal (possibly including throwing it all

Re: DRM security flaws and security levels.

2014-04-14 Thread One Thousand Gnomes
> throw out all GPU memory on master drop and block ioctls requiring > authentication until master becomes active again. If you have a per driver method then the driver can implement whatever is optimal (possibly including throwing it all out). > -1: The driver allows an authenticated client to

Re: DRM security flaws and security levels.

2014-04-14 Thread One Thousand Gnomes
throw out all GPU memory on master drop and block ioctls requiring authentication until master becomes active again. If you have a per driver method then the driver can implement whatever is optimal (possibly including throwing it all out). -1: The driver allows an authenticated client to

Re: DRM security flaws and security levels.

2014-04-14 Thread Thomas Hellstrom
On 04/14/2014 02:41 PM, One Thousand Gnomes wrote: throw out all GPU memory on master drop and block ioctls requiring authentication until master becomes active again. If you have a per driver method then the driver can implement whatever is optimal (possibly including throwing it all out).

Re: DRM security flaws and security levels.

2014-04-14 Thread Rob Clark
On Mon, Apr 14, 2014 at 8:56 AM, Thomas Hellstrom thellst...@vmware.com wrote: On 04/14/2014 02:41 PM, One Thousand Gnomes wrote: throw out all GPU memory on master drop and block ioctls requiring authentication until master becomes active again. If you have a per driver method then the driver

Re: DRM security flaws and security levels.

2014-04-11 Thread Rob Clark
On Fri, Apr 11, 2014 at 5:15 PM, Thomas Hellstrom wrote: > On 04/11/2014 10:31 PM, David Herrmann wrote: >> Hi >> >> On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom >> wrote: >>> as was discussed a while ago, there are some serious security flaws with >>> the current drm master model, that

Re: DRM security flaws and security levels.

2014-04-11 Thread Thomas Hellstrom
On 04/11/2014 10:31 PM, David Herrmann wrote: > Hi > > On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom > wrote: >> as was discussed a while ago, there are some serious security flaws with >> the current drm master model, that allows a >> user that had previous access or current access to an X

Re: DRM security flaws and security levels.

2014-04-11 Thread David Herrmann
Hi On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom wrote: > as was discussed a while ago, there are some serious security flaws with > the current drm master model, that allows a > user that had previous access or current access to an X server terminal > to access the GPU memory of the active

DRM security flaws and security levels.

2014-04-11 Thread Thomas Hellstrom
Hi, as was discussed a while ago, there are some serious security flaws with the current drm master model, that allows a user that had previous access or current access to an X server terminal to access the GPU memory of the active X server, without being authenticated to the X server and thereby

DRM security flaws and security levels.

2014-04-11 Thread Thomas Hellstrom
Hi, as was discussed a while ago, there are some serious security flaws with the current drm master model, that allows a user that had previous access or current access to an X server terminal to access the GPU memory of the active X server, without being authenticated to the X server and thereby

Re: DRM security flaws and security levels.

2014-04-11 Thread David Herrmann
Hi On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom thellst...@vmware.com wrote: as was discussed a while ago, there are some serious security flaws with the current drm master model, that allows a user that had previous access or current access to an X server terminal to access the GPU

Re: DRM security flaws and security levels.

2014-04-11 Thread Thomas Hellstrom
On 04/11/2014 10:31 PM, David Herrmann wrote: Hi On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom thellst...@vmware.com wrote: as was discussed a while ago, there are some serious security flaws with the current drm master model, that allows a user that had previous access or current

Re: DRM security flaws and security levels.

2014-04-11 Thread Rob Clark
On Fri, Apr 11, 2014 at 5:15 PM, Thomas Hellstrom thellst...@vmware.com wrote: On 04/11/2014 10:31 PM, David Herrmann wrote: Hi On Fri, Apr 11, 2014 at 2:42 PM, Thomas Hellstrom thellst...@vmware.com wrote: as was discussed a while ago, there are some serious security flaws with the