SystemAdministration/GroupPermissions - Revision history

Xlefay: /* Checking Permissions */

2014-03-29T18:26:45Z

Checking Permissions

← Older revision		Revision as of 18:26, 29 March 2014
Line 9:		Line 9:
	</pre>		</pre>

	Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups		Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups.

	If you feel, you should have access to a machine you don't currently have, discuss the matter with your team leader, they can then request access the matter with a member of the Sysops team. The decision however, falls entirely in the hands of the Sysops group.

	== List of Groups ==		== List of Groups ==

Xlefay at 18:26, 29 March 2014

2014-03-29T18:26:27Z

← Older revision		Revision as of 18:26, 29 March 2014
Line 10:		Line 10:

	Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups		Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups

			If you feel, you should have access to a machine you don't currently have, discuss the matter with your team leader, they can then request access the matter with a member of the Sysops team. The decision however, falls entirely in the hands of the Sysops group.

	== List of Groups ==		== List of Groups ==

FunPika: added Category:System administration using HotCat

2014-03-22T17:43:33Z

added Category:System administration using HotCat

← Older revision		Revision as of 17:43, 22 March 2014
Line 31:		Line 31:
	\|-		\|-
	\|}		\|}

			[[Category:System administration]]

NCommander at 17:29, 22 March 2014

2014-03-22T17:29:44Z

← Older revision		Revision as of 17:29, 22 March 2014
Line 2:		Line 2:

	== Checking Permissions ==		== Checking Permissions ==
	From any node, you can run 'id' on ~~yourself~~ to see what permissions you or anyone else has		From any node, you can run 'id' on a user to see what permissions you or anyone else has

	<pre>		<pre>
Line 11:		Line 11:
	Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups		Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, not roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups

			== List of Groups ==
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-

NCommander at 17:24, 22 March 2014

2014-03-22T17:24:49Z

← Older revision		Revision as of 17:24, 22 March 2014
Line 1:		Line 1:
	~~[[SystemAdministration]] - parent~~

	Access to machines are controlled by the POSIX groups you're present in LDAP. This page acts as a quick reference guide to see what you can do with what permissions.		Access to machines are controlled by the POSIX groups you're present in LDAP. This page acts as a quick reference guide to see what you can do with what permissions.

NCommander: NCommander moved page GroupPermissions to SystemAdministration/GroupPermissions

2014-03-22T17:01:09Z

NCommander moved page GroupPermissions to SystemAdministration/GroupPermissions

← Older revision	Revision as of 17:01, 22 March 2014
(No difference)

NCommander: Created page with "SystemAdministration - parent Access to machines are controlled by the POSIX groups you're present in LDAP. This page acts as a quick reference guide to see what you can ..."

2014-03-22T16:59:32Z

Created page with "SystemAdministration - parent Access to machines are controlled by the POSIX groups you're present in LDAP. This page acts as a quick reference guide to see what you can ..."

New page

[[SystemAdministration]] - parent

Access to machines are controlled by the POSIX groups you're present in LDAP. This page acts as a quick reference guide to see what you can do with what permissions.

== Checking Permissions ==
From any node, you can run 'id' on yourself to see what permissions you or anyone else has

<pre>
mcasadevall@soylent-db:~$ id mcasadevall
uid=2500(mcasadevall) gid=2500(firefighters) groups=2501(sysops),2500(firefighters),2502(db)
</pre>

Here's our breakdown of permissions that can access what. Please note this refers to physical access permissions, *not* roles in teams. We try and practice least amount of access necessary in an attempt to keep things relatively secure. You can be in multiple groups

{| class="wikitable"
|-
! Group Name !! Is What !! Can Access
|-
| firefighters || all staff || firefighters can access the shell box, used to springboard to other nodes
|-
| db || database administrators || db users can access production databases, and sudo to the db user. They can *not* sudo to root
|-
| dev_team || slashcode develoeprs || can access dev nodes, can sudo to root on dev nodes
|-
| ircops || IRC administrators || access to IRC hosting nodes, can sudo to root on irc boxes
|-
| prod_access || people trusted to pushout on production || can access all production nodes as well as edge nodes, can sudo to the slash account. No root privelleges
|-
| svcadmin || admins of misc svcs box || shell access to all services nodes (outdated?), can sudo to root on svc nodes.
|-
| sysops || users with global root || sysops can sudo to root on all nodes, as well as access any node that we run. Users in this group also have access to the Linode master panel
|-
|}