kr icon indicating copy to clipboard operation
kr copied to clipboard

authentication agent forwarding not working

Open OGKevin opened this issue 7 years ago • 5 comments

Hey there,

I remember I was able to ssh -A server and then was able to use KR(do git pulls/ssh) on the remote machine without having to actually install KR on the remote machine.

Recently I tried to do this again, but it seems to not be working. When running debug I can see the following:

debug1: Authentication succeeded (publickey).
Authenticated to xxxx (via proxy).
debug1: channel 0: new [client-session]
debug1: Requesting [email protected]
debug1: Entering interactive session.
debug1: pledge: proc
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug1: Requesting authentication agent forwarding.
debug1: Sending environment.
debug1: Sending env LC_CTYPE = UTF-8

debug1: Requesting authentication agent forwarding.

I'm not sure however if this means that the request was accepted by the remote or not. Did something change recently that broke/disabled this ?

OGKevin avatar May 25 '18 16:05 OGKevin

Nothing has changed in kr with respect to agent forwarding, maybe ssh -vv will contain something more helpful? On Fri, May 25, 2018 at 6:48 PM Kevin Hellemun [email protected] wrote:

Hey there,

I remember I was able to ssh -A server and then was able to use KR(do git pulls/ssh) on the remote machine without having to actually install KR on the remote machine.

Recently I tried to do this again, but it seems to not be working. When running debug I can see the following:

debug1: Authentication succeeded (publickey). Authenticated to xxxx (via proxy). debug1: channel 0: new [client-session] debug1: Requesting [email protected] debug1: Entering interactive session. debug1: pledge: proc debug1: client_input_global_request: rtype [email protected] want_reply 0 debug1: Requesting authentication agent forwarding. debug1: Sending environment. debug1: Sending env LC_CTYPE = UTF-8

debug1: Requesting authentication agent forwarding. I'm not sure however if this means that the request was accepted by the remote or not. Did something change recently that broke/disabled this ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kryptco/kr/issues/209, or mute the thread https://github.com/notifications/unsubscribe-auth/ABSUUxbGCQkL4GIFwkQzJDOgf3piY5Pzks5t2DXagaJpZM4UOSEg .

kcking avatar May 26 '18 06:05 kcking

With -vv i see

debug1: Requesting authentication agent forwarding.
debug2: channel 0: request [email protected] confirm 0

and take the 0 as false ?

Not sure why tho 🤔

OGKevin avatar May 26 '18 09:05 OGKevin

Apologies for the delay on this. Agent forwarding seems to be working fine for me, and my -vv output is the same as yours.

Does ssh-add -L output your krypton key when you are logged into the first server?

kcking avatar Jun 13 '18 15:06 kcking

@kcking yes it does.

OGKevin avatar Jun 15 '18 10:06 OGKevin

Can you check if the ssh -vv output to the final destination server offers the Krypton key? It sounds like the Krypton key may not have access to this server.

kcking avatar Jun 15 '18 14:06 kcking