Debian Configuration :: When User Is Admin Root Password Is Still Needed
May 7, 2015
I'm using Debian Jessie Cinnamon right now. I've got 1 user account on my machine--fred--as well as root, of course. "fred" is an administrator, and many times that is enough for root priviledges, for example, I can install packages via apt or dpkg. However, I cannot access "Users and Groups", or install packages via GDebi, with my password. For that, I have to have the root password.
I know that it is possible to let the admin account handle everything and not even need root--for example, Mint and (I believe) Ubuntu do it this way. I don't know how, though.
Code: Select allgroups fred
fred : fred cdrom floppy sudo audio dip video plugdev netdev lpadmin scanner bluetooth
I did disable the root account by Code: Select allsudo passwd -l root to see if it would make any change. Nothing different happened except that I now can't use GDebi or access "Users and Groups" since the root account and therefore password is inactivated. Not a big deal to get it back, though.
I have lost my password for my root and for my user account.
Code: Select alluser@debian:~$ su Password: su: Authentication failure user@debian:~$ su Password: su: Authentication failure user@debian:~$ su
I have just installed a gust debian 8 on debian 8 host in virtualbox, and when i wonted too login as su/root on the host there where no login possible, is there a way to regain the root password for the host?
I'm on Squeeze with KDE 4.4.5. Basically, I can use my password for things like logging in, or authenticating on a shell with sudo successfully. But in other cases, I am asked to "become root", and when I enter my usual password, I'm told to check if I entered my password correctly. This happens with Aptitude (terminal GUI), for example: from Actions, I try to update the package list, and when I enter my password, I can read su: Authentication failure. However, if I start Aptitude by typing kdesudo aptitude on Konsole I can enter my password in the authentication box successfully, and use Aptitude with administrative privileges.
The example is valid also for other applications, such as System Monitor: just for the sake of the example, if I try to stop a process owned by root, say Aptitude, I'm asked for a password to become root, but my password doesn't do the trick. I'll have to open it from terminal with kdesudo ksysguard, then I'll be allowed to kill that process. Does it have anything to do with my choice at installation? I think I must have chosen to leave the root password field blank, and only entered my password as a user, for it explained I could become root anytime if there was need to with sudo.
I have a minor problem with my "Update Applet 2.28.0" in Gnome. It occurs when I want to make the applet do one or more suggested update(s). It always asks me for the password of superuser/root: "Authenticate : Authentication is required to update packages. [...]". I think under my installation before (11.1 maybe updated from an older version) I could tell the automatic/semi automatic updater to remember the su password (in YaST or in the authentication dialog?).
In the help manual on my computer (and in the internet) there is the possibility to make the updater remember the password via policy kit: ("Access to all privileged operations is controlled via PolicyKit." See: GNOME Documentation Library : gnome-packagekit Manual : Introduction) I could not find any policy kid or any other possibility to give to the automatic updater (or its user) that privilege permanently (=to remember authorization). I think on a system with more (real) users this could be a real problem (not just an inconvenience).
For my dissertation I created a debootstrap install of Lenny. When I boot this system I just can login with root without a password. When I want to ssh this machine with the debootstrap install I can't just login with root. I'm asked for a password which I don't have.
So I created one with passwd root and after that I can connect to the machine with ssh and the given password. But the machine still logs in with without a password.
Reinstalled Debian Squeeze (64bit/gnome) on my Notebook using Netinstall. Everything worked like always but in the setup instead of typing in a root password as asked to i just pressed enter (in the hope of not having to type in a pw in the console later, just having to press enter then)
When i needed rootpw to install some software (using SoftwareDownloader) the normal loginpw seemed to work, but not in the console. ari@HP625:~$ su - Password: su: Authentication failure
I'm running sid, reasonably updated. I decided to add a samba share. I installed samba (2:3.4.8~dfsg-2), samba-tools, smbclient, smbfs, & samba-client. I did a "/etc/init.d/samba start" and even rebooted. But when I try to add a samba password for my regular user I can't.
# smbpasswd -a praxis bash: smbpasswd: command not found I did a "locate smbpasswd" but I'm only seeing:
I'm new to Linux (had some basic Unix experience in 1995 era). (Teenager) gave me HP2133 mini notebook running SUSE Linux Enterprise Desktop 10. Everything checks good (hardware and software), even wireless networking. Problem is she apparently created Admin/root password but says cannot remember. I cannot even set correct date time... yast is asking for root privilege: Command: /sbin/yast2 time Is there anything I can do to re-establish administrator privilege?
I try to install my printer again after reinstall ubuntu 9.04. ("downgraded from 9.10"). Instead of asking for the local-user-login password, as it does for other system changes, it asks for a root password that I never had. What happened? How can I set this right?I made a printscreen.
Suddenly Debian started rejecting my user pw and I have to login as root. Perhaps this is a coincidence, but this started when I re-booted after adding Russian keyboard layout in etc/default/keyboard. The Russian keyboard added successfully.
Being logged in as root, renewed the pw of my user account (actually assigned the same as wes previously), got confirmation the the pw has been changed. Reloaded. Yet it keeps complaining that the pw is wrong.
on my netbook I've tried to make possible for my user to shutdown without needing a password. battery could run low when I'm not in front of it. Editing sudoers has allowed my user to shutdown the system, but Gnome still prompts me for the root password whenever root is logged in too. That's usually the case, because to avoid entering the root password multiple times whenever I need elevated privileges and not wanting to cache the root password, I keep a Root Terminal always open.
One of the feature in my application involve changing of hardware setting. This require the user to be root or have administrative right.Before my application enable that feature, I want it to check whether the user is "root" or not, or whether user use "sudo" command to run the application or not, or whether the user has administrative rights or not.What are the codes or library that can do this?
NOTE: Sometimes, advanced linux user may set the user id of root to something else other than 0. So, getuid() may not be helpful in this case.
I have a very strange problem.ometimes, yes sometimes not all the time, I get a Destination Host Unreachable when I ping a computer on my network. If I switch to root using su I can ping that same computer. Here is a screen shot:
joseph@laptop:~$ ping 192.168.1.14 PING 192.168.1.14 (192.168.1.14) 56(84) bytes of data. From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
I upgraded a Guruplug Display machine running Lenny to Squeeze. It's running Linux on a MicroSD device, running an ARM-cpu.
# uname -a Linux gplugD 2.6.29 #1 Wed Feb 16 17:59:04 IST 2011 armv5tejl GNU/Linux yeri@gplugD ~ $ cat /etc/debian_version 6.0.1
However, after rebooting, every non root user was unable to access anything related to the net.This means, DHCP failed to auto start, ntp is giving errors, etc
# ntpq -p localhost: timed out, nothing received ***Request timed out
Mar 27 06:07:44 localhost ntpd: ./../lib/isc/unix/ifiter_ioctl.c:348: unexpected error: Mar 27 06:07:44 localhost ntpd: making interface scan socket: Permission denied Mar 27 06:07:44 localhost ntpd: Too many errors. Shutting up.
gplugD ~ # ping 184.108.40.206 -c 1 PING 220.127.116.11 (18.104.22.168) 56(84) bytes of data. 64 bytes from 22.214.171.124: icmp_req=1 ttl=58 time=42.1 ms
Having installed Debian 7 on an old machine from a Liinux Format Magazine DVD I was unable to log in as a specific user. I can login as root and use useradd etc but when I logout of root I still cannot login as a user and nor will the machine accept my root password. I have to shutdown and reboot to get back into root. I'm using O'Reilly's Linux Pocket Guide from 2004 for the commands. Could it be that things have changed?
I am using debian squeeze server with asterisk 1.6 installed and configured.my problem is non root users need to access the server using ssh and restart asterisk server after making changes in asterisk configuration files.As of now i am giving root username/password for this process (i know it is not at all a good idea) .now how can i create a username and configure it which can only access and modify asterisk configuration files and restart asterisk server without any other privileges.
I keep receiving the error message in the title above whenry to enterebmin.abc.com/webmin. I'm on Ubuntu 9.10. Other errors I'll receive are "You do not have access to any Webmin modules". Wondering if anyone knew what settings our permissions on files I could change to avoid these error
I no longer have access to my root desktop. On a session I attempted to change the root username but i apparently assigned it a wrong directory that does not exist. When I rebooted with my new root username, i was instead recognised as a simple user (no root privileges). I tried the console to change to "old" root but root password is not accepted and there is no way to access to sudoer files. it seems that inserting a new username requires root privileges and i am back to square one. Simply logging with old root username and password after restart gives me a blank screen with nothing on it and cannot even reboot.
At the RHEL prompt, I entered the standard user's username/password combo. Linux displays a message box stating:"Your account has expired; please contact your system administrator."Next, I entered "root" in the username field and entered the root password (which expired also--keep in mind that passwords are set to expire after x days). Linux displays a message box stating:"You are required to change your password immediately (password aged)."When prompted to "Enter current UNIX password", I entered the new password (was that the right thing to do?); Linux displays a message box stating:"The change of the authentication token failed. Please try again later or contact the system administrator."I rebooted the system and got into command line mode; somehow I logged in as "root" (don't know exactly how, but needed to change the password there). At the "#" prompt, I type "passwd root"; Linux displays the message "Changing password for user root", followed by the message "passwd: Authentication information cannot be recovered.
A friend of mine has told me to set a root password and use root (f.e. switching to su in terminal and work with root rights instead).Is there any way to unset the root password? I know how to use sudo now.
I use two separate systems both running Debian 8. On one (my main) I can't do some commands including ping, shutdown and reboot without running them as root user, however on my other system I can ping and reboot as a non-privileged user. The permissions on both systems are the same for /bin/ping and /sbin/systemctl (reboot). I thought at first it was something to do with what groups my main was in, but that doesn't seem to be the gase.
I know I can fix it by setting setuid for both, but my question is why is it different on both machines? Is there a global setting controlling this in /etc or perhaps an icmp setting?