Size: 886
Comment: Rough roadmap for 3.2.0
|
Size: 1847
Comment: gpg already has authenticated encryption. What we want to have are modern modes.
|
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) | 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 6: | Line 9: |
[[https://dev.gnupg.org/T3742|See the tracking task in dev.gnupg.org]] | The other focus is improved usability and automation. |
Line 8: | Line 11: |
Highlights: * New sign / encrypt handling in GpgOL * Notepad for Kleopatra * Basic WKS Support in GpgOL |
== Gpg4win 3.1.6 (early March 2019) |
Line 13: | Line 13: |
Beta: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe | See the [[https://dev.gnupg.org/T4264|Tracking Task]] |
Line 15: | Line 15: |
== Gpg4win 3.1.x (as needed) | General focus: GpgOL and bugfixes. * More but less secure automation support in GpgOL for OpenPGP (default off) * Basic support to read encrypted subjects in GpgOL * Better attachment handling in GpgOL * Option to decrypt permanently in GpgOL * Update to latest KDE and Qt with performance improvements for Kleopatra. |
Line 17: | Line 22: |
* Bugfixes / regression fixes. | == Gpg4win 3.2 (late summer 2019) |
Line 19: | Line 24: |
== Gpg4win 3.2.0 (Summer 2018) | * GnuPG 2.3 ** Basic ECC Support in GpgSM (including brainpool curves) ** rfc4880bis support with new AEAD methods (EAX, OCB) in GPG * Better support for [[https://wiki.gnupg.org/AutomatedEncryption|automated encryption]] for OpenPGP in GpgOL * Improved archive / folder support in Kleopatra * Usability improvements * S/MIME Adressbook integration for GpgOL |
Line 21: | Line 32: |
* 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. |
== 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 |
Line 29: | Line 45: |
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.
Gpg4win 3.1.6 (early March 2019)
See the Tracking Task
General focus: GpgOL and bugfixes.
- More but less secure automation support in GpgOL for OpenPGP (default off)
- Basic support to read encrypted subjects in GpgOL
- Better attachment handling in GpgOL
- Option to decrypt permanently in GpgOL
- Update to latest KDE and Qt with performance improvements for Kleopatra.
Gpg4win 3.2 (late summer 2019)
- GnuPG 2.3
- Better support for automated encryption for OpenPGP in GpgOL
- Improved archive / folder support in Kleopatra
- Usability improvements
- S/MIME Adressbook integration for GpgOL
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.