Debian :: Use Same Password For Root And Regular Account?
Jul 7, 2009
I first started using Ubuntu and I liked the sudo facility because I didn't need to remember two passwords, so when I installed Debian I wrote the same password for the limited and the root account. Is this very bad for security? I mean can a program started from my regular account immediately become root or something?
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 forgot the root passwd for linux (via the "single" mode) and, according to all confirms, did so successfully! I then try to log on to Centos as root, and I can't....it says "incorrect passwd"! So then I log on as another, regular, but not root, user, with that passwd, and boot up into Centos. if I try to "su" to root, with the new root passwd, again it says its incorrect. there is no "system admin" passwd set. I checked!. I need root access within Centos!
I am trying to log into a server with a particular account. Let's say I don't know the password for that account. Can I do this using ssh? I am wondering if it is possible to do it in one command, instead of logging in as root and running su.
I have a Debian VPS webserver running a forum, and I'm currently looking for a secondary tech-admin. Since they'll have to have the root password for the server, I'm looking for a way to create a backdoor account that I can use to get in if they divulge the root password, or go crazy and lock me out. Is there a way to do it?
I have a Windows domain with a proxy. I have an account that can use the proxy and the URL that points to the proxy.pac file. this might seem a stupid question but can anyone tell me how do I enter the username and password for my test Windows account so that Debian can authenticate it?
I came to debian from fedora so there I used ( su - ) to become root user. So my question is that in debian, is it same using ( su ) and ( su - ) or here also using ( su - ) is preferred with slash or without slash. What is the correct and secure way in debian with full root status.
One more question relating gedit sources.list
I use as root account : gedit /etc/apt/sources.list (and then enter and sources file in gedit open)
Is this correct method or any other way as when save after changing entries inside it says error.
How do I activate networking? (I am currently logged in from Ubuntu on another computer). I installed Debian Squeeze on an iMac 7.1 (which works perfectly well with ubuntu) from the netinstall CD (today's daily build), and of course I deactivated root login, coming from ubuntu. Now I find I have to enter my root password (login password will not do) to activate networking! Is this a joke? I had the network configured with DHCP during install! So how do I activate the root account, or, more to the point, how do I get by in Debian without activating root login?
I edited fstab to automatically mount my windows data partition on boot, but I screwed it up by not specifying the file system type, however that is not the problem, I was able to fix that easily. The problem was that when it failed to mount the partition, Debian automatically entered root and I guess that is to be expected in order for me to fix it, but I never configured a root password and it just gave me full root access without asking any password, not even my user password. I though that was strange so I set the root password and sure thing it asked me for the root password this time without automatically logging into root....
I then tried to lock the root account to see if it will ask me for a password or not, it did but of course I wasn't able to login as root because it was locked now and I was left with no way to access the system. I had to fix fstab from a live cd so that I can login normally as the user....
I didn't know what to search for or if that is the expected behavior if you don't set root password during installation, but it just seemed a bit strange to automatically enter root when you specifically disable root login during installation...
I just installed Debian 6 on a server and when the server powers up, it shows me all the accounts I created in order for me to choose and login under an account, except for the root account. At the colo where the server is going, they need the root account at the login screen.
I have a win XP box and want to share files on this win XP box In Ubuntu 10.10 I previous used, I just connect the win XP sahred folder via file browser without any username and password. In my Debian Squeeze, when I connect to my win XPIt poped up a window and asked me the username and password. But I don't set any password in my win XP even my administrator account. How can I do to make my connecting to win XP smoothly like the Ubuntu does?
I made a Desktop User account. When I went on that account, it allowed me to execute sudo as if I was an administrator. I don't know what might be causing this. I do have ufw set up and blocking incoming connections. Do you guys know what might be at the root of this?Also, when I used sudo from the user account (which I shouldn't have been able to do), I provided the password for my admin account.
I've started to get emails that would typically come from [URL] as [URL]. These emails come from services that send out emails (backup programs) directly, or from cronjobs. I've logged in as the non-root account and either sudo su - or su - to root and the restart the service at one point or another. If I login directly as root and bounce the service or cron the emails come across as from root. I don't see anything in my environment variables after I su to indicate what would cause this. I'm not sure where else to look? A pam setting? This seems to have happened between Fedora 10 and 14 (did a bunch of overdue upgrades recently) I've only got Fedora so I don't have anything to compare to. In Fedora 10 I did not have this problem.
I tryied to modify the root password, but instead of using the "passwd" command, i tried to use "usermod -p", without knowing what outcome exactly i would get. But since then, i can't log as root, neither with my old neither with my new password. And i can't install absolutely nothing on my machine.
Please, help me... i have a test next wednesday, and i can't work in my blueprint. In appendix, i've uploaded a print screen of the sequence commands, for you to be able to explain me this phenomenom and to tell me how to solve it.
I just did a net install of Debian Jessie in VMWare Player. I very much enjoyed the install. I chose not to install a desktop. I set the root password as root. And the user as paul/paul. Now I cant login in root, it says I have the wrong password. How would you resolve this?
After installation of Debian 5.0.4 when a window is shown to type the root password, after I have typed it and press OK, window is closed and nothing happen. I have verified that root password is correct, also I have reinstall Debian, but nothing is changed. Is there something to enable?
I know there has to be a way to log in as root through the GUI. I reverted back to the old GDM to get this problem fixed but it took out packages that I needed and the problems started which required me to reload Squeeze via the 8 DVDs. I don't want any posts talking about the dangers of logging in as root as I know what the consequences are. I don't want to play in the terminal mode either. I created an Admin passwd during installation. how to link the Root name to the Password during log in.
I am trying to reset the root password of Squeeze so that I may be able to update. I forgot it. I have followed the howto Reset Root Password without success. I am getting a root prompt but for some weird reason the root commands are not found. When I type passwd, I get, "command not found". Moreover, If I try reboot and shutdown -h now, both fail.
I finally got Sueeze installed and it works great for my user account. It won't accept my root password and so I can not do anything as root. This is strickly a home desktop setup and I am the only user. I have a working Ubuntu 10.10 in the ajacent partition. How can I change (or reinstall) my root password. Everything I've found says to boot single user and I have, but I still need the root password in Debian.
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.
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.