Page 3 of 3 FirstFirst 123
Results 21 to 22 of 22

Thread: Ubuntu + CUPS = Cannot Admin via {hostname}:631

  1. #21
    Join Date
    Jul 2008
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Ubuntu + CUPS = Cannot Admin via {hostname}:631

    Quote Originally Posted by AlexDudko View Post
    This is default for Ubuntu (and maybe other sudo based distro's) and usually there's no need to change anything. It works good and allows logins with the admin user name and its password.
    The admin user is the user which was created within the system installation procedure.
    But if root user is set then to log in you must enter root as login name and root password. (This is usually default for su based distro's).
    I believe you are correct. All the files in /etc/cups/ are owned by root. The only way that a user on a sudo based distro can can modify a file is to be a system admin (a member of the sudo group in the latest version of Ubuntu).

  2. #22
    Join Date
    Oct 2012
    Beans
    182

    Re: Ubuntu + CUPS = Cannot Admin via {hostname}:631

    CUPS is run by root

    To administer a single service remotely using root is not a good idea specially when you have to delegate limited access to someone else.
    Additionally root login is disabled on ubuntu.

    I cups the workaround is to allow a group or groups to do the administration. The default group is lpadmin i.e.
    Code:
    # Administrator user group...
    SystemGroup lpadmin
    One can change it or add another group to it but the better way is to add the user to this group who will be responsible for cups administration.

    I don't know about the server versions but on desktop version the default first user is also a member of lpadmin group. On server version i guess the user scheme is different and there is no user present for this purpose therefore a user needs to be created who will be a member of lpadmin group and can do the cups administration.

    The cupsys user is obsolete I guess because everywhere in the documentation root is mentioned now and this is the user under which cups is running.

    These are my findings so far.

    Just tested the cups and remote administration by creating a new dummy user who is a member of lpadmin group only and it successfully logged in did administration tasks like adding and deleting printer, setting deafults for the printer, sharing over network etc. So now I can confirm the a user needs to be only the member of lpadmin group to handle cups administration.
    Last edited by pkadeel; November 16th, 2012 at 07:55 PM. Reason: Implementation results of current findings

Page 3 of 3 FirstFirst 123

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •