- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 21 2018
close my account
Thanks for testing and the confirmation / praise ;-)
Hi Andre,
AWESOME! Thanks a lot. It works and it’s also faster. GREAT!!!
Jacques
From: aheinecke (Andre Heinecke) [mailto:noreply@dev.gnupg.org]
Sent: March 21, 2018 2:41 AM
To: Jacques Latour <Jacques.Latour@cira.ca>
Subject: [Task] [Changed Status] T3847: Pinentry-qt pop up not appearing when I send a signed/encrypted email
aheinecke changed the task status from "Open" to "Testing".
aheinecke triaged this task as "Normal" priority.
aheinecke added projects: gpgol, gpg4win.
aheinecke added a comment.
Hi,
I'm not 100% certain but I think that it is likely that your problem is fixed with the upcoming 3.1 version. We have reworked how GpgOL encrypts there a bit ( T3509https://dev.gnupg.org/T3509 )
Could you please try out the beta of the upcoming version https://www.gpg4win.org/version3.1.html and confirm that the problem is either still there or gone?
Thanks!
TASK DETAIL
https://dev.gnupg.org/T3847
EMAIL PREFERENCES
https://dev.gnupg.org/settings/panel/emailpreferences/
To: aheinecke
Cc: aheinecke, latour_jacques, Mak, gp_ast
This is an automated email from the GnuPG development hub. If you have registered in the past at https://bugs.gnupg.org/ your account was migrated automatically. You can visit https://dev.gnupg.org/ to set a new password and update your email preferences.
The second user ID in my test case was an "URL". So we now use what ever the "raw" user id data is as the Name if both name and email are empty.
I don't find an easy way to fix this.
Did not really help. It does not work for English somehow and even with a different language like french very few additional buttons were translated. Still a weird mix.
I just tested changing passphrases and indeed this is very ugly. Especially as this opens up a wide range of error states where you have different passphrases for different subkeys etc.
I'm not 100% certain but I think that it is likely that your problem is fixed with the upcoming 3.1 version. We have reworked how GpgOL encrypts there a bit ( T3509 )
Mar 20 2018
The field is now renamed to "Activate GnuPG Profile" to make it more clear the the button activates a new profile.
I've added this to libkleo formatting now. But seeing it and thinking more about it I don't like it. As I think that the export is mostly for "You give this to others" information about the subkeys is too verbose. The current header should suffice as "some info for differentiating between keys".
Kleopatra now shows this:
This works now reliably in my tests.
Cancel is now handled and the key is not removed if the user canceled.
I got beta feedback which after analysis showed that parts of the encrypt changes in 3.1 that would have addressed this lead to crashes. So we had to disable it for now and block Outlook again as temporary blocking is better then "random" crashing :-((