How to (Extra) Ban Someone: Difference between revisions

From CSCWiki
Jump to navigation Jump to search
Line 24: Line 24:
=== Step 4: Remove all Their Resources ===
=== Step 4: Remove all Their Resources ===


* '''<u>Remove their CSC Cloud VMs</u>''': https://wiki.csclub.uwaterloo.ca/CloudStack#Administration - (optional) Kill all processes they are running in General Use
* '''<u>Remove their CSC Cloud VMs</u>''': https://wiki.csclub.uwaterloo.ca/CloudStack#Administration
* (optional) Kill all processes they are running in General Use
* (optional) Delete their home directory (eg. `/users/f3hadi` 🥲)
* (optional) Delete their home directory (eg. `/users/f3hadi` 🥲)

Revision as of 11:20, 18 September 2023

Ahem, so in recent times, we had to disable/ban a CSC user's account for their repeated attempts to circumvent their ban in MathSoc/CSC (FR, totally no pun intended)...

This is a (hopefully comprehensive) guide on ensuring their existing account (based on their WATIAM) is put out of action for good, and immediately. This guide is mainly intended for Syscom as it requires root or admin access to many CSC services.

Step 1: Remove Membership

Through CEO's TUI (`ceo`) and LDAP (guide from Raymond):

  • Remove All Membership Terms: look for `memberTerm` in `ldapvi`
  • Reset their password (**and don't tell them!**)

Step 2: Screw Up Their Account

  • Change their Login Shell (through LDAP) to something like `/sbin/nologin` or `/bin/false`

NOTE: CEO will not allow this change, so LDAP is best (and likely only way)

Step 3: Deauth Them Everywhere

Step 4: Remove all Their Resources