-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
what is gpg-agent-passthrough.sh ? #1
Comments
Sorry, just seeing this now! I'll get a copy pushed later tonight or so. |
While you're at it, it might be a good idea to see if you can attempt to set this up on a freshly installed machine, using only the contents within this repo, and create a bare minimum set of instructions. |
I'll work on getting a better installer, for now gpg-agent-passthrough.sh was a red herring and I think just something I was using to test (in lieu of the go binary provided in the release).
You can test the efficacy of the plugin working by right clicking the extension's popup and going to the console, and then test signing something and it'll appear in the console logs. This was only meant as a test of how native messaging works to see if I could later use it for lastpass; my problem being I have a smartcard and can't actually upload my key there. This in itself isn't really a polished product :). Mind if I ask what you two are using it for? I'd be happy to make it an actual tool instead of a sandbox/playground. |
Absolutely! I had submitted a feature request to Flowcrypt, asking if
they'd be able to add the ability to communicate with gpg directly, that
way I could use a smart card with my key on it instead of uploading a
private key into the extension's local browser cache. Then I figured that I
might help the developers out and look for a reference extension that they
might look at to get a feel for how to do it.
If those instructions work, then I'll look into submitting a PR that makes
it a bit easier. :Smile:
~ Sent from my Alphabet phone
…On Mon, Jun 4, 2018, 04:41 Travis Beatty ***@***.***> wrote:
I'll work on getting a better installer,
for now gpg-agent-passthrough.sh was a red herring and I think just
something I was using to test (in lieu of the go binary provided in the
release).
1. move the host binary that either you compile or you copy from the
release into /opt/chrome-gpg-agent/gpg-agent-passthrough.sh
2. install
https://chrome.google.com/webstore/detail/chrome-gpg-agent/bleakneiblnngmahabhdffihlgmbpnbp
3. cp host/manifest.json
~/.config/google-chrome/NativeMessagingHosts/io.linux_fu.chrome_gpg_agent.json
4. replace the chrome-extension URL in that last file with
chrome-extension://bleakneiblnngmahabhdffihlgmbpnbp/ instead
You can test the efficacy of the plugin working by right clicking the
extension's popup and going to the console, and then test signing something
and it'll appear in the console logs.
This was only meant as a test of how native messaging works to see if I
could later use it for lastpass; my problem being I have a smartcard and
can't actually upload my key there. This in itself isn't really a polished
product :).
Mind if I ask what you two are using it for? I'd be happy to make it an
actual tool instead of a sandbox/playground.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfFs2rtqs8bm0hczaEw7pulcz6fz7kSks5t5Q7hgaJpZM4UEUpS>
.
|
I see '/opt/chrome-gpg-agent/gpg-agent-passthrough.sh' in plugins, can you share this script ?
The text was updated successfully, but these errors were encountered: