| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Credit: https://github.com/chjj/compton/issues/189
|
| |
|
| |
|
|
|
|
|
|
|
| |
* do not hack to force to use `pinentry-curses` with custom `pinentry`
and `gpg2-x11` shims
* explain to use the `pinentry-gtk-2`, which will fallback to text mode
* simply launch `gpg-agent` with `gpgconf --launch`
|
| |
|
|
|
|
| |
Credit: https://blog.mrloop.com/workflow/2017/02/09/pin-entry.html
|
|
|
|
|
|
|
|
|
| |
For a NFS-shared-home cluster, once login to a node and start the
gpg-agnet, then the original gpg-agent on the master will quit, which
causes the annoying agent connection error.
Simply ignore the error and do not try to launch the agent, which is of
little use for the above cases.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|