search for: ssh_agent_failur

...messages, which ssh-agent2 doesn't understand, so the agent sends back an "agent failure" message. This should be fine; the OpenSSH code looks for that. However, there are two "agent failure" messages in the ssh.com world: #define SSH1_AGENT_FAILURE 5 #define SSH_AGENT_FAILURE 102 OpenSSH only checks for the first one, but the agent returns the second one. OpenSSH doesn't recognize it, and dies. Below is a proposed fix, as diffs to authfd.c and authfd.h. -- Richard Silverman slade at shore.net ===================================================...

Folks, I am perplexed. I updated my workstation at work Wed before I left, from 6.7 to 6.8. Then, yesterday, I went to use ssh-add -s libcoolkeypk11.so, which I've done many times before to add the certs from my PIV card... and 100% of the time if fails, letting me SSH_AGENT_FAILURE, cannot add card. Now, using a script called sccr, which uses my public and private key to generate a one-time password (we use the to sudo to root), works with no problem. I used my card to go into the data center this morning, which also reads my card, and had no problem. I've tried eval...

On 04/04/18 21:56, Damien Miller wrote: > > I don't follow - clients always have to know that the last message sent > was, otherwise they wouldn't be able to disambiguate the shared > SSH_AGENT_SUCCESS / SSH_AGENT_FAILURE. The format of that message doesn't change though -- it's always a single byte (so you don't need that information in the function that actually parses the message). With this proposal that is no longer the case. I mean, maybe it's a pointless concern and things are fine as propos...

Hi, I've been reading the RFC draft for the OpenSSH agent protocol and trying to understand the extension mechanism. It seems like a client, after sending an extension message, will have to then interpret any following success (0x6) message differently according to the extension request just sent. The example with the "query" extension returning a success message with extra data

...m perplexed. I updated my workstation at work Wed before I left, > > from 6.7 to 6.8. Then, yesterday, I went to use ssh-add -s > > libcoolkeypk11.so, which I've done many times before to add the certs > > from my PIV card... and 100% of the time if fails, letting me > > SSH_AGENT_FAILURE, cannot add card. > > > > Now, using a script called sccr, which uses my public and private key > > to generate a one-time password (we use the to sudo to root), works > > with no problem. I used my card to go into the data center this > > morning, which also reads...

...ks, > > I am perplexed. I updated my workstation at work Wed before I left, > from 6.7 to 6.8. Then, yesterday, I went to use ssh-add -s > libcoolkeypk11.so, which I've done many times before to add the certs > from my PIV card... and 100% of the time if fails, letting me > SSH_AGENT_FAILURE, cannot add card. > > Now, using a script called sccr, which uses my public and private key > to generate a one-time password (we use the to sudo to root), works > with no problem. I used my card to go into the data center this > morning, which also reads my card, and had no prob...

Dear friends, First, thanks for helping me on ssh default option for smartcards. I recompiled SSH from CVS and it seems to work. I still have problems with: ssh-add -s /usr/lib/opensc-pkcs11.so Enter passphrase for PKCS#11: (I enter PIN code) SSH_AGENT_FAILURE Could not add card: /usr/lib/opensc-pkcs11.so pkcs11-tool --slot 1 -O Public Key Object; RSA 2048 bits label: Public Key ID: 7645d913d5***********54816ff02324c23a7ebf4 Usage: none Certificate Object, type = X.509 cert label: CAcert WoT User's Root CA ID ID:...

On Tue, 2010-04-06 at 15:52 +0300, Lars Nooden wrote: > You might wish to focus on sftp instead of scp. Okay, I will have a look. I had some problems: 1) I would like to store smart card information -o PKCS11Provider=/usr/lib/opensc-pkcs11.so in /etc/ssh/ssh-config. Is it possible? 2) ssh-add -s does not seem to work. Read:

...ty: P2 Component: Smartcard AssignedTo: unassigned-bugs at mindrot.org ReportedBy: jmpoure at free.fr Dear friends, I am using the latest version of OpenSC and cvs version of OpenSSH. ssh-add -s /usr/lib/opensc-pkcs11.so Enter passphrase for PKCS#11: (I enter PIN code) SSH_AGENT_FAILURE Could not add card: /usr/lib/opensc-pkcs11.so pkcs11-tool --slot 1 -O Public Key Object; RSA 2048 bits label: Public Key ID: 7645d913d5***********54816ff02324c23a7ebf4 Usage: none Certificate Object, type = X.509 cert label: CAcert WoT User's Root CA ID ID:...

...if (flags & SSH_AGENT_OLD_SIGNATURE) @@ -319,7 +319,7 @@ buffer_init(&msg); if (ok == 0) { buffer_put_char(&msg, SSH2_AGENT_SIGN_RESPONSE); - buffer_put_string(&msg, signature, slen); + buffer_put_binary(&msg, signature, slen); } else { buffer_put_char(&msg, SSH_AGENT_FAILURE); } @@ -354,7 +354,7 @@ key_size(key), bits); break; case 2: - blob = buffer_get_string(&e->request, &blen); + blob = buffer_get_binary(&e->request, &blen); key = key_from_blob(blob, blen); xfree(blob); break; diff -bur openssh-3.7.1p2.orig/ssh-dss.c...