Use the gpg-agent for initial ssh socket support about gpg-bridge HOT 17 CLOSED

I see. I can give it a try these weekend and see whether it works. What need to be done are to support name pipe and cygwin compatible socket.

If you are in a hurry, contributions are also welcome.

from gpg-bridge.

Waiting for tokio-rs/tokio#3388.

from gpg-bridge.

Detaching problem is detected and fixed.

from gpg-bridge.

reading through this makes it sound like the S.gpg-agent.ssh socket is special in Windows and handled differently than the extra gpg socket, so maybe I just need to continue using both tools until https://dev.gnupg.org/T3883 is fixed.

from gpg-bridge.

(selfishly, I'd love a tool that could do both with just one background service to setup)

from gpg-bridge.

along with wsl-ssh-pageant to forward SSH+GPG sockets to a remote machine and perform SSH+GPG operations.

Can you explain more on that? Like forward ssh from wsl to remote? Or something else?

I can forward the ssh agent to remote by using the native windows ssh client by simply configuring ForwardAgent yes to yes. What needs to be done is making sure the ssh-agent service that comes from the client are started.

from gpg-bridge.

from gpg-bridge.

This post contains details about the exact setup I'm using now: PowerShell/Win32-OpenSSH#827 (comment)

from gpg-bridge.

One thing I've noticed - however gpg-bridge is backgrounding itself, it manages to entirely disappear from Task Manager and then I don't know if it is running or not. (Process Explorer sees it, though.)

from gpg-bridge.

Windows will create a blank terminal window for console program, gpg-bridge uses some trick to get around the issue, the side effect is it will not be shown up in Task Manager. There are two solutions for the problem, one is to implement it as Windows Service instead, the other is to use a systray as #4 describes.

from gpg-bridge.

Looks like this is unblocked: tokio-rs/tokio#3760

EDIT: just wanted to say thanks again for this, I use it almost every day.

from gpg-bridge.

Glad it helps! I may check it at weekends.

from gpg-bridge.

I can read bytes from named pipe now, but I can't make gnupg ssh socket to accept requests. I may need more time on this.

from gpg-bridge.

I pushed my changes. The script has been largely updated, including changes to command line arguments to support new ssh forwarding. See README for how to use the tool.

I have tested locally to make sure ssh forwarding work, but if you find any problem, don't hesitate to report.

from gpg-bridge.

It seems like it's working well when I use this:

.\gpg-bridge.exe --extra 127.0.0.1:4321 --ssh \\.\pipe\gpg-bridge-ssh

If I use this instead, it went into some awful loop spawning itself over and over trying to spawn the detached window it looked like.

.\gpg-bridge.exe --detach --extra 127.0.0.1:4321 --ssh \\.\pipe\gpg-bridge-ssh

from gpg-bridge.

Also, thank you x1000. This is quite slick.

from gpg-bridge.

Close as the feature is implemented.

from gpg-bridge.