search for: input_userauth_pk_ok

...ckey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: next auth method to try is publickey debug1: userauth_pubkey_agent: testing agent key /root/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 400377a0 hint -1 debug2: input_userauth_pk_ok: fp 7a:44:be:6c:94:18:fb:0c:ff:e5:1a:9a:07:98:a5:27 debug3: sign_and_send_pubkey debug3: clear_auth_state: key_free 400377a0 debug1: ssh-userauth2 successful: method publickey debug1: channel 0: new [client-session] debug...

Hello I think I've found a bug but since no one replied to me on comp.security.ssh, I'll try my luck here. On my client, PreferredAuthentications is set to publickey,password. When using the commands option in authorized_keys file like command="ls" ssh-dss <key>... it is supposed to connect using the private key associated with <key>, perform ls and then quits.

Hi! I am distributing 2.5.1p1 for production use on my system by now and prepare switching to protocol 2 as default protocol. I just noted, that ssh-agent can be used for protocol 1 and 2, but the keys kept in ssh-agent are not compared against keys in .ssh. Example: I have a DSA key in id_dsa which I load into ssh-agent on login. When connecting to an account accepting the key everything is

...'s agent process worked as expected. After that commit, the user needs both the private and the cert (also with the private key) loaded together to work. if I try to use just the cert after this commit, I see: debug1: Server accepts key: pkalg ssh-rsa-cert-v01 at openssh.com blen 2769 debug2: input_userauth_pk_ok: fp SHA256:XiFOO+XzZ0m/aWzkQLgxVFI2HJV3abWpNyuIhcEYKuc debug3: sign_and_send_pubkey: RSA-CERT SHA256:XiFOO+XzZ0m/aWzkQLgxVFI2HJV3abWpNyuIhcEYKuc debug1: sign_and_send_pubkey: no private key for certificate "[Valid until Fri 11 Mar 2016 18:10 UTC, Version 2]" if I modify the ca to add bot...

...ickey packet, wait for reply debug1: Authentications that can continue: publickey debug1: Offering public key: RSA SHA256:B1iu57Rkn5emB//MUP4YEipr4oRRmqZeBHMQWf0U+Mk /home/xxx/.ssh/jumpline debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp SHA256:B1iu57Rkn5emB//MUP4YEipr4oRRmqZeBHMQWf0U+Mk debug1: Authentication succeeded (publickey). Authenticated to sohnen-moe.com ([216.222.193.110]:1022). ** blah blah blah *** ---[ end ]--- ---[ failed login ]--- debug2: set_newkeys: mode 0 debug1: rekey after 4294967296 blocks ** the logs...

Hi, When following the install instructions in README, I get the following build error: cc -O2 -DKRB5 -I/usr/include/kerberosV -DGSSAPI -I/usr/src/usr.bin/ssh/ssh/.. -c /usr/src/usr.bin/ssh/ssh/../sshconnect2.c /usr/src/usr.bin/ssh/ssh/../sshconnect2.c: In function `input_userauth_pk_ok': /usr/src/usr.bin/ssh/ssh/../sshconnect2.c:460: dereferencing pointer to incomplete type /usr/src/usr.bin/ssh/ssh/../sshconnect2.c:460: structure has no member named `idlist' *** Error code 1 Stop in /usr/src/usr.bin/ssh/ssh. *** Error code 1 Stop in /usr/src/usr.bin/ssh. The current Op...

..._FIPS + #include <openssl/fips.h> + #endif + + /* import */ extern char *client_version_string; extern char *server_version_string; *************** *** 591,597 **** key->type, pktype); goto done; } ! fp = key_fingerprint(key, SSH_FP_MD5, SSH_FP_HEX); debug2("input_userauth_pk_ok: fp %s", fp); xfree(fp); --- 604,611 ---- key->type, pktype); goto done; } ! fp = key_fingerprint(key, FIPS_mode() ? SSH_FP_SHA1 : SSH_FP_MD5, ! SSH_FP_HEX); debug2("input_userauth_pk_ok: fp %s", fp); xfree(fp); **********...

...On that board, ssh server greets with SSH-2.0-mpSSH_0.0.1 string. After the upgrade, I get the disconnection: Received disconnect from 10.1.1.169: 11: Client Disconnect Run with -vv shows debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: fp a9:76:16:94:32:31:37:5f:c1:10:6c:04:ab:33:d0:8f debug1: Authentications that can continue: password,publickey debug1: Offering public key: /usr/home/kostik/.ssh/id_dsa debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-dss blen 434 debug2: input_userauth_pk...

...e debug3: authmethod_lookup publickey debug3: remaining preferred: password,keyboard-interactive debug3: authmethod_is_enabled publickey debug1: next auth method to try is publickey debug1: try pubkey: //.ssh/id_dsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: input_userauth_pk_ok: pkalg ssh-dss blen 434 lastkey 10ae98 hint 1 debug2: input_userauth_pk_ok: fp b2:48:f6:61:cd:b8:d0:b5:58:85:95:be:7e:20:68:a8 debug3: sign_and_send_pubkey debug1: read PEM private key done: type DSA debug1: sig size 20 20 debug1: ssh-userauth2 successful: method publickey debug1: fd 6 setting O_NO...

