We won't apply any fixes to the cpp, QT, or Python language bindings in the 1.24 branch. The Qt branch has been factored out to the gpgmeqt project on request from the KDE folks. 8And yest we should add projtecs (tags) for gpgmepp and gpgmeqt
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mon, Apr 28
Sun, Apr 27
The report is correct but it does not make sense to fix it. If you want to use a concrete expiration date just enter the IS date at the prompt; use ? at the prompt for a short description.
Sat, Apr 26
Fri, Apr 25
Fixed:
Thu, Apr 24
Thanks for the patch but I think it is better to fix this in yat2m. I created a new tag for bugs related to it.
turned out that not the flowcrypt encryption is the issue here. The cause seems to be the usage of Proofpoint "Email Warning Tags".
Wed, Apr 23
This is really a minor thing and and it is actually true if you also sign something.
Tue, Apr 22
BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.
No more octals .-)
regarding the 403: one has to try the correct page AFAIK. Didn't research which one, look in the update checker code.
doc/HACKING says it's OK to use variadic arg macros (from C99 features).
If it's OK, this patch can fix the initialization (which silences GCC 15 warnings):
Mon, Apr 21
Sun, Apr 20
Sat, Apr 19
Good morning,
I stumbled upon this when digging through old Debian bug reports against 1.4 and checking whether they still applied to 2.4. This one really still applies.