|
Size: 1348
Comment:
|
Size: 1525
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == How to log in to mire without typing your password | == How to log in to mire without typing your password == |
| Line 5: | Line 5: |
| First, you must make sure that your krb5.conf (or, on MacOS, your edu.mit.Kerberos file) is sane. All you need to do is make sure that there are NOT entries in there which disable the dns_lookup_kdc or dns_lookup_realm options (unfortunately I think Fedora ships with these crippled). If you don't see those options in the file, you're fine. | First, you must make sure that your `/etc/krb5.conf` (or, on MacOS, your `/Library/Preferences/edu.mit.Kerberos` file) is sane. All you need to do is make sure that there are NOT entries in there which disable the `dns_lookup_kdc` or `dns_lookup_realm` options (unfortunately Fedora ships with these crippled). If you don't see those options in the file, you're fine. |
| Line 8: | Line 8: |
| {{{ kinit fred@HCOOP.NET }}} |
|
| Line 9: | Line 12: |
| kinit fred@HCOOP.NET Then type your password. |
Then type your password when prompted. Note that you MUST capitalize HCOOP.NET and you MUST NOT capitalize your user name. This is important. |
| Line 14: | Line 15: |
| {{{ | |
| Line 16: | Line 17: |
| }}} | |
| Line 20: | Line 21: |
| {{{ ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' mire.hcoop.net }}} If that doesn't work, add "`-vvv`" to the command line and copy and paste the ENTIRE output into an email to hcoop-discuss and we'll tell you what's up. |
|
| Line 21: | Line 26: |
| ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' mire.hcoop.net If that doesn't work, add "-vvv" to the command line and copy and paste the ENTIRE output into an email to hcoop-discuss and we'll tell you what's up. If you do this a lot, you can include the GSSAPIAuthentication and GSSAPIDelegateCredentials options in your .ssh/config file. But you should NOT turn on GSSAPIDelegateCredentials for arbitrary hosts (make sure you only enable it for HCOOP hosts). |
If you do this a lot, you can include the `GSSAPIAuthentication` and `GSSAPIDelegateCredentials` options in your `.ssh/config` file. But you should NOT turn on `GSSAPIDelegateCredentials` for arbitrary hosts (make sure you only enable it for HCOOP hosts). |
How to log in to mire without typing your password
Zeroth, you must have openssh client 4.3 or later. Other versions may work, but we make no guarantees.
First, you must make sure that your /etc/krb5.conf (or, on MacOS, your /Library/Preferences/edu.mit.Kerberos file) is sane. All you need to do is make sure that there are NOT entries in there which disable the dns_lookup_kdc or dns_lookup_realm options (unfortunately Fedora ships with these crippled). If you don't see those options in the file, you're fine.
Then, you must obtain kerberos tickets. If your username is "fred", you would do this by typing
kinit fred@HCOOP.NET
Then type your password when prompted. Note that you MUST capitalize HCOOP.NET and you MUST NOT capitalize your user name. This is important.
Next, make sure you have your tickets. To do this, type
klist
You should see your tickets and their expiration dates.
Last, depending on what version of ssh you have, type
ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' mire.hcoop.net
If that doesn't work, add "-vvv" to the command line and copy and paste the ENTIRE output into an email to hcoop-discuss and we'll tell you what's up.
If you do this a lot, you can include the GSSAPIAuthentication and GSSAPIDelegateCredentials options in your .ssh/config file. But you should NOT turn on GSSAPIDelegateCredentials for arbitrary hosts (make sure you only enable it for HCOOP hosts).