We got it fixed. I asked a co-worker for advice. I think he worked out that I was using the wrong key. Though how I came to have more then one nearby I'll never quite understand. I think I'm about 70-80% on his troubleshooting process. I'd like to be stronger, but for right now I'm just glad it works.<br>
<br>Thanks to all Clue-bies for their suggestions!<br><br>Bean<br><br><div class="gmail_quote">On Wed, Sep 12, 2012 at 11:43 AM, Mike Bean <span dir="ltr"><<a href="mailto:beandaemon@gmail.com" target="_blank">beandaemon@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The plot thickens! <br><br>Apparently even my normal/regular login<br><br>ssh -i (path to my cert) -l (mylogin) [destination IP]<br>
<br>has been generating the same error, I didn't know about it because I didn't have -v<br>
<br>debug1: Authentications that can continue: publickey,gssapi-with-mic,password<br>debug1: Next authentication method: gssapi-with-mic<br>debug1: Unspecified GSS failure. Minor code may provide more information<br>Credentials cache file '/tmp/krb5cc_0' not found<br>
<br>debug1: Unspecified GSS failure. Minor code may provide more information<br>Credentials cache file '/tmp/krb5cc_0' not found<br><br>debug1: Unspecified GSS failure. Minor code may provide more information<br>
<br><br>debug1: Unspecified GSS failure. Minor code may provide more information<br>Credentials cache file '/tmp/krb5cc_0' not found<br><br>checking perms on authorized_keys, and my ssh conffig <br><br>mbean@6M4S5R1 ~/.ssh $ ls -la<br>
total 20<br>drwx------ 2 mbean mbean 4096 Sep 12 11:32 .<br>drwxr-xr-x 43 mbean mbean 4096 Sep 12 08:58 ..<br>-rw-r--r-- 1 mbean mbean 963 Sep 12 11:32 authorized_keys<br>-rw-r--r-- 1 mbean mbean 442 Sep 12 11:02 known_hosts<br>
-rw-r--r-- 1 mbean mbean 32 Sep 12 11:14 ssh_config<br><br>No idea what sort of "credentials cache file" it's looking for.<br><br><div class="gmail_quote"><div class="im">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">David L. Anselmi</b> <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span><br>
Date: Sat, Sep 8, 2012 at 9:34 PM<br>Subject: Re: [clue] scp help?<br>To: CLUE's mailing list <<a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a>><br><br><br></div><div><div class="h5">
<div>Mike Bean wrote:<br>
><br>
> it's just sudo ssh -i (path to my cert) -l (mylogin) (some destination<br>
> server)<br>
<br>
</div>Why do you use sudo for this?<br>
<div><br>
> scp (some file) -i [path to my cert] mylogin:someserver (destination<br>
> directly on some server)<br>
<br>
</div>Could it be that if you don't use sudo some permissions are wrong?<br>
<br>
I don't particularly understand your specific problem but when I've seen this before it's due to<br>
configuration on the server side. Like the .ssh directory doesn't have the right permissions. So<br>
I've found my clues in the sshd log.<br>
<br>
Dave<br>
<div><div>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></div></div></div><br>
</blockquote></div><br>