Root privilege - Revision history

Ninereasons: common misspelling

2006-05-23T23:24:14Z

common misspelling

Simon at 18:32, 17 January 2005

2005-01-17T18:32:15Z

Jimbo at 04:31, 24 December 2004

2004-12-24T04:31:11Z

Dave: stub article -- needs work

2004-12-22T23:48:13Z

stub article -- needs work

New page

This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.

@@ Line 1: / Line 1: @@
-This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.
+This is a separate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.
 Denying the right to use [[su]], and therefore unlimited root privilege, from a regular user account is more secure for work that doesn't need root privileges in unpredictable ways; root can make scripts for that user to still be able to do predictabled root-privilege tasks as needed. Root is harder to hack that way if that user is compromised by a hacker or malware - assuming the simple user isn't permitted to edit the scripts, which is a common novice oversight.
 [[Category:FreeBSD Terminology]]

← Older revision		Revision as of 18:32, 17 January 2005
Line 1:		Line 1:
	This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.		This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.
		+
		+	Denying the right to use [[su]], and therefore unlimited root privilege, from a regular user account is more secure for work that doesn't need root privileges in unpredictable ways; root can make scripts for that user to still be able to do predictabled root-privilege tasks as needed. Root is harder to hack that way if that user is compromised by a hacker or malware - assuming the simple user isn't permitted to edit the scripts, which is a common novice oversight.
		+
	[[Category:FreeBSD Terminology]]		[[Category:FreeBSD Terminology]]

← Older revision		Revision as of 04:31, 24 December 2004
Line 1:		Line 1:
	This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.		This is a seperate entry because -- surprise -- you don't have to be [[root]] to run programs (or for [[daemons]] to run themselves) as root in order to have root privilege. Any daemon, user or group that has a [[uid]] or [[gid]] of 0 runs as [[root]] effectively. So anyone that hijacks an account that has a root uid is effectively root. Which is why it's a good idea to run as few programs as possible that do that.
		+	[[Category:FreeBSD Terminology]]