Overview
The department maintains general-purpose machines called "courselab" (currently, two machines that each have 2 Intel Xeon E5 2670v3 processors and 128GB of DDR4 2133MHz memory) and "armlab" (currently, two machines that each have 2 ThunderX CP 48-core processors and 128GB of DDR4 2400MHz memory). These machines are accessible via SSH at courselab.cs.princeton.edu or at armlab.cs.princeton.edu using one's NetID and OIT password. The USB Boot only machines in FC 011 and FC 012 are dedicated for courses where students develop custom boot loaders (e.g., COS 318).
The remainder of this document describes the authorization and authentication process for the courselab and armlab machines.
Authorization
The list of COS courses that have requested use of these machines can be updated by a course instructor using the ADM site. We get periodic updates of the enrollment rosters from the Registrar for these COS courses, and these students are authorized to use these machines. Notes:
- There is a delay from when the student registers for the course and when we get the information and are able to act on it. This delay may range from a few hours up to a full day. If a student is adding the course and needs immediate access, the instructor should send a message to csstaff@cs.princeton.edu.
- Instructors/TAs are not automatically added to the access list. Course managers can use the adm.cs site to enable individual instructors.
All members of Princeton with a NetID have access to the courselab and armlab systems. Accounts on the courselab and armlab machines are removed at the end of the semester. If you would like to keep your files please make sure you copy your files off the lab machines before the end of the semester.
Authentication
Users must use their OIT LDAP NetID and password to login to the machines.
Configuration
On February 1, 2016, CS Department login hosts switched to using RSA type SSH host keys. Since that time, the SSH Host RSA Key Fingerprint for the above hosts is: e0:0e:98:45:c9:4f:11:8f:19:bc:47:d2:07:0e:7c:ff.
Some older SSH clients may display the new fingerprint as: xepon-kibyl-bogur-palik-zyvar-lesuc-rikof-zusab-hypib-volyh-muxux.
Newer SSH clients (OpenSSH 6.8 or later) will use the SHA256 fingerprint: SHA256:9yBBea9Z0ER6asvvtNf6fRXVra6LOQ3OVZLtYKVpNc8.