|
Size: 914
Comment: Some more things for the road
|
Size: 1936
Comment: improve hint on how to update GnuPG for Gpg4win
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| (For Developers, just an initial stub, work in progress) = Potential Roadmap-Planning |
= Gpg4win Roadmap |
| Line 4: | Line 3: |
| == 2.2.2 | This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 6: | Line 6: |
| * screenreader ability for kleo * update of third party libraries * update of gnupg version and libraries * fix for dll load startup problems with kleopatra on some systems * possibly fix exchange address recognition in gpgOl for outlook 2010/2013 === Shall we remove Claws-Mail from the installer? |
== 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 14: | Line 9: |
| 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.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 18: | Line 11: |
| 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. |
== Gpg4win 4 (Q4 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 22: | Line 23: |
| == next normal release? maybe 2.3.0 | == 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]]. == 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.
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 (Q4 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
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.