General :: Using SSH To Log Into A Non-root Account Using Root Password
Feb 10, 2010
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 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?
Is there a way to login to an account with only the root password? Because I really need it the first unlock the computer next to me and second because I just want to know.
i used opensuse 11.1 ...there is option for root user to create password for root...but for ubuntu i did not find anything like that...so how can i create root password....or how can i use root
I was trying to edit a file requiring root permissions, so I used sudo. I typed the root password and it failed. This happened three times, and the process was ended. I then logged in as root (su) and was able to navigate to the file and make changes as root. Am I missing something? How would I edit the sudoers file such that this password would work? Or is there another way to log in to the sudo group to make these changes? How do I set sudo passwords?
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 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 am having problems with privileges i have created a new user with my name, but i cant get root privileges on it. i need the same privileges as the root profile.
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 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.
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...
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 deleted the root line in passwd and shadow and then tried to copy the backup and was able to put it all back to normal from rescue mode. However when i get to my login screen i can not login as root anymore or even after logged in as another user i can not su - or su root, it tells me that root user does not exist......
I have set up my crontab and whilst Im logged in and it works (It runs my shell script), however when Im not logged in, the script does not run. Initially I set the time/date to 0 0 * * * (Midnight every day), as this did not work, I tested it with to 0 * * * * (every hour) whilst logged in and the script starts.
I use crontab -e to set it up under the root account..Im sure you dont have to be logged in for it to run?, but maybe im missing a step or just overdosing on Linux and need a holiday:-)
I want to add a new user. For that purposeI switch to su and give root passwd. There I gave a command " useradd ". [smith@localhost smith]#adduser when i press enter key by typing adduser command it say me "Command not found" .Then i log off from my own account and login again from root account. The command "useradd" is then accepted.is there any way that without logging off from normal user account I may enter my roor accout and work as a root account instead to log off from normal user account.
I found this on Bee's website. For more info on this exploit there are links there:[URl]..All you have to do in Fedora 13 is enter the following lines in a shell as normal user:
[Code]...
I don't think this can be considered solely an "upstream" problem, because I first tried it in Arch using the same version of glibc, and the final command causes both gnome-terminal and xterm windows to disappear.
What is the user account number when you create a root user account for the system during the installation of any linux distribution? I'm not sure if its 0, 1, 10, or 100..
I am a user of a cluster. I don't want root to see/copy files from my user account(obviously). Is that possible to limit the access of root to users account?
I am an absolute Linux Beginner who is being required to do a bit of admin work because the boss just fired the old linux admin. Unfortunately, one of our employees cannot remember her password to her email account and as such I need to reset it on our linux server.What I want to check is that this email account is actually a linux user account and I simply will reset the password for it using the passwd command from the root login. Is that correct?
In the ubuntu series I find my hard disk description as this: /dev/sda. As we know in slackware (10.1) for partitioning we either use 'fdisk' or 'cfdisk' when I use fdisk, like mentioned: fdisk /dev/sda. It says disk cannot be found.... or something like that. I think I know why?
You see my hard disk has the D: E: F: as extended partitions comprising logical drives and only my C: drive is pure primary. Does this have any connection with my problem? As from my explanation you can find that I'm a total wreck with computers.. but I'm very thrilled to learn linux. The reason why I need slax is that I require a traditional root account.
This causes Tomcat to be run as myuser, which is expected. However after issuing the reboot command the system starts up and root is now the owner of this process. How can I force the process to be started off as myuser on reboot?
On a Fedora Core box, I have a normal non-privileged user and I also have sole access to the root account. Because I am the only administrator of this box, I frequently su over to root for administrative tasks. The problem is that many of the user configuration I've become accustomed to are only configured on my day-to-day account (.vimrc, .bashrc, .screenrc, etc). Other than giving my day-to-day user account privileges to perform administration tasks, how would I go about sharing configuration between these two accounts?
Or would this sacrifice security in some way? I've been using root only, and am ready to have a seperate account now. It's the dotfiles for GUI apps that I'm concerned about:
Code: -rw------- 1 root root 98 Feb 13 16:23 .Xauthority -rw------- 1 root root 6392 Feb 12 18:13 .bash_history drwx------ 5 root root 4096 Jan 13 17:47 .config drwxr-xr-x 4 root root 4096 Dec 29 21:36 .fvwm drwx------ 4 root root 4096 Nov 7 19:55 .mozilla -rw------- 1 root root 218 Jan 26 10:04 .recently-used.xbel -rw------- 1 root root 98 Feb 13 16:23 .serverauth.17096 drwxr-xr-x 2 root root 4096 Dec 25 12:42 .tuxcmd drwxr-xr-x 2 root root 4096 Feb 12 17:25 .xine
Is there a non-root shell command that can tell me if a user's account is disabled or not? note that there is a fine distinction between LOCKING and DISABLED:
LOCKING is where you prepend ! or * or !! to the password field of the /etc/passwd file. On Linux systems that shadow the passwords, this marker flag may be placed in /etc/shadow instead of /etc/passwd. Password locking can be done (at a shell prompt) via password -l username (as root) to lock the account of username, and the use of the option -u will unlock it.
DISABLING an account is done by setting the expiration time of the user account to some point in the past. This can be done with chage -E 0 username, which sets the expiration date to 0 days after the Unix epoch. Setting it to -1 will disable the use of the expiration date.
The effect of locking to to prevent the login process from using a supplied password to hash correctly against the saved hash (by virtue of the fact that the pre-pended marker character(s) are not valid output character(s) for the hash, thus no possible input can ever be used to generate a hash that would match it). The effect of disabling is to prevent any process from using an account because the expiration date of the account has already passed.For my situation, the use of locking is not sufficient because a user might still be able to login, e.g. using ssh authentication tokens, and processes under that user can still spawn other processes. Thus, we have accounts that are enabled or disabled, not just locked. We already know how to disable and enable the account - it requires root access and the use of chage, as shown above.To repeat my question: is there a shell command which can be run without root privileges which can output the status of this account expiration info for a given user? this is intended for use on a Red Hat Enterprise 5.4 system.The output is being returned to a java process which can then parse the output as needed, or make use of the return code.