To auto-login or to not auto-login?

[Gary W. Swearingen]

Daniel Carrera <daniel.carrera at zmsl.com> writes:

> Hello,
>
> Okay, say I give a computer to a non-technical user willing to try Ubuntu. Should it be set to auto-login?

I gather that you have one customer to please.  "Easy" to make it
depend on his environment, etc.  Maybe let him choose from a small set
of options, after hearing your recommendation.  Of course you can't do
that for all features, but this may be a rather biggie.

If he's comfortable with a GUI that anyone may use at any time, then
try to make it work like a kiosk, with no concept of login, users,
etc.  This can work for some small outfits who trust their people, for
good or ill.  His call, as long as your contract doesn't keep you
responsible for security.  You'll generally recommend one or more
passwords for each person with short-term screen and password
timeouts.  Users are paid to enter passwords; they shouldn't complain
about it, if that's what the employer wants, to keep accountability.
(And that's the main benefit of passwords.  It makes it more likely
that "joe" sent the "joe" message, not "jim" sitting down to joe's
console.  Or that it was joe that deleted some database entry. Etc.)

Companies (or IT suppliers) should give users a good SOP and tools for
maintaining passwords, etc., in lieu of sticky notes.