|
Size: 2962
Comment: Create page for 3.x testversions
|
← Revision 21 as of 2017-08-24 11:58:47 ⇥
Size: 2542
Comment: Make clear that the software has release candidate status and re-using the phrase "release candidate" to find the correct download link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Gpg4win 3.x Testversions = | = Gpg4win 3.0 pre-release 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. | If you want to help us with Ggp4win, you can try one of the test versions before we declare it stable. |
| Line 5: | Line 6: |
| **Versions published here are experimental and should not be used in a production environment or with production keys.** | * Since Gpg4win 3.0.0 beta276 ** the software has release candidate** status. The Outlook-Support with MIME is considerably better than 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 11: |
| The latest Version can be found [[https://files.gpg4win.org/Beta/current|on the downloads page]]. | * See [[Gpg4win/Roadmap|roadmap]] for our current Gpg4win release plan. |
| Line 9: | Line 13: |
| For our current release plan please refer to the roadmap [[Gpg4win/Roadmap|Roadmap]] | Release Candidate: ** [[https://files.gpg4win.org/Beta/current|Download Gpg4win-3.0 Beta]] ** Find the list of all 3.0 beta releases at [[https://files.gpg4win.org/Beta/]] |
| Line 14: | Line 20: |
| * Regressions with GnuPG Modern (meaning things that worked with gpg4win-2.3.0 and no longer work). | * 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. |
| Line 16: | 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 18: | Line 26: |
| == Known Issues == | == Additional notes / Known issues == |
| Line 20: | Line 28: |
| * HKPS is not yet supported in gnupg 2.1 for windows. You can use the TOR support as alternative. * There is no localization for gnupg included. * [[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|For some more see the Bugtracker]] * Kleopatra's about dialog lists the gpg4win version as 2.1.0 guessed |
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. |
| Line 27: | Line 45: |
| We tested Outlook 2010 - 2016 using an Exchange 2013 Server and with an IMAP Server. | * 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 |
| Line 29: | Line 54: |
| * Signed inline (not encrypted) signed is currently not handled. You have to use the clipboard commands for this. * GpgOL breaks multipart/signed (mime signed not encrypted) signatures for other clients if the inner MIME boundaries were on a single line. * GpgOL might break S/MIME opaque signed signatures for other clients (including Outlook) * The inline reply / forward / draft editors of Outlook 2016 have no UI and don't work yet for encryption / signing. * If you close Outlook when looking at a decrypted mail outlook asks you to save your changes, twice. (Won't be saved in plaintext). * When problems occur and GpgOL does not know what to do it will replace the plaintext by a blue "This message is encrypted box" ** The wording in that box needs to be fixed ** Failed decryption should be handled more gracefully ** This error might be synced to the server ** You generally should not see that. Consider reporting a bug. * When opening a Mail in it's own Window it will be shown as empty after you close the reader window. You can switch to another mail and back. * Localization is not completely done (and we are still doing to many string changes for that.) * Outlook is still blocked while crypto is done (nothing new) * We don't have UI in the reader / messagelist to show the Signature / Encryption state after verification. |
[[https://dev.gnupg.org/u/gpg4win|see bugtracker for more known issues]] |
Gpg4win 3.0 pre-release versions
If you want to help us with Ggp4win, you can try one of the test versions before we declare it stable.
- Since Gpg4win 3.0.0 beta276 the software has release candidate status. The Outlook-Support with MIME is considerably better than 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.
Release Candidate: Download Gpg4win-3.0 Beta
Find the list of all 3.0 beta releases at https://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