OT: ssh between linux and sco unix

[Tom Aldridge]

On 12/11/2009 8:52 AM, Jose Lerebours wrote:
>
>
> On Fri, Dec 11, 2009 at 8:53 AM, Tom Aldridge <toma at aldridgeinc.com
> <mailto:toma at aldridgeinc.com>> wrote:
>
>     Mark replied:
>      >
>      > You forgot the critical part--leave the passphrase -empty- during key
>      > generation.  That's the part Jose needs. :)
>
>     There are so many examples of this process and they pretty much ALL say
>     that part, so I assumed he knew that. In fact, now that I just googled
>     "ssh/authorized_keys2" and it returned 75,400 results) I see there are
>     so many examples of this entire process I'm not sure why he brought it
>     to this list or why I responded.
>
>
> I was aware of it and I never used passphrase ...
>
> On my original post I included a link to one of those many hits and
> after having followed the steps, I still was not able to log in nor run
> a commands without providing a password.
>
>      >
>      >>> scp ~/.ssh/id_rsa.pub
>     username at machine.domain.com:.ssh/authorized_keys2
>      >
>      > Why are you using authorized_keys2?  RSA keys have always gone in
>      > authorized_keys.  I think authorized_keys2 may be meant for DSA keys,
>      > although I've honestly never even heard of the authorized_keys2
>     file before
>      > your email, and I've been using ssh for automation for...well a
>     very LONG
>      > time.  :)
>
>     Long time... me too. In fact, just the other night I set up a no
>     password ssh rsync backup for my daughter's windows box (cygwin) to a
>     web hosting's backup server and authorized_keys2 worked while
>     authorized_keys didn't. I've used one or the other depending on which
>     one took. I guess it's an ssh version thing... something I pointed out
>     to him that could be an issue between his linux and sco box.
>
>
> At this point, I am going to try you last suggestion to remove the
> trusted hosts and start over again.  I am inclined to pay for the
> service if one of you is willing to take it up and get this thing to
> work for me ...  Please let me know if interested!
>
> Regards,
>
>
> Jose
>

Jose,

Other than what I've given you, I'm not sure what else to look for. Did 
you try both authorized_keys and authorized_keys2? Did you make sure 
.ssh permissions are set correctly on both boxes? Did you check out what 
version of ssh is running on either box? You could try setting up a 
no-password ssh log in between two users on the same linux box or 
between two linux boxes, if you have those available. If you can get 
that to work, it's something with the SCO box.

Tom