See for T6545 for a new request to support IDP.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 22 2023
We had one request to support this back in 2017 but it was closed because the respective CA stopped using this extension. See T2039.
I found the case of X.509, which also uses fixed length output for RSA-PSS and ECDSA: https://www.rfc-editor.org/rfc/rfc8692.html
The use cases are:
- oPassphraseFD for gpgsm, gpg
- oStatusFD for gpg-auth, gpg-wks-client, gpg-card, gpg-pair-tool, gpgtar, gpgconf, gpgsm, gpg, gpgv
- oLoggerFD for gpgsm, gpg, gpgv
- oAttributeFD for gpg
- oCommandFD for gpg
- oOverrideSessionKeyFD for gpg
Jun 21 2023
Removed parent task because this issue doesn't really block T5478: Kleopatra: Performance problems decrypting and encrypting large Archives.
ready for testing
Done. Can be tested and closed with T5478: Kleopatra: Performance problems decrypting and encrypting large Archives.
ok, then this is resolved
Yes, that was the intention eva reminded me that I had not done this yet, but the next releases of GnuPG VSD will have action/help_contents=false in their action restrictions.
I think that for VSD the Help action is disabled via the configuration because you have alternative documentation to the Kleopatra Handbook. @aheinecke?
Which is the same URL as the F1 Help page thus probably opened via QProcess?
It works, including the nice message box, for most links in the Help menu, but not for the Kleopatra Handbook.
Thank you. Now, I see the reason for conf/ sub directory.
Jun 20 2023
See T4168 and rMecfa48fffa9 for the reason why we need this conf directory. Thus (1) is not an option.
Thank you for having a look into that! The proposed patch looks good. Should we have this change also in master?
I vote for (1). All other GnuPG projects put config.h[.in] in the top directory.
Thank you.
Applied to master, 2.4 branch and 2.2 branch.
Thank you.
Applied to master, 2.4 branch, and 2.2 branch.
Jun 19 2023
rGb1ecc8353ae3 is just what I meant, so that we can recommend such an option in the future as a workaround until a new update becomes available which supports such an extension.
Nah, the description for that extension is pretty strict and I won't feel comfortable to just ignore it. BTW there is also T6398 (nameConstraints) which needs support. But for debugging a ignore extension makes sense.
For support reasons I would say that it might make sense to also ignore the extensions from "ignore-cert-extension" when checking CRLs?