Root Access

Users can grant themselves sudo access when the machine is first booted after installation. TIG can provide additional sudo access or the root password upon request. You can also add new sudoers files to the /etc/sudoers.d directory.

Root Alias

If you are reading this, its probably because you want to customize something on your machine install some extra software, set up a root cron job, add a local (non-Kerberos) account for a collaborator, or the like. If that is the case, you should arrange for yourself to get root mail. You can do this by creating a file /etc/facter/facts.d/local.txt and adding a line that says
root_alias=youremailaddress

That does not prevent TIG sysadmins from getting root mail as well, but it means you will see it too, and you can fix problems related to software you've installed or configuration changes you've made. (Of course, if you need help with that, send mail to help@csail.mit.edu.)

-- JaySekora - 10 Sep 2013

Restricting login access

Machine owners can limit access to their computers by providing a list (one per line) of allowed or denied usernames in /etc/csail/users.allow or /etc/csail/users.deny. Users listed in users.allow will be allowed at the exclusion of all other users. Usernames listed in users.deny will be denied, while all others will be allowed. Behavior is undefined if both files exist. This method is somewhat fragile, relying on our strang loccal method of populating /etc/password, it also means utilities like 'ls' won't be able to translate CSAIL user id numbers on shared filesystems (NFS and AFS) to usernames.

The currently prefered method is to restrict ssh access to a specific group or list of groups. This is done by adding a line to the file in /etc/facter/facts.d/local.txt (which may not yet exisist) defining sshdallowgroups to a space seperated list of groups to allow, for example:
sshdallowgroups=group1 group2 etc

This will be activated on the next configuration management run (within 30min) or can be activated immediately by running
sudo puppet agent -t

Access to NFS

Autofs is unconfigured by default. If you'd like to access the CSAIL NFS shares, add the following line to /etc/facter/facts.d/local.txt (which might not exist already):

autofs=true

You should be able to access the NFS shares in approximately 30 minutes after the next puppet agent runs.

-- StephenJahl - 06 Dec 2012
Topic revision: 15 Apr 2016, JaySekora
 

MIT Computer Science and Artificial Intelligence Laboratory

 

  • About CSAIL
  • Research
  • News + Events
  • Resources
  • People

This site is powered by Foswiki MIT: Massachusetts Institute of Technology