|
stealth
|
 |
« on: January 22, 2012, 01:17:33 AM » |
|
I have a new user who I switched from windblows to PCLOS. I set up the machine and everything worked as it was supposed to work.
She went home about 90 minutes away and started logging into her machine as root instead of doing what I told her to do. She called asking questions and I found out what she was doing and explained to her that she needed to run as user and not root. Now she can't access any app from her user account that requires the root password. She can still login as root.
So is there a way to setup the machine while in root to block users from accessing root password required apps in their user accounts even when they know the root password? I have never heard of such a thing so I am asking. I am guessing the best way to fix the problem is to start over and reinstall the OS.
|
|
|
|
|
Logged
|
|
|
|
marcin82
Full Member
 
Offline
Posts: 112
Metal is forever! // Yoda Królem Polski!
|
 |
« Reply #1 on: January 22, 2012, 03:13:16 AM » |
|
I am guessing the best way to fix the problem is to start over and reinstall the OS. It's not necessary. Run your system - when you will see Grub menu press Shift (stops counting to start the system). Then press F3. Delete word "nokmsboot", type single and press Enter. System will start in single user mode with prompt of sh shell. Then you will be able to setup new root password: passwd root [Enter] Type twice new password and reboot. ;]
|
|
|
|
|
Logged
|
 marcin82
|
|
|
|
stealth
|
 |
« Reply #2 on: January 22, 2012, 03:26:40 AM » |
|
Unfortunately that won't solve the problem. The user password for the user account works and the root password for the root account works. But when she tries to open Synaptic in her user account and types the root password to update her system she gets access denied. She was used to the windblows method of running as admin and just assumed that she needed to do the same thing with Linux even though I warned her several times not to do that. She did it anyway and started changing things while logged in as root. Probably the only way to be sure the OS is working properly is to reinstall the whole thing. I bet she won't make the same mistake again.
|
|
|
|
|
Logged
|
|
|
|
marcin82
Full Member
 
Offline
Posts: 112
Metal is forever! // Yoda Królem Polski!
|
 |
« Reply #3 on: January 22, 2012, 03:30:56 AM » |
|
Try run in a console: gksu synaptic or: kdesu synaptic Always you can run upgrade from console: su - [passwd] then: apt-get update && apt-get dist-upgrade
|
|
|
|
|
Logged
|
 marcin82
|
|
|
|
bicol_willem
|
 |
« Reply #4 on: January 22, 2012, 03:42:34 AM » |
|
It is not something silly like "CapsLock" on I hope (happened to me, LOL!)
|
|
|
|
|
Logged
|
|
|
|
|
stealth
|
 |
« Reply #5 on: January 22, 2012, 04:57:32 AM » |
|
I don't know if it is CAPS lock. I will have to ask her. I think it maybe something a lot more serious because she was logged in as root and not as a regular user. She was changing things. What things I don't know. She mentioned some other things as well and I am thinking it is all related to her being logged in as root and changing things. Being logged in as root is very dangerous because you have total unfettered access to everything and don't need the root password for anything. As root you can do whatever you want to do and you won't have any safety system to keep you from messing up. I know from experience that root can totally trash a system especially when a person has no idea what he or she is doing. New users coming from windblows don't know what they are doing in the beginning. When I was learning Linux many years ago I messed up my system a few times.
|
|
|
|
|
Logged
|
|
|
|
|
bicol_willem
|
 |
« Reply #6 on: January 22, 2012, 05:31:42 AM » |
|
Yeah, I am today still a Linux user THANKS to root but that is an other story that got me even banned on a forum, so I won't tell you!  But ... it is a new user. Set her up fresh again and do a "autologin" for the user. At least she will be logged in as 'user' automagically.
|
|
|
|
|
Logged
|
|
|
|
|
Leiche
|
 |
« Reply #7 on: January 22, 2012, 06:54:51 AM » |
|
I don't know if it is CAPS lock. I will have to ask her. I think it maybe something a lot more serious because she was logged in as root and not as a regular user. She was changing things. What things I don't know.
Here is the best way, to remove the actual user, and generate a new from a healty user account... Next point is to tell, never login in a root account, when it's not need. When it's need make sure you don't go in www without a firewall... My opinion...
|
|
|
|
|
Logged
|
|
|
|
|
Just18
|
 |
« Reply #8 on: January 22, 2012, 07:33:58 AM » |
|
I would go for a reinstall ........ you have no idea what she may have been at while running as root, and something may crap out at some future time because of it.
So, IMO, reinstall from scratch ..... I would even format the /home partition ....... and then remove the ROOT user from the users displayed at login.
|
|
|
|
|
Logged
|
MLUs rule the roost!
Linux XPS 3.2.17-pclos1.pae.bfs 32 bit Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz 4 GB RAM MCP51 High Def Audio GeForce GTX 550 Ti PHILIPS DVD+-RW DVD8701 Logitech BT Mini-Receiver Afatech DVB-T 2 USB DTT
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4107
Have a nice ... night!
|
 |
« Reply #9 on: January 22, 2012, 07:37:09 AM » |
|
I would go for a reinstall ........ you have no idea what she may have been at while running as root, and something may crap out at some future time because of it.
So, IMO, reinstall from scratch ..... I would even format the /home partition ....... and then remove the ROOT user from the users displayed at login.
+1
|
|
|
|
|
Logged
|
|
|
|
|
parnote
|
 |
« Reply #10 on: January 22, 2012, 08:10:20 AM » |
|
I would go for a reinstall ........ you have no idea what she may have been at while running as root, and something may crap out at some future time because of it.
So, IMO, reinstall from scratch ..... I would even format the /home partition ....... and then remove the ROOT user from the users displayed at login.
Another +1 ... no way to know what all she has done to the system. Safest (and quickest) is to just wipe everything, reinstall, and reformat the partitions as part of the installation process. parnote
|
|
|
|
|
Logged
|
|
|
|
Neal ManBear
Administrator
Super Villain
   
Offline
Posts: 15188
LXDE! Coffee, Bacon and Cheesecake!
|
 |
« Reply #11 on: January 22, 2012, 09:08:06 AM » |
|
I would go for a reinstall ........ you have no idea what she may have been at while running as root, and something may crap out at some future time because of it.
So, IMO, reinstall from scratch ..... I would even format the /home partition ....... and then remove the ROOT user from the users displayed at login.
Another +1 ... no way to know what all she has done to the system. Safest (and quickest) is to just wipe everything, reinstall, and reformat the partitions as part of the installation process. parnote +1! Reformat and reinstall. Use different passwords. Why? She may have connected to the net as root and exposed her passwords.
|
|
|
|
|
Logged
|
|
|
|
|
Crow
|
 |
« Reply #12 on: January 22, 2012, 10:09:55 AM » |
|
I agree, fresh install is the best option.
You can remove root user from screen but that won't prevent her from login as root, education is better and I think she just got the first lesson.
|
|
|
|
|
Logged
|
Linux User #330412 PCLinuxOS e17 Club Member
When life hands you lemons... add a little salt and Tequila
|
|
|
|
Leiche
|
 |
« Reply #13 on: January 22, 2012, 10:52:39 AM » |
|
I agree, fresh install is the best option.
You can remove root user from screen but that won't prevent her from login as root, education is better and I think she just got the first lesson.
okay, you are right 
|
|
|
|
|
Logged
|
|
|
|
|
stealth
|
 |
« Reply #14 on: January 22, 2012, 11:57:37 AM » |
|
Yep all of you are confirming what I thought.
|
|
|
|
|
Logged
|
|
|
|
|