jetlib.sec » BackTrack Linux Forums » BackTrack 5 Non-root user

Feeds

132763 items (0 unread) in 27 feeds

• 1337day (was: Inj3ct0r, 1337db)
• OSVDB Vulnerabilities
• Exploit-DB
• SecurityFocus Vulnerabilities
• Bugtraq
• Full Disclosure
• XSSed
• Packet Storm Security Headlines
• Packet Storm Security Advisories
• Packet Storm Security Exploits
• Packet Storm Security Recent Files
• Packet Storm Security Tools
• Packet Storm Security Misc. Files
• Sophos security news
• Sophos product advisories
• Penetration Testing
• SecuriTeam
• BackTrack Linux Forums
• Threatpost
• SecDocs
• carnal0wnage.attackresearch.com
• Carnal0wnage
• Kernel Fun
• Darknet
• The Exploitant
• Hack a Day
• Wirevolution

BackTrack Linux Forums

• October 12, 2011
• 

  BackTrack 5 Non-root user

  Posted: October 12th, 2011, 7:31am PDT by YesNoOk

  Tags:   

  I know root is the only account that's officially supported; however in some circumstances using named accounts might be helpful. A friend of mine had a situation where his company has a server they use for pen testing and the have a couple of testers. They wanted the logging to reflect their usernames vs. the shared root account. Using the following article, I helped them to get it working, but there were some changes necessary to get X started. Note that if you attempt this, you'll need to use sudo for most things you do. Aside from a few minor errors, I haven't found anything that doesn't work. TIFWIW. All of my testing was done with BT5 R1 64bit KDE.
  
  http://www.backtrack-linux.org/forum...cktrack-3.html
  
  Read the above first for specifics, then below is what I did that worked for me...
  
  Most of the commands below you'll run as the root account. You'll then switch to your new user account mid way through.
  
  Copy various configuration files to the /etc/skel directory
  
  Code: cp /root/.<folder name> /etc/skel The following folders are what I copied
  
  Code: .bash_logout
 .bashrc
 .config
 .gconf
 .gconfd
 .gem
 .kde
 .mozilla
 .msf4
 .profile
 .pulse
 .subversion
 .wine
 .xine Create your new user:
  
  Code: adduser <username> Add user to groups:
  Code: usermod --groups admin,disk,cdrom,audio <username> Login as the new user to console
  
  Allow user to start their x session (if you fail to do the command below and attempt to start X as your new user, you will get a black screen):
  
  Code: sudo chown <user>:<user> /home/<username>/Desktop/.Xauthority allow user to make KDE changes:
  
  Code: sudo chown <user>:<user> /home/<username>/.kde/share/config/kmixrc
sudo chown <user>:<user> /home/<username>/.kde/share/config/kmixctrlrc At this point you should be able to startx and get the normal BT5 environment.
  
  Hope this helps anyone else who's in a similar situation.