Wayland protocols

[Martin Gräßlin]

On Tuesday 19 August 2014 11:23:11 you wrote:
> On Tuesday 19 August 2014 11:03:48 Martin Gräßlin wrote:
> > On Tuesday 19 August 2014 10:51:43 Pier Luigi Fiorini wrote:
> > > *) ksmserver is a Wayland client that binds kf5_shell
> > > *) ksmserver is asked to lock (via loginctl, plasmoid or context menu)
> > > *) ksmserver calls the kf5_shell.lock request
> > > *) kwin hides all surfaces, prevent input and maybe turn the screen off,
> > > this is all independent from the greeter being running or not
> > > *) kwin emits the prepare_lock_surfaces and ksmserver picks it up
> > > *) ksmserver runs the greeter which will create the surfaces
> > > *) ksld use set_surface_role to set the lock role on those surfaces
> > 
> > how does ksld know about the surfaces? They are created by the greeter
> > process. If that requires to pass surface information between ksmserver
> > and
> > the greeter I'm wondering what we gain compared to letting KWin handle it
> > directly.
> 
> I mistaken ksld with the greeter.

ok, so it's
*) greeter use set_surface_role to set the lock role on those surfaces

but then: how does kwin know that this is the greeter which is allowed to use 
it and not some nsa-greeter which wants to bypass the greeter?

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140819/8c0b47b1/attachment-0001.sig>