|
Size: 1348
Comment:
|
Size: 2020
Comment: Overhaul
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == How to log in to mire without typing your password | #pragma section-numbers off |
| Line 3: | Line 3: |
| Zeroth, you must have openssh client 4.3 or later. Other versions may work, but we make no guarantees. | This page explains how to log in to our servers without having to type in a 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. | [[TableOfContents]] |
| Line 7: | Line 7: |
| Then, you must obtain kerberos tickets. If your username is "fred", you would do this by typing | = Prerequisites = |
| Line 9: | Line 9: |
| kinit fred@HCOOP.NET | You must have openssh client 4.3 or later. Other versions may work, but we make no guarantees. You will also want the {{{krb5-user}}} package if you are using Debian or Ubuntu. For further details, check out [MemberManual/TransferringFiles/OpenAFS], and follow just the Kerberos instructions. |
| Line 11: | Line 11: |
| Then type your password. | = Instructions = Once a Kerberos client hsa been installed, 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. |
| Line 15: | Line 23: |
| klist | {{{ klist }}} |
| Line 19: | Line 29: |
| Last, depending on what version of ssh you have, type | Last, type |
| Line 21: | Line 31: |
| ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' mire.hcoop.net | {{{ ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' fred@mire.hcoop.net }}} |
| Line 23: | Line 35: |
| 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. | (GSSAPI is sort of like Kerberos. Don't worry about the difference at this point.) |
| Line 25: | Line 37: |
| 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 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. = Automating things = 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). Here is an example entry for `~/.ssh/config`: {{{ Host mire.hcoop.net GSSAPIAuthentication yes GSSAPIDelegateCredentials yes User fred }}} This will allow you to type the following, instead of the longer command above. {{{ ssh fred@mire.hcoop.net }}} = If it doesn't work = See the [:MemberManual/ShellAccess/TroubleshootingKerberos:Troubleshooting Kerberos] page if you run into any problems. |
This page explains how to log in to our servers without having to type in a password.
Prerequisites
You must have openssh client 4.3 or later. Other versions may work, but we make no guarantees. You will also want the krb5-user package if you are using Debian or Ubuntu. For further details, check out [MemberManual/TransferringFiles/OpenAFS], and follow just the Kerberos instructions.
Instructions
Once a Kerberos client hsa been installed, 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, type
ssh -o 'GSSAPIAuthentication yes' -o 'GSSAPIDelegateCredentials yes' fred@mire.hcoop.net
(GSSAPI is sort of like Kerberos. Don't worry about the difference at this point.)
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.
Automating things
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).
Here is an example entry for ~/.ssh/config:
Host mire.hcoop.net GSSAPIAuthentication yes GSSAPIDelegateCredentials yes User fred
This will allow you to type the following, instead of the longer command above.
ssh fred@mire.hcoop.net
If it doesn't work
See the [:MemberManual/ShellAccess/TroubleshootingKerberos:Troubleshooting Kerberos] page if you run into any problems.