|
Size: 887
Comment: Remove issues done with 2.2.2 and move over generic stuff to 2.2.3
|
Size: 2163
Comment: update 3.1.16 is coming with a higher chance
|
| 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.3 * update of third party libraries * update of gnupg version 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 9: | Line 6: |
| == next normal release? maybe 2.3.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 11: | Line 9: |
| The other focus is improved usability and automation. | |
| Line 12: | Line 11: |
| === GnuPG 2.1 integration | == Life Cycle |
| Line 14: | Line 13: |
| === Refactoring Kleopatra | * 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.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 16: | Line 17: |
| See KleopatraHackability. | == Gpg4win 3.1.16 (Q2 2021) At least with https://dev.gnupg.org/T5248 changed to a warning. |
| Line 18: | Line 20: |
| === Shall we remove Claws-Mail from the installer? | == Gpg4win 4 Beta (April 2021) * GnuPG 2.3 * Improved Subkey handling in GpgOL and Kleopatra to better support "rules of representation (Vertreterregeln)". * New smartcard handling with support for multiple smartcards. * Additional Smartcard support for PIV Application - with GUI * 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 |
| Line 20: | Line 31: |
| 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 4 (2021) * Feedback and improvements from the Beta |
| Line 24: | Line 34: |
| 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. |
== 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 improvements == 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.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 3.1.16 (Q2 2021)
At least with https://dev.gnupg.org/T5248 changed to a warning.
Gpg4win 4 Beta (April 2021)
- GnuPG 2.3
- Improved Subkey handling in GpgOL and Kleopatra to better support "rules of representation (Vertreterregeln)".
- New smartcard handling with support for multiple smartcards.
- Additional Smartcard support for PIV Application - with GUI
- 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
Gpg4win 4 (2021)
- Feedback and improvements from the Beta
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 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.