Today
Please briefly try to reproduce on Windows with Gpg4win 5.0.2. At lot has changed since this ticket was created so that it might be fixed already.
I cannot reproduce the empty dialog on Linux with the current build. I always see a correct result dialog for the readable file.
We use individual texts now that all follow the pattern "Detailed results of import from ..." for import from file (file name is displayed), clipboard, notepad, smart card, WKD (URL is displayed), server ("keyserver" or "LDAP server").
Note: This isn't included in Gpg4win 5.0(.2).
Note: This isn't included in Gpg4win 5.0(.2).
Note: This isn't included in Gpg4win 5.0(.2).
Note: This isn't included in Gpg4win 5.0(.2).
I stand partially corrected. Apparently, pinentry-efl also sets close_button. For Gpg4win that's irrelevant because we ship pinentry-qt (and pinentry-w32) which doesn't have this IMHO contra-intuitive behavior.
Upstream MR for reading system config files before user config files: https://invent.kde.org/frameworks/kconfig/-/merge_requests/436
pinentry-tty and pinentry-curses support GPG_ERR_FULLY_CANCELED by Ctrl-C. But other pinentry implementations have no support (only GPG_ERR_CANCELED).
I'd also like to point out that changing the error code from GPG_ERR_CANCELED to GPG_ERR_FULLY_CANCELED could cause regressions in applications.
Merge request for KMessageBox: https://invent.kde.org/frameworks/kwidgetsaddons/-/merge_requests/339
How do you want to decide whether to show two "Cancel" buttons? How would you call those two "Cancel" buttons? For decryption I can imagine that for example "Try Next Key" and "Cancel Decryption" (or even just "Cancel") would make clear what happens.
Yesterday
Any further improvements will have to go in a new ticket when we have a plan. I'll close this one.
ok, lets go with the message box.
Q1 stays like it is, for Q3 @tfry made a merge request to wrap after 120 characters. Please add a link to this.
Relevant part from T6793: Cleanup temporary files / dirs with decrypted content:
If this definition is OK
@bernhard Thank you for the link.
Tue, Mar 10
What is an "incomplete team key" - a standard offline secret key (i.e. one with only secret subkeys)?
It would be used for key creation just like the legacy options PGPKeyType and RSAKeySizes were used (and still can be used but only for RSA with different key sizes).
If you specify a primary key the primary key shall be deleted. If there is only an offline or token based primary it can't be deleted. This is what the user requested. We can't change this because otherwise subkeys might be unintentionally deleted.
I guess the behavior changed with gpg 2.4, i.e. "With gpg 2.4 (or later), ..."
Shall that be used for key creation or shall a warning be displayed when a non-allowed key is used (receive or send)?
why gpg 2.4? Don't you mean 2.6? I'll add the proper 2.6 tag for avoiding confusion
FYI: We had a VSD support case today where the user complained that they thought the Admin PIN would work because of the tooltip text but it was not accepted. They needed to give the PUK, which is consistent with the state given in this ticket.
Hi @gniibe,
thanks for making progress on the issue.
I was wrong. gpg (scdaemon) needed to be fixed with more changes for the interaction with pinentry.
I pushed my patch for gpg, since it does not break anything, just allow empty passphrase input (to skip).
I also pushed my patch for gpgme. I believe that it's correct.
gpg 2.2 does: when it sees PKT_PUBKEY_ENC it asks a user to try decrypting the session key. when it sees PKT_SYMKEY_ENC it asks a user to try decrypting the encrypted session key by passphrase. When one of tries successes, it use the result (the session key) to decrypt PKT_ENCRYPTED_* packet. When there are multiple PKT_PUBKEY_ENC and PKT_SYMKEY_ENC, gpg 2.2 handles sequentially.
Mon, Mar 9
And *.pub is used for Microsoft Publisher documents
Panel Used By
| Dashboard | Restricted Dashboard |