...ib/pkcs11/opensc-pkcs11.so ssh-rsa /lib/pkcs11/opensc-pkcs11.so $ ssh -vv $REMOTEHOST OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016 ... debug1: Offering RSA public key: /usr/lib/libykcs11.so debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-rsa blen 279 debug2: input_userauth_pk_ok: fp SHA256:... sign_and_send_pubkey: signing failed: agent refused operation ... debug1: Next authentication method: password $USER@$REMOTEHOST's password: If I remove the library (and keys) and try the connection again: $ ssh-add -e /lib/pkcs11/opensc-pkcs11.so Card removed: /lib/pkcs11/open...

...yboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/phk/.ssh/id_dsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Server accepts key: pkalg ssh-dss blen 433 debug2: input_userauth_pk_ok: fp a1:04:99:61:03:22:7e:79:20:fd:57:57:2c:7c:a8:98 debug3: sign_and_send_pubkey debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/home/phk/.ssh/id_dsa': ------- You are receiving this mail because: ------- You are the a...

...ey > debug3: remaining preferred: password,keyboard-interactive > debug3: authmethod_is_enabled publickey > debug1: next auth method to try is publickey > debug1: try pubkey: //.ssh/id_dsa > debug3: send_pubkey_test > debug2: we sent a publickey packet, wait for reply > debug1: input_userauth_pk_ok: pkalg ssh-dss blen 434 lastkey 10ae98 hint > 1 > debug2: input_userauth_pk_ok: fp > b2:48:f6:61:cd:b8:d0:b5:58:85:95:be:7e:20:68:a8 > debug3: sign_and_send_pubkey > debug1: read PEM private key done: type DSA > debug1: sig size 20 20 > debug1: ssh-userauth2 successful: method...

.../id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: Remote: Forced command: echo yes debug1: Remote: Pty allocation disabled. debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 0x810acb8 hint -1 debug2: input_userauth_pk_ok: fp 3d:8d:0c:63:4c:31:62:7a:de:c7:b6:aa:58:b2:07:5a debug3: sign_and_send_pubkey debug3: clear_auth_state: key_free 0x810acb8 debug1: Remote: Forced command: echo yes debug1: Remote: Pty allocation disabled. debug1: Remo...

...debug1: next auth method to try is publickey debug1: try privkey: /export/home/etl_ops/.ssh/identity debug3: no such identity: /export/home/etl_ops/.ssh/identity debug1: try pubkey: /export/home/etl_ops/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 110948 hint 1 debug2: input_userauth_pk_ok: fp 61:ff:c1:f1:05:24:73:8d:8b:63:e0:4b:db:68:3e:61 debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug1: ssh-userauth2 successful: method publickey debug1: channel 0: new [client-session] debug3:...

...RVICE_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: /root/.ssh/id_dsa debug1: try pubkey: /root/.ssh/id_rsa debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 0x8112050 hint 2 debug1: read PEM private key done: type RSA debug1: ssh-userauth2 successful: method publickey debug1: fd 4 setting O_NONBLOCK debug1: channel 0: new [client-session] debug1: channel_new: 0 debug1: send channel open 0 debug1: Entering interactive ses...

http://bugzilla.mindrot.org/show_bug.cgi?id=227 ------- Additional Comments From mouring at eviladmin.org 2002-04-26 15:03 ------- Provide us with your environment and a reproducable example. The only thing I can think of is that you are using ssh-agent and you've registered your key with the agent the first time. Thus it is now usable for all following SSH sessions (from your account)

...orized_principals file contains one line: test at 172.31.43.3 I attempt to connect to the target server from the test client: $ ssh -vvv -Y -p 2022 -l test 172.31.44.115 There is verbose output, which mostly seems right until (on the client): debug1: ssh_rsa_verify: signature correct debug2: input_userauth_pk_ok: fp c9:42:44:91:48:04:45:b2:ee:93:12:3f:e5:89:13:ab debug3: sign_and_send_pubkey: RSA-CERT c9:42:44:91:48:04:45:b2:ee:93:12:3f:e5:89:13:ab debug1: read PEM private key begin debug1: key_parse_private_pem: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passp...

...g1: 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: /home/ipopovet/.ssh/id_rsa debug1: try pubkey: /home/ipopovet/.ssh/id_dsa debug1: input_userauth_pk_ok: pkalg ssh-dss blen 434 lastkey 13a380 hint 2 debug1: read PEM private key done: type DSA debug1: sig size 20 20 debug1: ssh-userauth2 successful: method publickey debug1: fd 5 setting O_NONBLOCK debug1: channel 0: new [client-session] debug1: channel_new: 0 debug1: send channel open 0 debug1: Ente...

...1: 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: userauth_pubkey_agent: testing agent key rsa-key-20020913 > debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 20043ab8 hint > -1 > debug1: ssh-userauth2 successful: method publickey > debug1: fd 4 setting O_NONBLOCK > debug1: fd 5 setting O_NONBLOCK > debug1: channel 0: new [client-session] > debug1: send channel open 0 > debug1: Entering interactive ses...

...authmethod_lookup publickey debug3: remaining preferred: password,keyboard-interactive debug3: authmethod_is_enabled publickey debug1: next auth method to try is publickey debug1: try pubkey: /users/clad/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 4001df30 hint 1 debug2: input_userauth_pk_ok: fp 0f:95:05:08:b7:47:eb:dd:37:ae:71:c1:5a:24:4b:20 debug3: sign_and_send_pubkey debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> Enter passphrase for key '/users/clad/.ssh/id_...