Systemback user authentication

If no user in sudo (and admins) group (so no administrator user), only the root user can be used for authentication.
You can check it, just execute 'groups' command with own user. If no 'sudo' in the list, this user is not administrator.

Here are the results of running 'groups' (first and second machines
respectively):

roger@roger-Inspiron-3531:~$ groups
roger adm cdrom sudo dip plugdev lpadmin sambashare

roger@roger-PowerEdge-400SC:~$ groups
roger adm dialout cdrom sudo plugdev lpadmin admin sambashare

But before I found this <http://ubuntuforums.org/showthread.php?t=2224913>
which points to this <http://ubuntuforums.org/showthread.php?t=2214042>,
'sudo' wasn't on machine 2. I stumbled across the solution while futzing
around with 'su' and 'sudo'. At some point I got the 'no talloc stackframe
... leaking memory' error.

I thought something was weird, since I used 'sudo' to install Systemback.
Could have something to do with #1 being a fresh install and #2 being an
upgraded 12.04 LTS.

In any event, thanks for your quick response, and for nudging me in the
right direction.

-Roger

On Sat, Nov 15, 2014 at 5:56 PM, Kendek <
<email address hidden>> wrote:

> Your question #257680 on Systemback changed:
> https://answers.launchpad.net/systemback/+question/257680
>
> Status: Open => Answered
>
> Kendek proposed the following answer:
> If no user in sudo (and admins) group (so no administrator user), only the
> root user can be used for authentication.
> You can check it, just execute 'groups' command with own user. If no
> 'sudo' in the list, this user is not administrator.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/systemback/+question/257680/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/systemback/+question/257680
>
> You received this question notification because you asked the question.
>

I am a little confused. So now your problem is solved? 'roger' user is selectable in Systemback?
Systemback does not use sudo in directly, but the administrators are identified by 'sudo' group. Members of this group are listed in Systemback.
So if the sudo package is not installed, Systemback checks the root user. You enter the password, and this is compared with stored password hash. So if the root user has a password (not in default), it can be used for identification (just like 'su' command).

Yes, the problem is solved and 'roger' is selectable.

The fix was running 'sudo apt-get remove libpam-smbpass' and rebooting.
After doing that, 'groups' showed that I was a member of the 'sudo' group
on machine 2, and Systemback presented 'roger' as the only choice. Why
that fix fixed it is beyond me at this point.

Let me know if I can provide further information.

-Roger

On Sun, Nov 16, 2014 at 4:31 AM, Kendek <
<email address hidden>> wrote:

> Your question #257680 on Systemback changed:
> https://answers.launchpad.net/systemback/+question/257680
>
> Status: Open => Needs information
>
> Kendek requested more information:
> I am a little confused. So now your problem is solved? 'roger' user is
> selectable in Systemback?
> Systemback does not use sudo in directly, but the administrators are
> identified by 'sudo' group. Members of this group are listed in Systemback.
> So if the sudo package is not installed, Systemback checks the root user.
> You enter the password, and this is compared with stored password hash. So
> if the root user has a password (not in default), it can be used for
> identification (just like 'su' command).
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/systemback/+question/257680
>
> You received this question notification because you asked the question.
>

Thanks for the information, this problem is solved.