|
Size: 1446
Comment: 2.2.4 planning gets more real triggered by gnupg 2.0.27
|
Size: 2204
Comment: move 3.1.11 to End of Nov
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| (For Developers, work in progress) = Potential Roadmap-Planning |
= Gpg4win Roadmap |
| Line 4: | Line 3: |
| == 2.2.4 (Q1 2015) * update of third party libraries. ** libpng to 1.2.5 (probably no relevant changes for Gpg4win) * update of gnupg to 2.0.27 and libraries * (Claws will not be updated, because overall time pressure and lack of help with it.) |
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 10: | Line 6: |
| == next normal release? maybe 2.3.0 or 3.0.0 | 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 12: | Line 9: |
| (Not scheduled yet, may depend on available funding). Mid 2015? | The other focus is improved usability and automation. |
| Line 14: | Line 11: |
| === GnuPG 2.1 integration | == Life Cycle |
| Line 16: | Line 13: |
| * GnuPG 2.2 will be security maintained at least until the end of 2022. GnuPG can be updated individually from Gpg4win. * GnuPG 2.3 will be security maintained at least until the end of 2024. |
|
| Line 17: | Line 16: |
| === Refactoring Kleopatra | == Gpg4win 3.1.11 (End of November 2019) |
| Line 19: | Line 18: |
| See KleopatraHackability. | Tracking task: https://dev.gnupg.org/T4660 |
| Line 21: | Line 20: |
| === Shall we remove Claws-Mail from the installer? | * More quality / stability improvements, especially for GpgOL. * First start experience in GpgOL improved for S/MIME users with configurable CSR creation. * Draft encryption in GpgOL. (stable) * MSI packaging as basis for a Long Term Support Gpg4win package for customers if [[https://gnupg.com|GnuPG.com]] of Gpg4win-3.1.10. |
| Line 23: | Line 25: |
| Rationale: Claws-Mail maintains [[https://www.claws-mail.org/win32/|its own installer for windows]], which often is more current. Supporting it by building in into the Gpg4win 2.0.0 installer was a success, this helped the initiative to get a windows installer and it spread the word. |
== Gpg4win 3.2 (Q1 2020) |
| Line 27: | Line 27: |
| It makes Gpg4win easier to maintain, if we decouple the installers. There is less work to be done, especially less quality control and even some space is safed. |
* GnuPG 2.3 (Release March 2020) ** Basic ECC Support in ~Gpg~S~M (including brainpool curves) ** [[https://datatracker.ietf.org/doc/draft-ietf-openpgp-rfc4880bis|RFC4880bis]] support with new ~A~E~A~D methods (EAX, OCB) in GPG ** Support for OpenPGP v5 keys using SHA-256 fingerprints. * Better support for [[https://wiki.gnupg.org/AutomatedEncryption|automated encryption]] for ~Open~P~G~P in GpgOL * Usability improvements * Improved archive / folder support in Kleopatra (zip / Unicode filenames). |
| Line 30: | Line 35: |
| This raises is a more general question: Shouldn't we consider to make the engine (GnuPG and the core libraries) a separate package which can be updated on its own and other packages may install it on the fly? -- [[Werner Koch]] <<DateTime(2014-10-24T19:10:21Z)>> |
== Gpg4win 3.3 (early 2020) |
| Line 33: | Line 37: |
| === Additional features from wishlist | * 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. * Additional S/MIME Smartcard support. * (maybe) Rework of ~Gpg~E~X to have "ZIP Style" explorer integration for encrypted files. * Usability improvements |
| Line 35: | Line 44: |
| (Depends on funding and available time) more improvements from the [[../Wishlist|Wishlists]]. | == For each release * Update of third party libraries. * Update of Gnu~P~G and libraries. //Additional features from [[../Wishlist|wishlist]] (needs cleanup) depending on funding and available time.// |
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.
One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in Europe.
The other focus is improved usability and automation.
Life Cycle
- GnuPG 2.2 will be security maintained at least until the end of 2022. GnuPG can be updated individually from Gpg4win.
- GnuPG 2.3 will be security maintained at least until the end of 2024.
Gpg4win 3.1.11 (End of November 2019)
Tracking task: https://dev.gnupg.org/T4660
- More quality / stability improvements, especially for GpgOL.
- First start experience in GpgOL improved for S/MIME users with configurable CSR creation.
- Draft encryption in GpgOL. (stable)
- MSI packaging as basis for a Long Term Support Gpg4win package for customers if GnuPG.com of Gpg4win-3.1.10.
Gpg4win 3.2 (Q1 2020)
- GnuPG 2.3 (Release March 2020)
- Basic ECC Support in GpgSM (including brainpool curves)
- RFC4880bis support with new AEAD methods (EAX, OCB) in GPG
- Support for OpenPGP v5 keys using SHA-256 fingerprints.
- Better support for automated encryption for OpenPGP in GpgOL
- Usability improvements
- Improved archive / folder support in Kleopatra (zip / Unicode filenames).
Gpg4win 3.3 (early 2020)
- 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.
- Additional S/MIME Smartcard support.
- (maybe) Rework of GpgEX to have "ZIP Style" explorer integration for encrypted files.
- Usability improvements
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.