New answers tagged gpg
If a little redirection is acceptable, then pv is a good way in general to achieve this type of thing, but GPG has (unsurprisingly) /dev/random hard-coded into it, so that's not going to work here without some hackery. On linux, using unshare to temporarily overlay /dev/random is probably the least disagreeable, though it requires root permissions : mkfifo ...
The 0x prefix determines that the following is either a short ID, a long ID or a fingerprint. At least with GnuPG 2.0.22 this seems not to make any difference (I don't know though whether this has always been the case). If you use a selection string that looks like a short ID, long ID or fingerprint then it is ignored as a text search string. You can put ...
NOTE: Before I begin, all the representations here are hexidecimal only. There isn't any other representation. Key IDs The man page seems pretty clear on where these values are coming from. The key IDs are a portion of the SHA-1 fingerprint. The key Id of an X.509 certificate are the low 64 bits of its SHA-1 fingerprint. The use of key Ids is just ...
I have done some investigation and the result is surprising to me but simple: When called this way gpg doesn't communicate with gpg-agent at all! gpg is capable of doing all these operations on its own. But if gpg-agent doesn't even know that something has happened then it can hardly know a passphrase it didn't know before.
Top 50 recent answers are included