Turist

From CSLabsWiki
Jump to: navigation, search
Turist
IP Address(es): 128.153.145.214
Contact Person: Jared Dunbar
Last Update: March 2016
VM Host (Physical): hydra
Host VM: Turist


Hostname: http://turist.cslabs.clarkson.edu
Operating system: Debian
LDAP Support: No
Development Status: Completed
Status: Running


Turist is for alumni who want to share files and other fun stuff, be able to vpn into COSI, etc.

The SSH daemon runs on Clarkson's zip code

Current Users

Username Real Name
alan Alan Beadle
cmesh Christian Mesh
grissess Graham Northup
roddonfire Amanda Horne

Getting an account

Submit your SSH keys and preferred username to dunbarj@clarkson.edu

Uses

Acceptable use of the VM would be as follows:

  • sharing files (not illegal stuff plz) (hint - use /tmp)
  • as your personal IRC bouncer
  • chatting via write (or wall?)

Applications

Some useful stuff on there:

  • irssi - IRC client (among others)
  • weechat - IRC client
  • screen - Multitasking
  • tmux - Multitasking

Policies

Violating these following terms can permanently terminate your use of the VM

Aside from the normal morals of using someone else's machine:

  • Don't distribute your private key. Only you are allowed to log into the server.
  • Don't fill up the disk, and if you do then it's your job to pester the other users to clean their shit
  • Don't fool with network resources (ever), incl. attacking internal COSI services
  • Don't perform DoS attacks
  • Don't download large files at ridiculous speeds (baring we get a software limit on the speed of the network interface of the vm)

Administrative Stuff

Adding a User

Add the user

adduser <username>

Come up with some password and then forget it (it's not necessary to remember, the user can set it but it does nothing since you can't ssh over password (only public key) and there's no sudo for users.

Add their SSH public key

Log in as root, and make a file at /etc/ssh/authorized_keys/<username>

Edit that file to contain their public key, and then profit. (contact the alumnus)

(hint: if you're in console but have access to their ssh public key over the network, do this:)

ssh <you>@<your-machine> "cat <theirkey>" > afile

Then copy "afile" to the auth keys folder as root and check permissions.

The authorized_keys folder nor the username file should be editable by anyone besides root for security reasons.