Deleting a user id is more or less useless. What you want is to revoke a user id.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 25 2018
Jul 24 2018
I can't reproduce this. When I make Dirmngr offline I correctly get a No CRL known error. So it must be something different.
Jul 18 2018
Tester reports that this works now.
Jul 17 2018
This was a misunderstanding. Import is possible. The german translation of Kleopatra wrongly indicated an error because it translated "unknown certificates" as "ungültige Zertifikate".
Jul 16 2018
Jul 10 2018
On another note. We might also want to reduce the clicks required when certifying a key. The "I have checked the fingerprint" checkbox is out of time. People will check it regardless and we can't force them to do it.
Jul 5 2018
Finally changed it. Especially for keyserver search this was important.
I'm going for Wontfix here. It's just too verbose and I don't really see the point of that additional information.
Jul 4 2018
We have two cases:
- No MDC with a "modern" cipher algo
ASCII Armored CMS files now also use p7m and p7s this is already handled gracefully by Kleopatra and does not require us to register new filetypes.
Jul 2 2018
Ha, I wish e-mail-like searches would be done using only WKD with no fallbacks to keyservers... that way keys would be "more verified"... but I understand it may be not practical :)
I'm pretty sure that the running command ist the reloadkeyscommand.
Jun 27 2018
Changed
Jun 26 2018
Thanks a lot!
Jun 25 2018
Will be fixed with the next release. With the next release kleopatra will only set "allow-version-check" once except if the user explicitly selects "help -> check for updates".
Right. The only way to disable it is if an update notification pops up. If you then unselect "Show this notification for future updates" it is disabled. And you only get to that dialog if there is an update check.
Jun 22 2018
Jun 21 2018
Jun 20 2018
Jun 18 2018
I'm changing this to wishlist as I don't think anymore that we have something new here. When working with unsigned files the user has/had already the same problems as described in the issue.
(Wishlist does not mean that it will be ignored.)
Forgot to comment. Yes what is in the video is also what I thought.
Jun 6 2018
BTW, you now need to use --rfc2440 to create a non-mdc message for testing.
Jun 1 2018
Thanks. Yes, I think that's it. Here's a video just in case.
Ok You could notice it because if the year changes there was no "blue" selected date in the current page.
Had a bit trouble reproducing it. It worked for me.
It's nice. Although for now I've only added a message in the legacy_cipher_nomdc case:
I justed commited some gadgets to gpgme which might be helpful But please show warnings etc before you use that new option.
May 22 2018
Yes, I checked and I can indeed add multiple keys.
No, that does not solve my problem.
Because I absolutely need to be able to see exactly what I am doing and in this respect the previous version (as it still is on Ubuntu) is much, much better.
Thanks. I'll look into it. It's possible that in our tests we only changed the complete date.
Thanks for the report. This is indeed a bug.
If you click on the grey question mark in the "Entry field" when adding recipients you get a dialog that lists all keys and also allows for multiple selection.
May 19 2018
May 18 2018
May 15 2018
May 8 2018
Wait. Users should not have the ability in the GUI to mess with the CRL cache. That is internal / private stuff. And something for developers, so this should be removed from the GUI altogether.
May 7 2018
May 3 2018
Better but still not perfect. It still can happen that it is opened in the background if you put the options dialog in the background before the window pops up. But I think that is acceptable for such a rarely used feature.
At the very least the dialog should not be easily closable if the CSR was not exported to a file. This makes it too easy to accidentally loose the CSR.
Apr 30 2018
Apr 27 2018
Oops. I also opened T3939 about this.
Apr 26 2018
Apr 25 2018
Apr 20 2018
Apr 18 2018
Mh, we can probably drop the GPGME part of this. In the longer term I'm hoping for the automatic refresh in dirmngr. So that refresh-keys would not be needed.
Are you asking for a way to --refresh-keys via GPGME? IF so shall that be a syncronous thing or just a trigger. Note that we the last update time is already part of gpgme_key_t and can thus be used to check whether a trigger worked.
Anyway this will be a larger change and may need gpg support.
Apr 16 2018
A reason we did not touch it in the past is that Ideally we don't want users to have to mess with refresh keys but would rather have this done automatically in the background by dirmngr.
Apr 13 2018
3.1.0 is released and this issue is to our knowledge fixed.
3.1.0 is released and this issue is to our knowledge fixed.
Apr 12 2018
New version of GnuPG is now packaged.