|
Size: 1415
Comment: 2.2.4 is out. Plan 2.2.5 This also removes the libpng update as the rationale for this is unclear to me.
|
Size: 1854
Comment: Update roadmap
|
| 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.5 (Q2 2015) * update of third party libraries. * update of gnupg 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 or 3.0.0 (Not scheduled yet, may depend on available funding). Mid 2015? |
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 13: | Line 9: |
| === GnuPG 2.1 integration * Probably something for a 3.0 release |
The other focus is improved usability and automation. |
| Line 16: | Line 11: |
| == Life Cycle | |
| Line 17: | 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. |
| Line 19: | Line 16: |
| See KleopatraHackability. | == Gpg4win 4 Beta (Q3 2020) * 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 21: | Line 27: |
| === Shall we remove Claws-Mail from the installer? | == Gpg4win 4 Final (Q4 2020) * Feedback and improvements from the Beta |
| Line 23: | Line 30: |
| 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. |
== Ongoing developments |
| Line 27: | Line 32: |
| 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. |
* 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 |
| Line 30: | Line 37: |
| 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)>> |
== For each release * Update of third party libraries. * Update of Gnu~P~G and libraries. |
| Line 33: | Line 41: |
| === Additional features from wishlist (Depends on funding and available time) more improvements from the [[../Wishlist|Wishlists]]. |
//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 4 Beta (Q3 2020)
- 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 Final (Q4 2020)
- 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.