Skip to content

readme: clarify that 127.0.0.1 should be used over localhost #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
colemickens wants to merge 1 commit into
base: master
Choose a base branch
from
Open

readme: clarify that 127.0.0.1 should be used over localhost #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,10 @@ A bridge connects openssh-portable and GnuPG on Windows.
~/.cargo/bin/gpg-bridge 127.0.0.1:4321
```

If you have customized extra socket localtion, you can append the path as second parameter.
If you have customized extra socket location, you can append the path as second parameter.

**NOTE**: Ensure that you listen on and forward to `127.0.0.1:<port>` as opposed to `localhost:<port>`. The latter will cause `gpg-bridge` to listen

@BusyJay BusyJay Mar 16, 2021

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it's true for all users. How about adding it as a hint or FAQ?

on a TCPv6 socket and then `ssh.exe` will be unable to forward to it properly.

Now you are all set, requests to gpg agent on remote should be able to forward to your local.

Expand All @@ -49,4 +52,4 @@ There are several gotchas if not using bridge to forward gpg agent on Windows. S
available in version 1809 (aka the October 2018 Update), and in Windows Server 1809/2019.

GnuPG on Windows has not utilized native UDS support yet. It simulates a UDS using a TCP stream socket with
customized connect step. So without extra tools, you can't really connect openssh-portable to GnuPG.
customized connect step. So without extra tools, you can't really connect openssh-portable to GnuPG.