Sudo, configuring - Revision history

Dave at 04:56, 14 December 2005

2005-12-14T04:56:38Z

2005-10-16T11:47:22Z

2005-10-16T11:46:45Z

2004-09-15T13:30:47Z

2004-09-14T18:57:10Z

2004-09-14T16:20:00Z

Using Aliases to make life easier

2004-09-14T16:17:30Z

2004-09-14T13:02:08Z

2004-09-14T07:13:02Z

Using Aliases to make life easier

2004-09-14T07:11:46Z

Using Aliases to make life easier

← Older revision		Revision as of 04:56, 14 December 2005
Line 74:		Line 74:
	This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.		This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.

−	[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]]	+	[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]][[Category:Securing FreeBSD]]

@@ Line 35: / Line 35: @@
 Finally, if you just want to give yourself [[root]] access on your server via sudo with no password, your sudoers might look like:
   root ALL=ALL(ALL) ALL
-  convoy ALL=(ALL) NOPASSWD: ALL
+  yourself ALL=(ALL) NOPASSWD: ALL
 '''NOTE:''' remember that setting sudo rights for multiple machines in a single '''sudoers''' file is only meaningful if that file is actually shared or distributed across those multiple machines.  Simply writing permissions for the machine samizdata ''on'' the machine deus isn't going to do anything useful by itself. You would need to copy the file contents over to all the machines that are listed (and then [[kill]] -HUP the sudo process, if it's running,) in order to make the changes meaningful.

@@ Line 32: / Line 32: @@
   peet  ALL=deus(ALL) ALL
   light ALL=ALL(ALL) /sbin/shutdown
 '''NOTE:''' remember that setting sudo rights for multiple machines in a single '''sudoers''' file is only meaningful if that file is actually shared or distributed across those multiple machines.  Simply writing permissions for the machine samizdata ''on'' the machine deus isn't going to do anything useful by itself. You would need to copy the file contents over to all the machines that are listed (and then [[kill]] -HUP the sudo process, if it's running,) in order to make the changes meaningful.

← Older revision		Revision as of 13:30, 15 September 2004
Line 70:		Line 70:
	This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.		This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.

−	[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]	+	[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]]

← Older revision		Revision as of 18:57, 14 September 2004
Line 70:		Line 70:
	This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.		This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.

−	[[Category:System Commands]] [[Category:Ports and Packages]]	+	[[Category:System Commands]] [[Category:Ports and Packages]] [[Category:Configuring FreeBSD]

@@ Line 39: / Line 39: @@
 You can make groups within the sudoers file so that you don't have to type more than you need to. Follow this format:
-  User_Alias allows you to define a group of users
+  '''User_Alias''' allows you to define a group of users
-  Runas_Alias allows you to define the daemon or user the command can run as
+  '''Runas_Alias''' allows you to define the daemon or user the command can run as
-  Host_Alias allows you to define a group of hosts
+  '''Host_Alias''' allows you to define a group of hosts
-  Cmnd_Alias allows you to define which commands (full path '''must''' be given) are in a group
+  '''Cmnd_Alias''' allows you to define which commands (full path '''must''' be given) are in a group
   You ''can'' use already existing system groups, but you have to add the prefix % (e.g., %wheel)

@@ Line 64: / Line 64: @@
   DHCPADMINS DHCPSERVERS=(DAEMONS) DHCP
-and this would essentially give jimbo rights to do root-priviledge stuff with any server, as any daemon, but only using the commands that '''DNS''' and '''DHCP''' specify; peet would only get root access to NAMESERVERS, only run as the DAEMONS, and only use the commands in DNS. Light would only get root access to DHCPSERVERS, run as DAEMONS and only be able to run /usr/local/sbin/dhcpd.
+Note that there are no spaces between the users and commas, likewise, servers and commands only have a comma seperating them -- '''no spaces'''. This would essentially give jimbo rights to do root-priviledge stuff with any server, as any daemon, but only using the commands that '''DNS''' and '''DHCP''' specify; peet would only get root access to NAMESERVERS, only run as the DAEMONS, and only use the commands in DNS. Light would only get root access to DHCPSERVERS, run as DAEMONS and only be able to run /usr/local/sbin/dhcpd.
 This is ideal if you have a) a lot of servers and/or b) a lot of admins with specific functions, that don't need complete access to the machine, but do need some sort of administrative rights on it.
 [[Category:System Commands]] [[Category:Ports and Packages]]