Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 Getting an account

It's a 2 step process.

  1. You have to be registered as a SLAC user. To do this go to https://www-sslonly.slac.stanford.edu/slacuserinfo/SLACformI.aspImage Added
    • You are NOT a SLAC employee, use your home institution as your employer.
    • Your work type is computing. SLAC will not be paying you. You will be using SLAC computing resources.
    • The experiment is Computing. I am your sponsor. Your SLAC group department is
    • SCCS. You will spend < 10% time at SLAC. Please be careful to
    • use the recommended  date format dd-mon-yyyy.T
    • this will get you a SLAC ID. It may take a couple work days.
  2. Once you have a SLAC ID then you will be able to apply for a SLAC computer account.  For this you will need to go to http://www2.slac.stanford.edu/comp/slacwide/account/account.htmlImage Added Fill out this form, sign it, and FAX it to the attention of Les Cottrell at +1-650-926-3329.

Unix/NFS group iepm 

File used to keep track of network group privs. It use the ypgroup Unix databases

...

Code Block
ssh-keygen -t dsassh-keygen -t rsassh-keygen -t rsa1 rsa1

 It will also ask you for a pass phrase, just enter a carriage return. If it asks where to save the keys just take the default (carriage return).  Another used can verify that the public keys are created as follows:

Code Block
3cottrell@pinger:~>more ~tanzeel/.ssh/.public/identity.pub
       10241024 35 146653454394770889044623166877077310614501899921965775234647207308036879
       6375041385200908053973712675241260108885683770799723142981802623462013796428518963750413852009080539737126752412601088856837707997231429818026234620137964285189
       9091613921724725246555463586808086359559849967741053332149176216302700706949189190916139217247252465554635868080863595598499677410533321491762163027007069491891
       4340587378551870388396825934486942920897192759972273669042211270900673586735743405873785518703883968259344869429208971927599722736690422112709006735867357 ta
       nzeel@iepmnzeel@iepm-bw

Someone who can already logon to account iepm will then need to copy the new person's (in the example above tanzeel) public keys into ~iepm/.ssh/.public/authorized_keys:

Code Block
2iepm@iepm-bw:~>cat ~tanzeel/.ssh/identity.pub >> ~/.ssh/authorized_keys
3iepm@iepm-bw:~>cat ~tanzeel/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
4iepm@iepm-bw:~>cat ~tanzeel/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
5iepm@iepm-bw:~>cat ~tanzeel/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys2 keys2

 One can then check that the new person's public ssh keys are available in the iepm account as follows:

Code Block
    9iepm@iepm-bw:~>tail -3 ~/.ssh/authorized_keys
       10241024 35 146653454394770889044623166877077310614501899921965775234647207308036879637504138520
       0908053973712675241260108885683770799723142981802623462013796428518990916139217247252465554609080539737126752412601088856837707997231429818026234620137964285189909161392172472524655546
       3586808086359559849967741053332149176216302700706949189143405873785518703883968259344869429235868080863595598499677410533321491762163027007069491891434058737855187038839682593448694292
       0897192759972273669042211270900673586735708971927599722736690422112709006735867357 tanzeel@iepm-bw
       sshssh-dss AAAAB3NzaC1kc3MAAACBAIEC24o7qaGXu7BhvDEyVLfbtNCyHDqsW5N7urvW2DLKam7MMyZmnAqpQh1X7j8L
       UU+DAy6eX50ToychvrwDA8pmA45Hbf61dnoSc/yfd1sM8fC1x0faWvglf/PNT5EfQzwPKEEzIeTieNRL9OTNr4ZS7WjXJ
       +i+bvc/a6bq+6Rj1AAAAFQCWTL/9FG3xCJ3nKwRg/g5cduZ9BwAAAIA8N63JWBa+xr2I4ylDaaONQNfVP9ODNMvtSBSj
       OlEK7YD4oDdOlEK7YD4oDd/ZZPLEdW+mcHGTbEgwBB15acl+4PdpGBy5HCGsA7xXJPEPGnjNHRcsfRCdAuyQiaUKfJLfPPvdAAlKxO+
       DGJCItlsE8hyfDGJCItlsE8hyf+vbDJGxoa4nOqm2aQ6XneXhWhJuwAAAAIAXJMhOKrGAYBn72q+IbwM2c33bXLDnTTlGo7WKlzeBpLas
       jnt79E10TZEX6h0WDYuK0Ymdjy8XEoaStpFjnt79E10TZEX6h0WDYuK0Ymdjy8XEoaStpF/bH+TxXclLNCAhjeWVf/FJI1neDhvhfrLHV3rOVEgH+d9Wka7Q+e2RPYY
       8WJOx8WJOx/eh7vW21LwqmnfLK/h0lyxJ3/EX9w== tanzeel@iepm-bw
       sshssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA4uzuhQTykqyFHpEayNxTz0HC951ynsxxT2ltHXzjdTbudozvtXEnCYGe
       hXVoog4wS2yhwXskRZj8mKyoahXVoog4wS2yhwXskRZj8mKyoa/ZtPOd2fXZgQs+zJB5SrDN7jf2aWt5A1a2VynVAFPor4Vu/Yh79dAkj3zN3ojcoelqt
       wFheKhmPRh1cxNIpNyPmelEwFheKhmPRh1cxNIpNyPmelE= tanzeel@iepm-bw

and the new user should be able to logon to the iepm account using:

Code Block
   ~tanzeel@iepm-bw.slac.stanford.edu>ssh -v iepm@iepm-bw.slac.stanford.edu if that does not work then try:
       ~tanzeel@iepm-bw.slac.stanford.edu>ssh -v -1 iepm@iepm-bw.slac.stanford.edu
and
       ~tanzeel@iepm-bw.slac.stanford.edu>ssh -v -2 iepm@iepm-bw.slac.stanford.edu  

Sudo

The sudoers file can be found at:

...