|
Size: 863
Comment: Update roadmap with a 3.1.3 release
|
← Revision 128 as of 2023-09-21 13:49:59 ⇥
Size: 1535
Comment: small update, now that 4.2.0 is there
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == Gpg4win 3.1.3 (July 2018) | This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 5: | Line 6: |
| [[https://dev.gnupg.org/T4029|Tracking Task]] | The [[https://dev.gnupg.org/project/board/117/|Release Info workboard]] sometimes has more features for upcoming GnuPG or Gpg4win releases. |
| Line 7: | Line 9: |
| * Improved error handling in Kleopatra, especially for MDC errors. * New options in GpgOL that might be made default in 3.2.0 * Moving Mails in GpgOL ;-) * Lots of other fixes. |
== Life Cycle * For the crypto engine, see [[https://gnupg.org/download/index.html#end-of-life|GnuPG's EOL]]. Note that GnuPG can be updated for Gpg4win by using the simple Gnu~PG installer. |
| Line 12: | Line 12: |
| == Gpg4win 3.2.0 (Fall 2018) | * Gpg4win 3.1.x is no longer maintained. A technical similar software is the BSI approved [[https://gnupg.com/gnupg-desktop.de.html|GnuPG VS-Desktop®]]; available for Windows and Linux as part of a support contract. |
| Line 14: | Line 14: |
| General focus: GpgOL and improved automation. | == Gpg4win 4.2.x (tba) * Fixing important defects. * Will be released as needed. * New features (that keep the user experience). |
| Line 16: | Line 19: |
| * Defaulting to automated trust model for GpgOL. (more implementation of the [[AutomatedEncryption]] concept) * Automatic encryption selection if keys are available in GpgOL by default. * Probably with a GnuPG 2.3.x * Updates to all libraries * Kleopatra usability improvements. |
== Ongoing developments * Authenticated encryption support for S/MIME in Gpg~S~M * Better Microsoft Exchange / GAL integration for GpgOL (fingerprints and encryption info as attributes in the GAL) * Further improvements to automated encryption -> default on. * Usability and automation improvements * One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in [[https://dev.gnupg.org/T4363|Europe]]. |
| Line 23: | Line 30: |
| * Update of third party libraries. * Update of gnupg and libraries. |
* Update of third party libraries. * Update of Gnu~P~G and libraries. |
Gpg4win Roadmap
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details.
The Release Info workboard sometimes has more features for upcoming GnuPG or Gpg4win releases.
Life Cycle
- For the crypto engine, see GnuPG's EOL. Note that GnuPG can be updated for Gpg4win by using the simple GnuPG installer.
- Gpg4win 3.1.x is no longer maintained. A technical similar software is the BSI approved GnuPG VS-Desktop®; available for Windows and Linux as part of a support contract.
Gpg4win 4.2.x (tba)
- Fixing important defects.
- Will be released as needed.
- New features (that keep the user experience).
Ongoing developments
- Authenticated encryption support for S/MIME in GpgSM
- Better Microsoft Exchange / GAL integration for GpgOL (fingerprints and encryption info as attributes in the GAL)
- Further improvements to automated encryption -> default on.
- Usability and automation improvements
- One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in Europe.
For each release
- Update of third party libraries.
- Update of GnuPG and libraries.
Additional features from wishlist (needs cleanup) depending on funding and available time.