-
Notifications
You must be signed in to change notification settings - Fork 78
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
Keychain backend not working on macOS #302
Comments
As a temporary workaround, you can add the passphrase manually to the macOS keychain. Then set |
Hi @mlangenberg First of all, thanks for submitting the bug. To be honest, I have not tested the macOS keychain integration. The 99designs/keyring library documentation is pointing to several configuration keys that are probably missing in your setup. I have to figure out what config items are missing. |
Okay, let me know if I can test something for you. And thanks for the effort in protecting the credentials to my Google Photos library. |
Hi @mlangenberg
But I haven't seen it on your issue. Could you run again the
|
Sure, here is the output.
|
I also compiled from source (a1ba508), to see if that made any difference. This gives a more useful error message, so it partly has to do with the homebrew build. Although keychain support still does not work.
Full stack trace
|
Hi @mlangenberg Thanks a lot for all the information that you have already submitted. It has helped me to point where the problem is. Can you test something more?
|
Hey @pacoorozco, the 'file' secrets backend does work for the compiled homebrew package. But when compiling from source myself, the 'file' secrets backend also returns the same error message and stracktrace as the 'keychain' secrets backend. |
On macOS Catalina (10.15.7) building from source resulted in SIGSEV when reading the password from stdin. See gphotosuploader#302 for details. Upgrading the golang.org/x/term to the latest version fixes this problem.
FYI, after upgrading golang.org/x/term, the keychain secrets backend also works for my own compilation. Do you think that this will also fix the issue for the binary that is distributed through homebrew? |
Hi @mlangenberg Yes, It could be... I was testing locally the "main" branch code and It was failing to me as-well. So there's a problem with the dependency. I'll do my best to update it an release a new version. I'll let you know it to ask the favor of testing it... Thanks a lot for your time investment. |
Hi @mlangenberg I've merged your PR (thanks a lot) and I've released a new version. Would you be so kind to test the homebrew binary?* |
With
|
Uhm... good finding @mlangenberg I'm not an expert in cross-compilation. As far as I seen this enables the use of CGO, which is required to compile If I added it to my I need to investigate more about this. AFAIK compiling the main branch in your macOs should provide you a binary able to use |
@mlangenberg Would you be able to test these binaries (wo/ homebrew). |
When I download the binaries, the keychain backend does not work.
When I compile from source with
I'm sorry that we are not making much progress on this. To be honest, my workaround to set I did come across this comment: 99designs/keyring#78 (comment) |
Describe the bug
The keychain backend is not working on macOS.
To Reproduce
Steps to reproduce the behavior:
brew install gphotosuploader/tap/gphotos-uploader-cli
gphotos-uploader-cli init
config.hjson
and setSecretsBackendType
tokeychain
.gphotos-uploader-cli push
Expected behavior
Be able to run the program without further user interaction whilst having the Google Photos credentials safely stored in the macOS keychain.
Actual behavior
Desktop & Client versions (please complete the following information):
The text was updated successfully, but these errors were encountered: