CSC Machine Policy Summary, 15 February 1995

# Notes

Policies for group accounts and administrative accounts are not yet available (this section will contain links to them when they do become available). This is a brief (instead of legalese) version of the usage policy. Everyone who receives an account on one of the CSC machines must sign the agreement based on the usage policy, and this summary lists the things that the users will agree to.

# Summary

### Use of accounts:

- one person only
- for hacking or course work, not for cracking
- if you're not working on a specially authorized project, don't abuse system resources
- don't abuse other users, either

### Security:

- again, don't crack
- your .rhosts file should only contain your user IDs on CSC and MFCF machines
- don't use passwords that you use elsewhere, and never

  tell anyone your password
- be secure!
- if you find security holes, report them to the sysadmin but don't blab or try to take advantage of them

### The Systems Committee may:

- Examine programs that seem to be violating policy or security; this includes the following when necessary

  - watching what the program does
  - looking at the executable and source
  - looking at files that the program seems to be using
  (you will be informed if any of this happens)
- Remove accounts with an explanation but no notice (especially if the user is violating the machine policy)

### General:

- you are completely responsible for your actions
- don't do illegal, damaging, or unethical things
- the exec can change their policies with reasonable notice
- CSC machines will not be up at all times, and may even crash while you are using them
- if CSC machines cause you to lose time, data, sleep or your SO, then it's your own tough luck