BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING - SSH

This is a discussion on BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING - SSH ; Hi, I spent about a week getting openssh to let me use public/private key auth. I read a lot also in this forum, but could not get any suffiecient answer to my problem. I can log in via passwd auth, ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

  1. BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Hi, I spent about a week getting openssh to let me use public/private
    key auth.
    I read a lot also in this forum, but could not get any suffiecient
    answer to my problem.

    I can log in via passwd auth, thats no problem. (Just created a new xp
    user and give em a password! thats it!)

    But because passwd auth is no way secure, I want PPK auth.
    when I try to use public private key auth. ssh gives me this:

    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug2: dh_gen_key: priv key bits set: 118/256
    debug2: bits set: 503/1024
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug3: check_host_in_hostfile: filename /home/user/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 1
    debug3: check_host_in_hostfile: filename /home/user/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 1
    debug1: Host 'laptoper' is known and matches the RSA host key.
    debug1: Found key in /home/user/.ssh/known_hosts:1
    debug2: bits set: 501/1024
    debug1: ssh_rsa_verify: signature correct
    debug2: kex_derive_keys
    debug2: set_newkeys: mode 1
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug2: set_newkeys: mode 0
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug2: service_accept: ssh-userauth
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug2: key: /home/user/.ssh/identity (0x0)
    debug2: key: /home/user/.ssh/id_rsa (0x100e9778)
    debug2: key: /home/user/.ssh/id_dsa (0x0)
    debug3: input_userauth_banner

    ****USAGE WARNING****
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug3: start over, passed a different list
    publickey,password,keyboard-interact
    ive
    debug3: preferred publickey
    debug3: authmethod_lookup publickey
    debug3: remaining preferred:
    debug3: authmethod_is_enabled publickey
    debug1: Next authentication method: publickey
    debug1: Trying private key: /home/user/.ssh/identity
    debug1: PEM_read_PrivateKey failed
    debug1: read PEM private key done: type
    Enter passphrase for key '/home/user/.ssh/identity':
    debug1: read PEM private key done: type RSA
    debug3: sign_and_send_pubkey
    debug2: we sent a publickey packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug1: Offering public key: /home/user/.ssh/id_rsa
    debug3: send_pubkey_test
    debug2: we sent a publickey packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug1: Trying private key: /home/user/.ssh/id_dsa
    debug3: no such identity: /home/user/.ssh/id_dsa
    debug2: we did not send a packet, disable method
    debug1: No more authentication methods to try.
    Permission denied (publickey,password,keyboard-interactive).

    I THINK SOMETHING MUST BE WRONG AFTER:
    debug2: we sent a publickey packet, wait for reply
    BECAUSE THERE IS NO ANSWER!?
    WHAT DO I DO WRONG!?

    THANKS FOR HELPING!


  2. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    I should add: 192.168.0.11 is the client (desktoper)
    192.168.0.18 is the server (laptoper)
    when i go
    Run -> compmgmt.msc ->
    And check the protocoll I ses a:
    "PID 3424 : Connection closed by 192.168.0.11."

    Aint it strange that the client suddenly terminates the connection!?


  3. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Is the client prompting for the private key's passphrase? If using an
    agent, have you cached the private key?

    BTW password authentication is not insecure as long as you pick a good
    password. Unlike telnet, ssh never sends a password in plain text. Use
    upper and lower case, numbers and special characters, no words in the
    dictionary. For example: mY1sTp@55w0rd.

  4. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Thanks for the help!
    Yes I am asked for a passphrase... and it seems to be okay.

    okay here is a step-by-step description of how i tried to set up ssh:

    1. set path
    PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\Sys tem32\Wbem;C:\Programme\CE
    Software\QuicKeys;C:\Programme\OpenSSH\bin
    so commands are found

    2. Start -> Run -> compmgmt.msc
    create new user called user password user

    3. add user to passwd
    mkpasswd -l -u user >> C:\Programme\OpenSSH\etc\passwd

    4. make group file
    mkgroup -l >> C:\Programme\OpenSSH\etc\group

    5. generate key on client system
    ssh-keygen -b 1536 -t rsa -C "rsa key for user on client"

    than i have two files in /documents and settings/user/id_rsa (private
    key) and /documents and settings/user/id_rsa.pub (public key)

    6. than i am renaming
    id_rsa(private key)-> identity
    id_rsa.pub(public key)-> id_rsa

    otherwise, openssh will not ask me for a passphrase, don't ask me why.

    7.i add the public key of "user on client" via notepad copy & paste
    to C:\Dokumente und Einstellungen\user\.ssh\authorized_keys2
    on the server
    (authorized_keys2 because i want to use RSA2)

    8. now i could set the access rights of /user/.ssh to only allow user
    access this directory via windows cacls command:

    Allow: cacls .ssh /t /g user:f

    Dissalow: cacls .ssh /d gast:n
    Dissalow: cacls .ssh /d administrator:n
    Dissalow: cacls .ssh /d everybody

    9. i try to log in using this command line on the client:

    ssh -v -v -v -o PreferredAuthentications=publickey laptoper
    -verbose (more info)
    -option PreferredAuthentications=publickey

    and get:













    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    D:\Dokumente und Einstellungen\user>ssh-keygen -b 1536 -t rsa -C "rsa
    key for us
    er on client"
    Generating public/private rsa key pair.
    Enter file in which to save the key (/home/user/.ssh/id_rsa):
    /home/user/.ssh/id_rsa already exists.
    Overwrite (y/n)? y
    Enter passphrase (empty for no passphrase):
    Enter same passphrase again:
    Your identification has been saved in /home/user/.ssh/id_rsa.
    Your public key has been saved in /home/user/.ssh/id_rsa.pub.
    The key fingerprint is:
    58:81:54:4f:cf:c1:20:24:04:12:a1:b0:50:ed:80:d8 rsa key for user on
    client

    D:\Dokumente und Einstellungen\user>ssh -v -v -v -o
    PreferredAuthentications=pub
    lickey laptoper
    OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
    debug1: Reading configuration data /etc/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to laptoper [192.168.0.18] port 22.
    debug1: Connection established.
    debug3: Not a RSA1 key file /home/user/.ssh/identity.
    debug2: key_type_from_name: unknown key type '-----BEGIN'
    debug3: key_read: missing keytype
    debug2: key_type_from_name: unknown key type 'Proc-Type:'
    debug3: key_read: missing keytype
    debug2: key_type_from_name: unknown key type 'DEK-Info:'
    debug3: key_read: missing keytype
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug2: key_type_from_name: unknown key type '-----END'
    debug3: key_read: missing keytype
    debug1: identity file /home/user/.ssh/identity type -1
    debug3: Not a RSA1 key file /home/user/.ssh/id_rsa.
    debug1: identity file /home/user/.ssh/id_rsa type 1
    debug1: identity file /home/user/.ssh/id_dsa type -1
    debug1: Remote protocol version 2.0, remote software version
    OpenSSH_3.8.1p1
    debug1: match: OpenSSH_3.8.1p1 pat OpenSSH*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug2: kex_parse_kexinit:
    diffie-hellman-group-exchange-sha1,diffie-hellman-gro
    up1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
    aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-c
    tr
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
    aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-c
    tr
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@open
    ssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@open
    ssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: kex_parse_kexinit:
    diffie-hellman-group-exchange-sha1,diffie-hellman-gro
    up1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
    aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-c
    tr
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
    aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-c
    tr
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@open
    ssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@open
    ssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: mac_init: found hmac-md5
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug2: mac_init: found hmac-md5
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug2: dh_gen_key: priv key bits set: 131/256
    debug2: bits set: 527/1024
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug3: check_host_in_hostfile: filename /home/user/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 1
    debug3: check_host_in_hostfile: filename /home/user/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 1
    debug1: Host 'laptoper' is known and matches the RSA host key.
    debug1: Found key in /home/user/.ssh/known_hosts:1
    debug2: bits set: 479/1024
    debug1: ssh_rsa_verify: signature correct
    debug2: kex_derive_keys
    debug2: set_newkeys: mode 1
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug2: set_newkeys: mode 0
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug2: service_accept: ssh-userauth
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug2: key: /home/user/.ssh/identity (0x0)
    debug2: key: /home/user/.ssh/id_rsa (0x100e9778)
    debug2: key: /home/user/.ssh/id_dsa (0x0)
    debug3: input_userauth_banner

    ****USAGE WARNING****
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug3: start over, passed a different list
    publickey,password,keyboard-interact
    ive
    debug3: preferred publickey
    debug3: authmethod_lookup publickey
    debug3: remaining preferred:
    debug3: authmethod_is_enabled publickey
    debug1: Next authentication method: publickey
    debug1: Trying private key: /home/user/.ssh/identity
    debug1: PEM_read_PrivateKey failed
    debug1: read PEM private key done: type
    Enter passphrase for key '/home/user/.ssh/identity':
    debug1: read PEM private key done: type RSA
    debug3: sign_and_send_pubkey
    debug2: we sent a publickey packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug1: Offering public key: /home/user/.ssh/id_rsa
    debug3: send_pubkey_test
    debug2: we sent a publickey packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interacti
    ve
    debug1: Trying private key: /home/user/.ssh/id_dsa
    debug3: no such identity: /home/user/.ssh/id_dsa
    debug2: we did not send a packet, disable method
    debug1: No more authentication methods to try.
    Permission denied (publickey,password,keyboard-interactive).

    D:\Dokumente und Einstellungen\user>

    please anybody help!


  5. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    IIRC authorized_keys2 is deprecated. You should be using authorized_keys
    in any recent version of OpenSSH.
    --
    To reply by email remove "_nospam"

  6. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    On Fri, 07 Apr 2006 15:51:51 +0000, Chuck wrote:

    > For example: mY1sTp@55w0rd.


    Damn it! Now I need to change my password.

    - Andrew


  7. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Hi,
    I also tried:
    C:\dokumente und einstellungen\neo\.ssh\authorized_keys
    instead of authorized_keys2

    Question: Do I have to have to be logged in as neo on client in order
    to be allowed to access server via PPK auth?

    because for passwd auth I can be logged in as whoever I like, as long
    as the username/password is correct. (that's what I am used to)

    It just soooooo stupid that it won't give me any suffiecient info what
    I did wrong. ARGH!
    Now I am messing with putty *sigh*

    thankx guys!


  8. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Is there any list of things on the net that tells me what file with
    what name must be where with what priviliges in order to gain access??

    I tried collection informations from all over the place and put them in
    one word doc.
    But It did not help.

    It's kind of killing my self esteem!
    Can it be so hard to use this system?
    I bet I made a tiny little mistake somewhere, but I just can't beliefe
    I have to study informatics and c++ and mess with the source in order
    to use ssh properly.
    ARGH again.


  9. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Does it make any difference if server has sp1 and client has sp2
    installed?

    ======Right now my files setup on server is like this:=======
    C:\dokumente und einstellungen\neo\.ssh\authorized_keys
    containing:
    ssh-rsa
    AAAAB3NzaC1yc2EAAAABIwAAAMEAtcawYiticglVKVeEC12xmL SHi7J+YnQS3muwrpuEL4lkBjCWv/mZyxUsMf6vgb5cK3ZfoukQGxxfupzXWVEkv9INEQsQOBPJ2WpM 4zgelfe1j7u5PM2owq18HeKaaVhZZ+Asy9TBggB4eHKRBGAmxB C7NjT5Ehm18FBJVb3uIjv8axjmaHe/e2ADypNXP6JMpnTNmzkMjBs1LQuvgWhp6ZolOR0YXCM+LzC33h tMKX72SCNynyftDtarbCItrOgl
    rsa key for user on client

    C:\dokumente und einstellungen\neo\.ssh\\known_hosts
    containing:
    desktoper,192.168.0.11 ssh-rsa ssh-rsa
    AAAAB3NzaC1yc2EAAAABIwAAAMEAtcawYiticglVKVeEC12xmL SHi7J+YnQS3muwrpuEL4lkBjCWv/mZyxUsMf6vgb5cK3ZfoukQGxxfupzXWVEkv9INEQsQOBPJ2WpM 4zgelfe1j7u5PM2owq18HeKaaVhZZ+Asy9TBggB4eHKRBGAmxB C7NjT5Ehm18FBJVb3uIjv8axjmaHe/e2ADypNXP6JMpnTNmzkMjBs1LQuvgWhp6ZolOR0YXCM+LzC33h tMKX72SCNynyftDtarbCItrOgl
    rsa key for user on client

    laptoper,192.168.0.18 ssh-rsa
    AAAAB3NzaC1yc2EAAAABIwAAAIEAs/4wRD+JP630U63hVX7I+lQP7tJ0T+BDv+WnY54gxno3cLAXrvRe lvR/wIHAQRlCGf3yxasx+SdCB1dW5hdUj9A7OjibQ2qdes1XtP8qeC tNTbJD8zhAGGSoENS1tk8LEeH7+OoQF52xZadAV/NZEl5/rZAiO7g4AW7bGrE374U=

    C:\Programme\OpenSSH\etc\passwd
    containing:
    neo:unused_by_nt/2000/xp:1003:513:U-LAPTOPER\neo,S-1-5-21-527237240-616249376-839522115-1003:/home/neo:/bin/switch
    user:unused_by_nt/2000/xp:1007:513:user,U-LAPTOPER\user,S-1-5-21-527237240-616249376-839522115-1007:/home/user:/bin/switch
    user:unused_by_nt/2000/xp:1008:513:user,U-LAPTOPER\user,S-1-5-21-527237240-616249376-839522115-1008:/home/user:/bin/switch

    C:\Programme\OpenSSH\etc\group
    containing:
    root:S-1-5-32-544:0:
    SYSTEM:S-1-5-18:18:
    Kein:S-1-5-21-527237240-616249376-839522115-513:513:
    Administratoren:S-1-5-32-544:544:
    Benutzer:S-1-5-32-545:545:
    Gäste:S-1-5-32-546:546:
    Hauptbenutzer:S-1-5-32-547:547:
    Netzwerkkonfigurations-Operatoren:S-1-5-32-556:556:
    Remotedesktopbenutzer:S-1-5-32-555:555:
    Replikations-Operator:S-1-5-32-552:552:
    Sicherungs-Operatoren:S-1-5-32-551:551:
    Hilfedienstgruppe:S-1-5-21-527237240-616249376-839522115-1001:1001:
    root:S-1-5-32-544:0:
    SYSTEM:S-1-5-18:18:
    Kein:S-1-5-21-527237240-616249376-839522115-513:513:
    Administratoren:S-1-5-32-544:544:
    Benutzer:S-1-5-32-545:545:
    Gäste:S-1-5-32-546:546:
    Hauptbenutzer:S-1-5-32-547:547:
    Netzwerkkonfigurations-Operatoren:S-1-5-32-556:556:
    Remotedesktopbenutzer:S-1-5-32-555:555:
    Replikations-Operator:S-1-5-32-552:552:
    Sicherungs-Operatoren:S-1-5-32-551:551:
    Hilfedienstgruppe:S-1-5-21-527237240-616249376-839522115-1001:1001:
    root:S-1-5-32-544:0:
    SYSTEM:S-1-5-18:18:
    Kein:S-1-5-21-527237240-616249376-839522115-513:513:
    Administratoren:S-1-5-32-544:544:
    Benutzer:S-1-5-32-545:545:
    Gäste:S-1-5-32-546:546:
    Hauptbenutzer:S-1-5-32-547:547:
    Netzwerkkonfigurations-Operatoren:S-1-5-32-556:556:
    Remotedesktopbenutzer:S-1-5-32-555:555:
    Replikations-Operator:S-1-5-32-552:552:
    Sicherungs-Operatoren:S-1-5-32-551:551:
    Hilfedienstgruppe:S-1-5-21-527237240-616249376-839522115-1001:1001:

    ======on client is like this======
    (I am just posting everything here including the private key... gonna
    be deleted/changed as soon as I found the error)

    D:\Programme\OpenSSH\etc\passwd
    neo:unused_by_nt/2000/xp:1004:513:neo,U-DESKTOPER\neo,S-1-5-21-1659004503-484061587-1417001333-1004:/home/neo:/bin/switch
    user:unused_by_nt/2000/xp:1003:513:U-DESKTOPER\user,S-1-5-21-1659004503-484061587-1417001333-1003:/home/user:/bin/switch

    D:\dokumente und einstellungen\neo\.ssh\id_rsa
    ssh-rsa
    AAAAB3NzaC1yc2EAAAABIwAAAMEAtcawYiticglVKVeEC12xmL SHi7J+YnQS3muwrpuEL4lkBjCWv/mZyxUsMf6vgb5cK3ZfoukQGxxfupzXWVEkv9INEQsQOBPJ2WpM 4zgelfe1j7u5PM2owq18HeKaaVhZZ+Asy9TBggB4eHKRBGAmxB C7NjT5Ehm18FBJVb3uIjv8axjmaHe/e2ADypNXP6JMpnTNmzkMjBs1LQuvgWhp6ZolOR0YXCM+LzC33h tMKX72SCNynyftDtarbCItrOgl
    rsa key for user on client

    D:\dokumente und einstellungen\neo\.ssh\identity
    -----BEGIN RSA PRIVATE KEY-----
    Proc-Type: 4,ENCRYPTED
    DEK-Info: DES-EDE3-CBC,0AAF2BED6C0B2231

    A5Ff8CJfjv+IG5nmo1FSoePWzdiRc3VOZ9jf9NPPRH9w20hePE 1bXbR3Y907nurz
    42RiEiyRHX2bY7kxB/xICVpz6ihDaOY7XIqqwIzcDbaTA9AGyeHcUOvPOxCDcV1O
    QlC67dLccZmxtCkCm839ppuKb/gDIdgTr8SA6EkWwMjHfqZ4oc9WA+mVGq/rH8xK
    nHfkSo+T6Lcorr8G8ioYcyO2jsTzbPsSGJmmD9/8T5SXBPeb+oe9Cdk1MgTKpn7Y
    OX8PK0bkTP0MbvoulZI+/ACN5FIPB7ddXyCU28qQAUqw+eSEwisM9TKphi6pxVO5
    qJcpk9Sm+YT4G4sXloD2hKPwMXNR0xRshQrmk7LoatXgzRgNUU RbZgXeas6v+KTH
    yQOAfgrTVBqluh8cn1lchZotOi6hacI/aeGRNsBnLkCttX/v1Sh0nzsk48QUQWsG
    rkMhti7av6g035Ey5CqDYCLHe3SyQAhwCWRgubX44L75iOeYgs PHbJq4giNOIrFN
    8313WYuMc0XbVGEIYT1boSEAbCZ6+yzo4sB7eC/kmurd5OWSk5vZ5YNqJdHm6xCf
    d8bIe2wS/9r8DGtgs9WNwI0T8R1a9hgkSognMxORZY8u6idVNDX5ZquTMCW DaoWX
    IXLsvdoIQlKKn+XVt6u5eTrVOds1P3iLwHPs1du3WN+3VMX3vz TKfVJRLjKgT3EA
    SM0/hDzyqdTHBf9S/UUON1C0icb/+++9S0l1z9iGlTjU4S710w5f6xQKPCWgQtZJ
    iUKgxp89z9WTZ40QKngSrbK18B2cOl2L/fbCajtMgcY/chLEvxxz7jV2Pjtc5+zp
    yUA0YroJb8JMDIhM3Mdy4z6RQKD5mO8XDkNAG3OXHjLKQ2SoZX IJlf0SamK5hi7w
    FIK/YtTTYVXTVhq7NgXynUsgli5oE1bB94cggue0TWcNeFvOoXyAy4 fWs+dL/rBK
    faNCKozhQrRjcY+2t19rzdMqPs1z8/mJBT9hiRYHVUZHeB8MhM0ml+evFPXqnjG6
    wByyCBXMQu9aloo1p1NLaOqHxBmNqQWYkrVkCxxLq88CKZt8AD ZqR83dodUcrzwx
    q4aFsdiiNCfBhLuH/McWPAP0iVwLMAzCPAO2xttRQOY3lhCoLE6vkt8zajahnTL9
    V4A1sLu4gXU7yGPYmSNhPURFjiHJoMWAbSWdYgrPTss=
    -----END RSA PRIVATE KEY-----


    D:\dokumente und einstellungen\neo\.ssh\known_hosts
    laptoper,192.168.0.18 ssh-rsa
    AAAAB3NzaC1yc2EAAAABIwAAAIEAs/4wRD+JP630U63hVX7I+lQP7tJ0T+BDv+WnY54gxno3cLAXrvRe lvR/wIHAQRlCGf3yxasx+SdCB1dW5hdUj9A7OjibQ2qdes1XtP8qeC tNTbJD8zhAGGSoENS1tk8LEeH7+OoQF52xZadAV/NZEl5/rZAiO7g4AW7bGrE374U=


    HELP!
    I AM KINDA LOST!


  10. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    E-MOTION wrote:
    > Is there any list of things on the net that tells me what file with
    > what name must be where with what priviliges in order to gain access??
    >
    > I tried collection informations from all over the place and put them in
    > one word doc.
    > But It did not help.
    >
    > It's kind of killing my self esteem!
    > Can it be so hard to use this system?
    > I bet I made a tiny little mistake somewhere, but I just can't beliefe
    > I have to study informatics and c++ and mess with the source in order
    > to use ssh properly.
    > ARGH again.
    >


    Sounds like your running the server on windows. The location of the file
    differs depending on which ssh server package you're using and should be
    in the docs. Is it WinSSH or CopSSH? I prefer the latter. I found it
    easier to install, administer, and it just worked better. In the case of
    CopSSH the authorized_keys file is in...

    c:\Program Files\CopSSH\home\userid\.ssh

    In WinSSH IIRC it was in c:\Documents and Settings\userid\.ssh but I'm
    not 100% sure of that. I only used WinSSH for a few days and switched.

  11. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    On Sat, 08 Apr 2006 08:10:19 -0700, E-MOTION wrote:

    > than i have two files in /documents and settings/user/id_rsa (private
    > key) and /documents and settings/user/id_rsa.pub (public key)
    >
    > 6. than i am renaming
    > id_rsa(private key)-> identity
    > id_rsa.pub(public key)-> id_rsa


    Why did you do this? This is nonsense. If you copy a private key file
    to a public key filename how can you expect to get it to work? They are
    different formats and contents.

    You should undo this step and try again.

    JohnK

  12. Re: BIG BIG PROBLEM OPENSSH PUBLIC KEY AUTH NOT WORKING

    Hi,
    I did not know there were more FREE open ssh packages out there for
    windows.
    I used OpenSSH for Windows v3.8.1p1-1 by Michael Johnson from
    sourceforge.net (OpenSSHv381-20040709.exe).

    Thankx for the hint! I gonna try out copssh!


+ Reply to Thread