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

use GPGME #5

Open
nullobsi opened this issue Jan 22, 2022 · 2 comments
Open

use GPGME #5

nullobsi opened this issue Jan 22, 2022 · 2 comments
Assignees

Comments

@nullobsi
Copy link
Owner

Using pass directly as a subprocess feels fragile and prone to error (#2)

Pros:

  • direct support for encrypting/decrypting
  • error handling
  • less hacky

Cons:

  • git commit would not be made
  • have to manually support .gpg-id
@nullobsi nullobsi self-assigned this Jan 22, 2022
@Thaodan
Copy link

Thaodan commented Sep 6, 2022

Have you looked into use QGPGME or LibKleo (more high lvl)? Plus would be a higher lvl API suited for C++ rather than using the C API.

I think this should be probably an item split into different points:

  • Replace pass by doing the pass functionality manually
    • Indexing - Traverse password-store to find password
    • Decrypt password
    • Write password and encrypt
  • Call either gpg or gpgme. I would first go by calling gpg and then gpgme since you can't really avoid calling external processes until you also use libgit for git commit.

@nullobsi
Copy link
Owner Author

nullobsi commented Sep 7, 2022

I haven't looked into other options, no. But definitely a higher level API would be better to use :)

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

2 participants