|
Size: 2539
Comment: Update notes for beta-215
|
Size: 2604
Comment: Link gpg4win dashboard
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Gpg4win 3.x Testversions = | = Gpg4win 3.0 test (beta) versions = |
| Line 3: | Line 3: |
| This page is intended for persons who are willing to help develop Gpg4win by testing new versions before we make a stable release. * **Important: Versions published here are experimental and should not be used in a production environment or with production keys.** * Download the latest Gpg4win test version from [[https://files.gpg4win.org/Beta/current]]. (with automatic beta numbering) |
If you want to help us developing Ggp4win, you can try one of the test versions before we do a full release. * **Since Gpg4win 3.0.0 beta276 we have release candidate** status. The Outlook-Support with MIME is considerably better then with elder Gpg4win 2.3.x versions. So it is **okay to use in production settings for normal security** requirements. As a precaution do not use it for high security settings or keys. |
| Line 7: | Line 12: |
** [[http://files.gpg4win.org/Beta/gpg4win-3.0.0-beta-current.exe|Download Gpg4win-3.0 Beta]] [[https://files.gpg4win.org/Beta/current|(sources / signature)]]** Find the list of all 3.0 beta releases at [[http://files.gpg4win.org/Beta/]] |
|
| Line 11: | Line 20: |
| * Regressions with GnuPG Modern (meaning things that worked with gpg4win-2.3.0 and no longer work). * Regressions in Kleopatra. |
* Regressions with GnuPG modern (2.1.x). - Meaning: Things that worked with Gpg4win 2.3.x but no longer work with current Gpg4win beta release. * Regressions in Kleopatra |
| Line 15: | Line 24: |
| Please send Feeback to [[http://lists.wald.intevation.org/mailman/listinfo/gpg4win-devel/|gpg4win-devel]] or open bugs in the [[https://bugs.gnupg.org|gnupg bugtracker]] | Please send feeback to [[http://lists.wald.intevation.org/mailman/listinfo/gpg4win-devel/|gpg4win-devel]] or open bugs in the [[https://bugs.gnupg.org|gnupg bugtracker]] |
| Line 17: | Line 26: |
| == Additional notes / Known issues == | |
| Line 18: | Line 28: |
| [[https://bugs.gnupg.org/gnupg/issue?%40search_text=&title=&%40columns=title&category=&version=&topic=39&id=&%40columns=id&creation=&creator=&duedate=&activity=&%40columns=activity&%40sort=activity&actor=&priority=&%40group=priority&status=-1%2C1%2C2%2C3%2C4%2C5%2C6%2C7&%40columns=status&assignedto=&%40columns=assignedto&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search|You may also want to search in the Bugtracker for known issues]] == Additional Notes == |
If you find something obvious during testing that you think would belong on a list of known issues please add it here. |
| Line 23: | Line 31: |
| For 3.0 we plan to offer a quick switch to a more automatic mode that will set the gnupg options: {{{ auto-key-locate wkd auto-key-retrieve trust-model tofu+pgp }}} |
|
| Line 31: | Line 32: |
| As this is not properly handled everywhere (especially Kleopatra's file verification dialog) this is not yet default or easily accessible. |
==== Command line Executable renamed ==== |
| Line 34: | Line 34: |
| You can add it manually to your gpg.conf. The trust-model is fully supported by GpgOL. |
The command line executable has been renamed from {{{gpg2.exe}}} to {{{gpg.exe}}} scripts or command line usage has to be modified accordingly. ==== Automatic mode ==== GnuPG now offers a more automatic mode for key discovery and trust based on the communication history. This might become default in future Gpg4win Versions. You can enable it now through Kleopatra or by adding: {{{trust-model tofu+pgp}}} to your gpg.conf This is not yet properly handled everywhere (especially Kleopatra's file verification dialog). The trust-model is fully supported by GpgOL, though. |
| Line 48: | Line 54: |
| [[https://bugs.gnupg.org/gnupg/issue?@columns=title,id,activity,priority,status,assignedto&@sort=-activity&@filter=status&@pagesize=50&@startwith=0&status=-1,1,2,3,4,5,6,7&@dispname=last-changed|For some more see the Bugtracker]] | [[https://dev.gnupg.org/u/gpg4win|see bugtracker for more known issues]] |
Gpg4win 3.0 test (beta) versions
If you want to help us developing Ggp4win, you can try one of the test versions before we do a full release.
- Since Gpg4win 3.0.0 beta276 we have release candidate status. The Outlook-Support with MIME is considerably better then with elder Gpg4win 2.3.x versions. So it is okay to use in production settings for normal security requirements. As a precaution do not use it for high security settings or keys.
- See Roadmap for our current Gpg4win release plan.
Download Gpg4win-3.0 Beta (sources / signature)
Find the list of all 3.0 beta releases at http://files.gpg4win.org/Beta/
Feedback we are most interested in
- Feedback on GpgOL
- Regressions with GnuPG modern (2.1.x). - Meaning: Things that worked with Gpg4win 2.3.x but no longer work with current Gpg4win beta release.
- Regressions in Kleopatra
- Problems with decrypt / verify and file extension integration.
Please send feeback to gpg4win-devel or open bugs in the gnupg bugtracker
Additional notes / Known issues
If you find something obvious during testing that you think would belong on a list of known issues please add it here.
General
Command line Executable renamed
The command line executable has been renamed from gpg2.exe to gpg.exe scripts or command line usage has to be modified accordingly.
Automatic mode
GnuPG now offers a more automatic mode for key discovery and trust based on the communication history. This might become default in future Gpg4win Versions. You can enable it now through Kleopatra or by adding: trust-model tofu+pgp to your gpg.conf
This is not yet properly handled everywhere (especially Kleopatra's file verification dialog). The trust-model is fully supported by GpgOL, though.
GpgOL
- It is not possible to modify mails (e.g. moving / flagging the mail) while they are shown decrypted. To workaround this unselect the crypto mail and then make changes through the right click context menu or move it with drag and drop.
- Crypto mails forwarded as attachment are not properly handled.
- The certificate selection dialog sometimes opens in the background and needs an overhaul.
- Localization is incomplete