Women in Technology

Hear us Roar



Article:
  SSH on Mac OS X for Worry-Free Wireless
Subject:   SSH Problem with Instructions
Date:   2001-11-30 05:05:10
From:   ahinds
Response to: SSH Problem with Instructions

I too am having the same problem with automatic logins.


I followed the instructions to the letter. Here is part of my session transcript. Any help would be appreciated. Thanks!


---
[localhost:~/.ssh] ahinds% ssh -v xxx.com
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /etc/ssh_config
debug1: Seeding random number generator
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 501 geteuid 501 anon 1
debug1: Connecting to xxx.com [xxx.xx.xxx.xx] port 22.
debug1: restore_uid
debug1: restore_uid
debug1: Connection established.
debug1: identity file /Users/ahinds/.ssh/identity type -1
debug1: identity file /Users/ahinds/.ssh/id_rsa type -1
debug1: identity file /Users/ahinds/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9p2
debug1: match: OpenSSH_2.9p2 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_2.9p2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 125/256
debug1: bits set: 1049/2049
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'xxx.com' is known and matches the RSA host key.
debug1: Found key in /Users/ahinds/.ssh/known_hosts2:1
debug1: bits set: 1012/2049
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /Users/ahinds/.ssh/identity
debug1: try privkey: /Users/ahinds/.ssh/id_rsa
debug1: try pubkey: /Users/ahinds/.ssh/id_dsa
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is password
ahinds@xxx.com's password:

Full Threads Newest First

Showing messages 1 through 5 of 5.

  • SSH Problem with Instructions
    2001-12-31 06:52:52  cochella [View]

    Have you found a solution yet?

    Thanks,

    Chris
    • SSH Problem with Instructions
      2002-04-29 11:44:47  hanspoo [View]

      Somebody found a solution to this ?

      Maybe RPM's.

      Hans Poo
      • SSH Problem with Instructions
        2002-05-10 21:12:37  bdharring [View]

        After a frustrating (hugely) night, I have finally cracked it on my setup... this is a stupid error but you cannot have world permissions set on at least the authorized_keys* files, and possibly on the local ./ssh/identity|rsa|dsa pubkeys.
        easy way to test this- on the intended system to log into, add to sshd_conf file the option StrictMode no .
        if this fixes it (try both ssh -1 and ssh -2 in case you have either protocol setup screwed up), then you should only have to remove the world readable permission.
        Good luck with it... I'm still struggling with it, but this at least got it to work for protocol 1.
        • SSH Problem with Instructions
          2003-05-12 12:13:49  anonymous2 [View]

          FROM HOME WHILE LOGGED IN AS MYSELF 'craig', I GENERATE SOME KEY PAIR:

          ssh-keygen -t dsa

          THEN I BECOME ROOT AND COPY MY KEYS TO MY ROOT ACCOUNT ALSO

          su -
          cd /var/root/.ssh
          cp ~craig/.ssh/id* .

          THEN I TRY MY PORT FORWARDING TO WORK MAIL SERVER, I CHANGED THE HOST NAME

          sudo ssh -2 -L 25:localhost:25 craig@work.example.com

          THE RESULT:
          surprisingly it no longer requires me to enter my root password for PORT FORWARDING on a PRIVILEDGED PORT.

          is this a security violoation.
          it always asked me for my root password prior to even trying to do port forwarding.

          -craig
    • SSH Problem with Instructions
      2007-04-02 08:32:59  bglnelissen [View]

      i have had the same problems, it worried me the whole day, one way was doing ok, the other way was asking my password.

      But now it is fixed. My problem where the permissions of my home folder, .ssh folder and the content of the .ssh folder.
      I did a (i can be wrong, if so corrent me but i dont know the default permissions of the home folder so i took 755)

      change the rights of EVERY file in my homefolder, this is done with the -R flag. It might be nicer if you dont use it at all and type (chmod 755 /Users/USERNAME/)
      $ chmod -R 755 /Users/USERNAME/

      change the permissions of the .ssh folder
      < code >$ chmod 700 ~/.ssh

      change the permissions of the .ssh folders content
      < code >$ chmod 600 ~/.ssh/*

      good luck.