- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 12 2024
Right. I think this task inherited the assignee from its parent task.
Done.
Isnt this more of a task for werner? But if you could create a patch that would be great, too
this should be easy since we already start gpg-agent on start
needs to be fixed soon. But we don't have a tag for Gpg4win 5 or whatever we call a kf6 based gpg4win.
Mar 11 2024
This can be tested with Kleopatra by configuring an invalid keyserver and then updating an OpenPGP certificate.
Instead of "The key hasn't changed." Kleopatra now displays "The update was skipped because no keyserver is configured."
It could have been discussed whether this makes sense. However, we can't change it anymore because it would change the behaviour. Consider a cron job which looks into a directory with keyids and imports them from a keyserver. It is totally fine if the script returns success if no keys are available.
In T6761#183780, @ebo wrote:But in the case "Refresh OpenPGP keys" (in Kleopatras certificate Details) there is no error message but instead ~"the key is unchanged".
Your above excerpt for the log is not a bounce. Can you please give me an example from a rejected bounce? Noet that BATV is also in use.
Mar 10 2024
There is no way to recover it?
The mail server is misconfigured. no SPF <> not allowed.
That is on purpose. Please add an SPF record to your site. If there is really really a problem for you with that, write me off tracker.
See T7034
Sorry, this is not a help line but a bug tracker. If you lost or forgot your password you are screwed up.
Mar 9 2024
Mar 8 2024
I have also not found a straightforward way to correct a cross-signature that was made with a weak digest algorithm using GnuPG.
I still need to land the fix for the kwallet problem, but that can be done first thing monday so nothing that really blocks a release
with Version 3.2.2.231170+git~ (Gpg4win-4.3.1-beta12):
- no error message any more with keyserver = none
- correct error message when choosing "publish on server"
But in the case "Refresh OpenPGP keys" (in Kleopatras certificate Details) there is no error message but instead ~"the key is unchanged".