Call for Bikeshedding: remote auth at install time

Simo Sorce simo at
Tue Jun 4 12:43:39 UTC 2013

On Mon, 2013-06-03 at 18:07 -0700, Adam Williamson wrote:
> We all know what devel@ does best, so let's fire up the power of the
> bikeshedding machine :)
> We had on the list of
> release blocker candidates that we evaluated at the blocker review
> meeting this morning. Attendance at blocker reviews is pretty spotty
> these days (please, people, come out and feel in a position of ABSOLUTE
> POWER), and no-one present felt like they were a huge expert on typical
> remote authentication use cases, so we really didn't feel qualified to
> make a call on this one.
> As things stand, in Fedora 19, it's basically impossible to configure
> remote authentication from the install/firstboot process. If you want to
> use remote auth, you'd have to create a local user first and then do it
> using whatever tools are available. anaconda / initial-setup has a
> button for "Use network login..." on its 'user creation' spoke which
> ought to be where you configure remote auth, but right now it does
> precisely nothing at all.
> Whether this is a blocker or not comes down to a judgement call, because
> it hinges on whether this is a significant inconvenience for a large
> enough number of users. So we need to know from people who use Fedora in
> remote auth environments whether it's a big problem not to be able to
> set it up at install / firstboot time, or whether you'd be okay with
> creating a local user to get through initial-setup and then configuring
> remote auth from that local account.

Can we get back an option to not create a user at first boot ?

Even with great warnings, I usually just drop to the console, login as
root and configure the machine, then go back to GDM and login with the
remote user. I prefer not to create a local user that may conflict (uid
wise) with remote users.


Simo Sorce * Red Hat, Inc * New York

More information about the devel mailing list