How to report a bug

Step-by-step instructions.

1. Check whether you are using the latest version of Gpg4win

The download button on top of the Gpg4win homepage shows the current version.

You can find your installed Gpg4win version number in Kleopatra under Help->About Kleopatra. Should this not be the latest version, please update and check if the issue persists.

2. Check whether the problem is already reported

Search through the list of open bugs and try to identify whether one of the entries already describes your problem. You should also check out the forum, too.

3. Create a new report

If you should already have an account at dev.gnupg.org you can report the problem using this form. As normal registration is disabled due to spam, the easiest option is to report the issue on the forum. After verification someone will create a task for it in the dev tracker. For reporting a bug in the tracker yourself, please ask on one of the gnupg lists lists for an account and provide handle, shown name, and a mail address.

Please note the following:

Provide version numbers

If you report a new bug or add comments to an existing bug report, describe the exact version of Gpg4win, the Windows System, and, if appropriate, of MS Office and Outlook.

Notes on how to reproduce the bug

If possible provide a step by step method on how you can reproduce the bug.

Add debug information

If appropriate, attach a debug log of the procedure where you produced the bug. Look at the instructions for the several Gpg4win components in the Gpg4win Compendium.

If you feel able to, just send an excerpt with the relevant information.

Private reports / security issues

If you do not want to publicly divulge the contents of a report, e.g. because that would leak private information or if you consider an issue a severe security problem, the security contact can be found on this page.