Protocol Error Rcvd Type 60
On Thu, Mar 08, 2001 at 12:25:51PM +0100, Markus Friedl wrote: > On Thu, Mar 08, 2001 at 10:55:44AM +0100, Lutz Jaenicke wrote: > > 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 /home/aet/serv01/jaenicke/.ssh/id_rsa > > debug2: we sent a publickey packet, wait for reply > > debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 4001da88 hint -1 > > this means the server will accept the agent key. > > it did stop here? you did not login automatically?? It does mean precisely that, the login failed with the error shown below. > could you try -v -v -v? > (server output is not relevant). > > > debug1: next auth method to try is publickey > > debug2: userauth_pubkey_agent: no more keys > > debug2: userauth_pubkey_agent: no message sent > > debug1: try pubkey: /home/aet/serv01/jaenicke/.ssh/id_rsa > > debug2: we sent a publickey packet, wait for reply > > Disconnecting: protocol error: rcvd type 60 > > debug1: Calling cleanup 0x4000dffa(0x0) And here is the output with triple -v: debug1: done: 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 debug3: start over, passed a different list debug3: authmethod_lookup publickey debug3: authmethod_is_enabled publickey debug1: next auth method to try is publickey debug1: userauth_pubkey_agent: testing agent key /home/aet/serv01/jaenicke/.ssh/id_rsa debug2: we sent a publickey packet, wait for reply debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 4001da88 hint -1 debug3: authmethod_lookup publickey debug3: authmethod_is_enabled publickey debug1: next auth method to try is publickey debug2: userauth_pubkey_agent: no more keys debug2: userauth_pubkey_agent: no message sent debug1: try pubkey: /home/aet/serv01/jaenicke/.ssh/id_rsa debug2: we sent a publickey packet, wait for reply Disconnecting: protocol error: rcvd type 60 debug1: Calling cleanup 0x4000dffa(0x0) I can also add my id_dsa key into ssh-agent to no avail: 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 debug3: start over, passed a different list debug3: authmethod_lookup
Views: 1485 Permalink Re: ssh-agent and id_dsa [In reply to] On Thu, Mar 08, 2001 at 12:49:43PM +0100, Lutz Jaenicke wrote: > debug1: userauth_pubkey_agent: testing agent key /home/aet/serv01/jaenicke/.ssh/id_rsa > debug2: we sent a publickey packet, wait for reply > debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 4001da88 hint -1 i don't understand why 'ssh' does not try to send a pubkey packet. could you please add debug statements to the https://lists.mindrot.org/pipermail/openssh-unix-dev/2001-March/005564.html 'if': if (authctxt->last_key != NULL && authctxt->last_key_sign != NULL && key_type_from_name(pkalg) != KEY_UNSPEC && -> debug key_type_from_name(pkalg) (key = key_from_blob(pkblob, blen)) != NULL && -> debug %p, key -> debug key_fingerprint(key) -> debug key_fingerprint(authctxt->last_key) key_equal(key, authctxt->last_key)) { debug2("input_userauth_pk_ok: fp %s", key_fingerprint(key)); sent = sign_and_send_pubkey(authctxt, key, authctxt->last_key_sign); } > debug3: authmethod_lookup publickey > debug3: http://www.gossamer-threads.com/lists/openssh/dev/11274?do=post_view_threaded authmethod_is_enabled publickey > debug1: next auth method to try is publickey > debug2: userauth_pubkey_agent: no more keys > debug2: userauth_pubkey_agent: no message sent > debug1: try pubkey: /home/aet/serv01/jaenicke/.ssh/id_rsa > debug2: we sent a publickey packet, wait for reply > Disconnecting: protocol error: rcvd type 60 > debug1: Calling cleanup 0x4000dffa(0x0) > > I can also add my id_dsa key into ssh-agent to no avail: > 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 > debug3: start over, passed a different list > debug3: authmethod_lookup publickey > debug3: authmethod_is_enabled publickey > debug1: next auth method to try is publickey > debug1: userauth_pubkey_agent: testing agent key /home/aet/serv01/jaenicke/.ssh/id_rsa > debug2: we sent a publickey packet, wait for reply > debug1: input_userauth_pk_ok: pkalg ssh-rsa blen 149 lastkey 4001da88 hint -1 > debug3: authmethod_lookup publickey > debug3: authmethod_is_enabled publickey > debug1: next auth method to try is publickey > debug1: userauth_pubkey_agent: test
openssh (Fedora) Edit Fix Released Unknown redhat-bugs #466818 You need to log in to change this bug's status. Bug watch updates for Red Hat Bugzilla are disabled. Affecting: openssh (Fedora) Filed here by: Brian Murray https://bugs.launchpad.net/bugs/304623 When: 2008-12-03 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Fedora Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status http://www.cisco.com/c/en/us/support/docs/routers/7500-series-routers/7603-cef-error-msgs-7603.html Importance Fix Released Unknown Assigned to unknown Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. Red Hat Bugzilla #466818 URL: The protocol error information about this bug in Launchpad is automatically pulled daily from the remote bug. This information hasn't been pulled yet. Comment on this change (optional) Email me about changes to this bug report openssh (Ubuntu) Edit Fix Released Undecided Caspar Clemens Mierau Edit You need to log in to change this bug's status. Affecting: openssh (Ubuntu) Filed here by: Azhar When: 2008-12-03 Confirmed: 2009-11-02 Assigned: 2009-02-21 protocol error rcvd Started work: 2009-11-02 Completed: 2009-11-02 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Fix Released Undecided Assigned to Me Caspar Clemens Mierau (leitmedium) Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: openssh-client Bug is exactly similar to the one submitted to Fedora here https://bugzilla.redhat.com/show_bug.cgi?id=466818 Add tags Tag help Bug Watch Updater (bug-watch-updater) on 2008-12-03 Changed in openssh: status: Unknown → Fix Released Charlie Kravetz (charlie-tca) wrote on 2008-12-13: #1 Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. Please include, if possible: The source package you found the bug in, for help see https://wiki.ubuntu.com/Bugs/FindRightPackage . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
7500 Series RoutersTroubleshoot and AlertsTroubleshooting TechNotes Troubleshooting CEF-Related Error Messages Download Print Available Languages Download Options PDF (66.4 KB) View with Adobe Reader on a variety of devices Updated:Jun 24, 2008 Document ID:7603 Contents Introduction Prerequisites Requirements Components Used Conventions Background Information Verify Cisco Express Forwarding Status on VIPs and LCs External Data Representation (XDR) Overview Troubleshoot %FIB-3-FIBDISABLE : Fatal error, slot [#]: no memory and %FIB-3-NOMEM: Malloc Failure, disabling dCEF on line card %FIB-3-FIBDISABLE: Fatal error, slot [#]: No window message, LC to RP IPC is non-operational %FIB-3-FIBDISABLE: Fatal error, slot [#]: IPC failure %FIB-4-RPPREFIXINCONST2/1 and %FIB-4-LCPREFIXINCONST2/1 %FIB-3-NORPXDRQELEMS: Exhausted XDR queuing elements while preparing message for slot [#] %FIB-3-FIBBADXDRLEN and %FIB-4-FIBXDRLEN %FIB-3-FIBLC_OOSEQ: Slot [#] disabled - Out of Sequence. Expected [#], received [#] %FIB-4-PUNTINTF: CEF punting packets switched to [int] to next slower path and %FIB-5-NOPUNTINTF: CEF resuming switching packets to [int] %HW_RES_FAIL-4-LOW_CEF_MEM: SLOT [char] is running low %FIB-4-FIBCBLK2: Missing cef tableid [dec] during [chars] event for [IP_address][IP_netmask] Collect Troubleshooting Information if You Create a TAC Service Request Other Troubleshooting Resources Related Information Introduction This document describes the causes of common Cisco Express Forwarding (formerly CEF)-related error messages on platforms that run Distributed Cisco Express Forwarding (formerly dCEF) switching (Cisco 7500 Series Routers and Cisco 12000 Series Internet Routers) and how to troubleshoot them. Note:Depending on the platform on which Distributed Cisco Express Forwarding is configured, Route Processors (RPs) and Line Cards (LCs) are referred to differently. For the 7500 Series, the RP is called the Route Switch Processor (RSP) and LCs are called Versatile Interface Processors (VIPs). On the 1