|
Size: 800
Comment: 3.1.1 will be released next week.
|
Size: 1418
Comment: As 4.0.0 was released, add 4.0.x and 4.1.0
|
| 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.1 (KW 17 2018) | == 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 6: | Line 9: |
| [[https://dev.gnupg.org/T3899|See the tracking task in dev.gnupg.org]] | * Gpg4win 3.1.x with GnuPG 2.2 will be maintained as part of GnuPG VS-Desktop [[https://gnupg.com/gnupg-desktop.de.html|GnuPG Desktop]] at least until Gpg4win 4 gains approval for restricted communication in Germany. |
| Line 8: | Line 11: |
| Highlights: * GPGSM: Fixed several CRL handling issues. * GpgOL: Fixed a regression when decrypting signed / encrypted mails in a specific format, when the signers key was not available. * Fixes for mkportable |
== Gpg4win 4.1.0 (tba) |
| Line 13: | Line 13: |
| == Gpg4win 3.2.0 (Summer 2018) | == Gpg4win 4.0.x (2022) * Fixing important defects. * Will be released as needed. * New features (that keep the user experience). |
| Line 15: | Line 18: |
| * 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) |
== 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 20: | Line 30: |
| * Update of gnupg and 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.
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 with GnuPG 2.2 will be maintained as part of GnuPG VS-Desktop GnuPG Desktop at least until Gpg4win 4 gains approval for restricted communication in Germany.
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.