Chrome Remote Desktop and Wayland

[Benjamin Berg]

Hi,

On Fri, 2020-04-17 at 09:22 -0400, Ray Strode wrote:
> On Fri, Apr 17, 2020 at 3:59 AM Marcel Hollerbach <mail at bu5hm4n.de> wrote:
> > I really like the idea of curtaining the session.
> > However, i am wondering if logind couldn't serve there as sort of
> > gatekeeper
> [...]
> > The idea is that a session in logind can be locked or unlocked. In case
> > it is locked, logind would spin up a "micro" session with a process that
> > renders something to login.
>
> So you're saying logind would take on the function of e.g. GDM?
> 
> I think logind is intentionally primarily about bookkeeping and resource
> passing.  The individual desktops want to be able to design the user
> experience for their unlock screens.

I don't think that it makes sense for logind to spin up such a micro-
session, that is indeed something that needs to be delegated to GDM.

I do however think there is value in supporting such delegation from
the logind side. A primary motivator for me here is systemd-homed, as
it may freeze the user session, making it impossible to re-authenticate 
from within. And really, it would be better if we don't let the user
ever see their own password.

But, it should be as simple as logind forcing a VT switch to the
correct greeter UI/session. Plus a little bit more magic to maybe spin
up the UI in the background before suspending and pre-selecting the
user to make the experience smoother.

Benjamin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20200417/6b5b2725/attachment.sig>