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
Add KBI0012: annex encryption & GPG pinentry #44
Conversation
kbi/0012/index.rst
Outdated
.. index:: | ||
single: git-annex; encryption | ||
|
||
KBI0012: Annex encryption & gpg pinentry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can make it more clear in the title that this KBI is about resolving an issue, and not, e.g., about how to set encryption up? Maybe its also useful to cross-reference your usecase in the handbook as a pointer: http://handbook.datalad.org/en/latest/usecases/encrypted_annex.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point - updated.
The intro explains that the KBI is about resolving a very specific issue, and not about setting up encryption in general - for the latter, the user is pointed to the Handbook use case. Suggested-by: Adina Wagner <adina.wagner@t-online.de>
Makes it clear that the error is because there was no way to ask for the passphrase.
LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me, thx!
This short KBI is converted from my own notes. The origin was an issue on MacOS which was discussed during office hours at some point in March 2023 (and also demonstrated on our cluster).