Size: 886
Comment: Rough roadmap for 3.2.0
|
Size: 1562
Comment: Clarify state of gpg4win 3.1
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
|
Line 4: | Line 6: |
== Gpg4win 3.1.0 (Mid / End March 2018) | The [[https://dev.gnupg.org/project/board/117/|Release Info workboard]] sometimes has more features for upcoming GnuPG or Gpg4win releases. |
Line 6: | Line 9: |
[[https://dev.gnupg.org/T3742|See the tracking task in dev.gnupg.org]] | == 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 8: | Line 12: |
Highlights: * New sign / encrypt handling in GpgOL * Notepad for Kleopatra * Basic WKS Support in GpgOL |
* 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 13: | Line 14: |
Beta: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe | == Gpg4win 4.1.0 (tba) |
Line 15: | Line 16: |
== Gpg4win 3.1.x (as needed) | == Gpg4win 4.0.x (2022) * Fixing important defects. * Will be released as needed. * New features (that keep the user experience). |
Line 17: | Line 21: |
* Bugfixes / regression fixes. | |
Line 19: | Line 22: |
== Gpg4win 3.2.0 (Summer 2018) | == Ongoing developments |
Line 21: | Line 24: |
* File support for Kleopatras notepad. (Read / Write of simple PGP/MIME and S/MIME messages) * Defaulting to automated trust model for GpgOL. (more implementation of the [[AutomatedEncryption]] concept) * Much faster keyring access through GnuPG. |
* 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 26: | Line 32: |
* 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.1.0 (tba)
Gpg4win 4.0.x (2022)
- 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.