Skip to content
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

Secure keyring storage doesn't work with KeepassXC #2236

Open
Real-Gecko opened this issue Aug 5, 2024 · 9 comments
Open

Secure keyring storage doesn't work with KeepassXC #2236

Real-Gecko opened this issue Aug 5, 2024 · 9 comments

Comments

@Real-Gecko
Copy link

Real-Gecko commented Aug 5, 2024

Describe the bug

When using KeepassXC Freedsktop.org Service integration feature infisical-cli is unable to get secrets during infisical init

To Reproduce

Steps to reproduce the behavior:

  1. Setup KeepassXC as your default system keyring
  2. Use infisical login to login to your server
  3. Navigate to project and run infisical init
  4. Observe error: failed to fetch creditnals from keyring because [err=something went wrong, failed to retrieve value from system keyring [error=org.freedesktop.Secret.Error.IsLocked]]

Expected behavior

Retreive credintials from KeepassXC

Platform you are having the issue on:

Arch Linux

Additional context

Looks like known problem with go-keyring
cli/cli#8691
zalando/go-keyring#88

@maidul98
Copy link
Collaborator

maidul98 commented Aug 5, 2024

This has been resolved in CLI version v0.27.0. Can you please confirm?

@Real-Gecko
Copy link
Author

Alas no:
image
I've deleted Infisical record from DB and retried everything from scratch, after login a new record is successfully created, but init still fails
image

@maidul98
Copy link
Collaborator

maidul98 commented Aug 5, 2024

Can you please run the following command infisical vault set file --passphrase <your-passphrase> and try again?

@Real-Gecko
Copy link
Author

image

@maidul98
Copy link
Collaborator

maidul98 commented Aug 7, 2024

Hey @Real-Gecko , the previous release of the CLI did not include the change. Please update the CLI once more please

@Real-Gecko
Copy link
Author

image
But there's definitely a progress, DB was locked when I issued command, and keepass asked confirmation for request. However result is not positive yet.

@maidul98
Copy link
Collaborator

maidul98 commented Aug 7, 2024

You will need to reset the cli by running infisical reset then try again

@Real-Gecko
Copy link
Author

realgecko@rog-strix ~/W/O/f/backend (master)> infisical reset
Reset successful
realgecko@rog-strix ~/W/O/f/backend (master)> infisical login
✔ Self Hosting
✔ Domain: ***********█


To complete your login, open this address in your browser: ***********/login?callback_port=40353 


Once login is completed via browser, the CLI should be authenticated automatically.
However, if browser fails to communicate with the CLI, please paste the token from the browser below.


Token: Browser login successful
>>>> Welcome to Infisical! You are now logged in as *********** <<<< 

Quick links
- Learn to inject secrets into your application at https://infisical.com/docs/cli/usage
- Stuck? Join our slack for quick support https://infisical.com/slack
realgecko@rog-strix ~/W/O/f/backend (master)> infisical init
error: we couldn't find your logged in details, try running [infisical login] then try again
Unable to get your login details


If this issue continues, get support at https://infisical.com/slack
realgecko@rog-strix ~/W/O/f/backend (master) [1]> 

When I run infisical reset record disappears from DB, when I run infisical login it appears after successful login, but result is still the same.

@AlanD20
Copy link

AlanD20 commented Aug 17, 2024

Hey! I stumbled upon this issue from one of my related issues. Looks like the go-keyring for this cli project is not using the go-keyring-v0.2.5. This issue was fixed at https://github.com/zalando/go-keyring/releases/tag/v0.2.5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants