Remove refresh keys again. You can Refresh your keys through Tools -> Refresh ... Certificates. (Someone told me this was missing)
completed entry to Kleo about clipboard sign&encrypt
|Deletions are marked like this.||Additions are marked like this.|
|Line 62:||Line 62:|
=== Clipboard: Integrated Sign&Encrypt support
User may want to use the clipboard for encrypting and signing text (as it is possible with files) to be able to secure
confidentiality and integrity. For a description of user problems with Gpg4win 2.2.4 see [[https://wald.intevation.org/forum/forum.php?thread_id=1488&forum_id=21&group_id=11]].
- Crypto in general
- Guide first time users
- Improved Smart Card handling
- GUI for Revocation certificates
- Additional localizations
- Better certificate selection dialog
- Ability to decrypt files that do not have the .gpg extension in their filename
- Report hints
- Integration in the gpg4win build system
- Clipboard: Integrated Sign&Encrypt support
- Website / Documentation
Crypto in general
x509: access windows certstores
Windows already has a "keystore" for x509 certificates, for some settings it would be good if this store could be read in from Gpg4win (the components dirmngr and gpgsm).
long shot email idea: encrypt as message/rfc822
The headers of emails may contain more information than many people would like to reveal. A standard conforming method to send these emails is to just attach the full email as message/rfc822 type and encrypt the result. Email client with MIME support will already display it. So they only missing link is to add a convention that the subject line and reciepients of the attached email will be used and display when an email is read. Would be nice to try this concept and implement it in Free Software clients like mutt, Kontact Mail, claws, (a fork of) Thunderbird.
Make it easier to create of keys larger than 3072 bits?
Some people wish that Gpg4win/GPA should make it easier to create RSA keys with more than 3072bits, especially 4096 bit keys that seem to be popular for new certs in some circles. If so, it would be done in the advanced configuration "create new key" input GUI. Others believe that 2048 bit is a sane default, for the discussion see LargeKeys.
Also see KleopatraHackability.
Guide first time users
When starting Kleopatra for the first time on Windows it currently starts up with an empty Window and users may felt lost or may not know what do to next. Kleopatra should give users an idea what to do next, e.g. generated a certificate or configure some keyservers.
Improved Smart Card handling
GUI for Revocation certificates
Kleopatra should allow you to generate and publish a revocation certifcate for your certificates.
Kleopatra is KDE Software and thus available in 50 Languages. There could be optional "Language pack downloads" made available for those languages or at least for all the languages that the Gpg4win installer supports.
Better certificate selection dialog
The selection dialog could be improved. The default view should be very simple, but showing something that motivates people to look into the second and third layer of information. Ideally the display of the first two layers should be integrated in the email application.
- Layer: Just a graded information how well the fit of certificates is.
- Layer: Showing the accumulated information per email address.
- Layer: Showing the default information per email, address like encryption method, last contact via the certification, trustlevel, grade of algorithms.
- Hide untrusted (expired) keys by default and only show them on request.
Ability to decrypt files that do not have the .gpg extension in their filename
As of Feb 2014, trying to decrypt a file without the .gpg extension results in the somewhat missleading error message "Could not determine whether this is an S/MIME or an OpenPGP signature - maybe it is not a signature at all?"
Trying to import a certificate with an MD5 has signed user id fails because "gpg: Note: signatures using the MD5 algorithm are rejected", it seems this "note" is not displayed, but it should so the user can diagnose this case. post on users-list
Integration in the gpg4win build system
Qt / Kleopatra should be compiled from sources when creating the gpg4win package. See KleopatraHackability
Clipboard: Integrated Sign&Encrypt support
User may want to use the clipboard for encrypting and signing text (as it is possible with files) to be able to secure confidentiality and integrity. For a description of user problems with Gpg4win 2.2.4 see https://wald.intevation.org/forum/forum.php?thread_id=1488&forum_id=21&group_id=11.
Note: Microsoft dropped the exchange client extension interface that GpgOl used in Outlook 2010. Because of this there are now basically two Versions of GpgOl one for Outlook 2010 and later Versions and another one for Outlook 2003 - 2007. Please mark feature ideas for those versions with an (Ol 2010+)
PGP/MIME (Ol 2010+)
Yes that one,.. The big problem here is that Outlook and Exchange mangle the MIME structure and we have to use tricks to correctly implement it. Full support for PGP/mime in an Outlook and Exchange environment might even be impossible. Another problem are restrictions on the way how we can display decrypted and/or verified Data in a way that is secure and user friendly.
In Body Sign/Encrypt (OpenPGP) (Ol 2010+)
For the basic support it would be nice if there was an option to combine the sign encrypt options to create a combined PGP Message. This feature would only be available for OpenPGP (similar as with the clipboard).
Support for 64bit Outlook (Ol 2010+)
Compile, package and test a version of GpgOL for 64bit versions of Outlook. Probably Outlook 2013 as this seem to be more widespread.
- Checkbox for "Show Passphrase" A checkbox that disables the obfuscation of the Passphrase in the input field. This could help with the input of complex passphrases if you are sure that no one watches over your shoulder ;)
- Add these features also to the GTK+ Version of the Pinentry.
- Improve the native Windows passphrase which is part of the vanilla installer. For example it could be tied to the Windows taskbar, so that a user knows where to look for it. (not ideal because another pinentry-variant to maintain)
- Or create a static pinentry-qt4 binary that does not depend on the Qt DLL's and could be included in the vanilla / light installers.
- Ribbon UI for Windows 8 / Context integration. It would be nice if GpgEX would show Ribbon UI actions depending on the Explorer context.
- Shell extension for encrypted tarballs The general idea is that an encrypted tarball could be accessed as a Windows Shell data source. Something in a bit similar to what windows does with ".zip" folders. This would include drag & drop support to decrypt / encrypt and could probably even work transparently for some applications. Could be a lightweight alternative (with a platform independent data storage) to a virtual disk driver for a fully fletched encrypted disk.
Website / Documentation
- link the wiki (more prominently).
- Documentation: More details on adding more IDs, e.g. that Add Id only works if you have the privat certificate.
- HTML Documentation: Make it easier to click it, right now, it is way down on the page and below the download button.
- Reimplement adele to be Free Software and to handle OpenPGP/MIME. (E.g. by using Python3 and pyme/pygpgme).
- Improve the style in which "NEWS" are writting to be displayed by the website and the announcement, it should be both
- Give the refences to the issues so that interested people can go deeper. Like an issue number or a CVE or similiar.
- More written from the point of view of the users. So what does this particular entry mean for the users? What changes for them
- Werner commented about this point: Detailed information should be looked up in the GIT which has links to CVE ids, Debian and GnuPG bug ids.
- Screenshots: English ones. Windows 8.1. Explicitely state permissions like CC-BY.
Howto to make root certificates trusted
- The installer should only suggest a restart as a very last resort when it is impossible to unlock all files by killing the relevant processes.
- A launch certificate manager (together with a firststart wizard in the certificate manacher) as an Option after installation would be nice.
- http://lists.wald.intevation.org/pipermail/gpg4win-users-en/2014-July/000988.html "Plea for GPG4Win vanilla installation step reduction"
Improved Encoding handling
- Test / fix filename problems for gpgEx with Unicode characters (e.g. issue1324)
- Fix gpgol < 2010 encoding Problems
- Proactively hunt encoding Problems and tackle them. (issue1691)
File extension handling:
Gpg4win should register file extensions like .asc .gpg .pk7 etc. and open an appropriate Software / Dialog to handle those files when they are double clicked in the Windows explorer. FWIW, gpgme now has an identify feature which works similar to file(1) by looking at the content of a file. As of now it is able to detect binary CMS message and armored PGP messages. We should extend that to binary PGP messages.
Comprehensive Video Tutorials
It would be nice to have a set of clear and short Video tutorials that explain a single use case. With the idea that you can link to those if you want to send someone a short "User friendly" explanation how they can securely communicate with you. Some ideas:
- How to generate an OpenPGP Key and distribute your public key.
- How to encrypt/sign files
- How to handle encrypted and signed files
- How to use the rudimentary Outlook 2010 / 2013 support
- Working with encrypted Text and the Clipboard.
It seems some people would benefit from an interactive walkthrough to some of the usually stages. Or an interactive question and answer session with screencast (== webinar/webworkshop? :) )
Remove necessity to reboot in the installer
The Gpg4win installer should get a proper handling of running processes and make sure that everything is killed correctly when updating / uninstalling so that the Windows 98'ish "Reboot Now" will usally not anymore happen. (May be a bad idea if we need to close the file explorer.)
Display the GnuPG engine logo more prominently
There are probably few places where the GnuPG logo should be visible in addition in Gpg4win. The idea behind this is that GnuPG can do many things and Gpg4win should point out that it is fully included and strengthen GnuPG's recognition.
Ready for distributions via app-store or digital distribution platforms?
Digital distributions platforms like Steam or the Windows v>=8.1 app-store can help with
- Updates, they may notify the user of new versions.
- Trusted downloads. Many users already trust a platform or software from the same vendor, e.g. Microsoft.
- Finding Gpg4win when searching for crypto or trust enabling applications
- Payments, if a user already has paid via a distribution platform, another payment for Gpg4win would be a small step. Users are conceptionally the best source of funding for Gpg4win. Download versions without the advantages could still be gratis.
It makes sense to check what would need to be done to distribute Gpg4win over wide spread digital distribution platforms. This usually includes a technical, a financial and a licensing/condition part that need to be clarified.