Input rework

[Ray Strode]

Hi,

On Thu, Dec 18, 2008 at 3:39 PM, Charlie Brej <plymouth at brej.org> wrote:
> Ray Strode wrote:
>>
>> Well question is how to enable it...  It only makes sense to do some
>> cases.
>> How are you gettng the password to pam?
>>
>> We should probably use the automatic login path of gdm to use a pam
>> conversation that doesn't ask for password,
>> and to by pass the greeter entirely.
>>
>> The idea of booting up and getting coffee and coming back to a loaded
>> session sounds nice though.
>
> I hacked a couple scripts together and here is what a mockup looks like:
>
> http://www.cs.man.ac.uk/~brejc8/temp/early_login.swf
Hey that's pretty sweet!.
>
> When you press "L" it shows a question dialogue which asks for a username.
> If that is entered before quit, it activates a script which asks for a
> password. Entry of a password tests pam and then causes gdm to automaticly
> login. One of the things that are missing is a message to state that the
> login was successful and you will be autologged in (go away and have a tea).
> Before loading the gnome-session it starts a screensaver. Once logged into
> gnome it takes absolutely ages to load all the startup apps so I didn't try
> unlocking the screensaver until the HD stopped grinding.
>
> Currently with pam I cheated and used the "pam_auth" that comes with squid.
> Google claims there is no program that does this in the pam package so it
> may mean writing a helper util.
I don't think you should ask for username and password from plymouth at all.
To me this seems like the kind of thing that fits the laptop,
single-user workstation
model very well.  There should ben an option somewhere to toggle it
on.  Once on,
it should just tell gdm to autologin and the lock the screen.

Since screen unlock requires enter a password anyway, it's pretty secure.

Actually we could probably do this from GDM/gnome-session without much
in plymouth at all.

1) Make GDM Autologin set an environment variable GDM_AUTO_LOGGED_IN=1
2) Make gnome-session check that environment variable and do a dbus
call to gnome-screensaver to Lock the screen.

The latter will cause gnome-screensaver to get started if it hasn't already.

> Should this go through FESCo?
Feature process is here:
https://fedoraproject.org/wiki/Features/Policy/Proposals

--Ray