- 16 May, 2021 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 14 May, 2021 1 commit
-
-
Ingo Klöcker authored
Add custom subclass of KeyListSortFilterProxyModel that allows specifying a key that is always accepted by the filtering. Use this subclass to make sure that the default key is not filtered out. This fixes the problem that KMail didn't show keys not matching the email address of an identity in the identity configuration dialog and that KMail cleared the keys silently if one saved such an identity after opening the Cryptography tab. Funded by: Intevation GmbH BUG: 437091 FIXED-IN: 5.18.0
-
- 12 May, 2021 9 commits
-
-
Ingo Klöcker authored
-
Ingo Klöcker authored
GnuPG-bug-id: 5245
-
Ingo Klöcker authored
It has to be hidden by the user of the model. GnuPG-bug-id: 5245
-
Ingo Klöcker authored
-
Ingo Klöcker authored
GnuPG-bug-id: 5245
-
Ingo Klöcker authored
-
Ingo Klöcker authored
-
Ingo Klöcker authored
-
Laurent Montel authored
-
- 10 May, 2021 1 commit
-
-
Laurent Montel authored
-
- 09 May, 2021 1 commit
-
-
Laurent Montel authored
-
- 08 May, 2021 1 commit
-
-
Laurent Montel authored
-
- 04 May, 2021 1 commit
-
-
Laurent Montel authored
-
- 03 May, 2021 1 commit
-
-
Laurent Montel authored
-
- 01 May, 2021 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 29 Apr, 2021 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 28 Apr, 2021 8 commits
-
-
Ingo Klöcker authored
-
Ingo Klöcker authored
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
- 27 Apr, 2021 4 commits
-
-
Ingo Klöcker authored
This allows proper handling of groups in the different modes of the resolver. GnuPG-bug-id: 5283
-
Ingo Klöcker authored
* Kill all running gpg daemons, e.g. gpg-agent * Unset GNUPGHOME environment variable GnuPG-bug-id: 5283
-
Ingo Klöcker authored
* Remove group support from findBestByMailBox(). * Add findGroup() for looking up suitable group for a key protocol and some usage. GnuPG-bug-id: 5283
-
Ingo Klöcker authored
GnuPG-bug-id: 5283
-
- 24 Apr, 2021 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 23 Apr, 2021 3 commits
-
-
Laurent Montel authored
-
Ingo Klöcker authored
-
Laurent Montel authored
-
- 22 Apr, 2021 4 commits
-
-
Ingo Klöcker authored
-
Ingo Klöcker authored
Keys with the wrong protocol should be ignored because the corresponding key selection combos are not visible. GnuPG-bug-id: 5283
-
Ingo Klöcker authored
If the key that is set with setCurrentKey() became the current key by changes in the underlying model (i.e. because it happens to be the item at the current index), then no signal was emitted. This triggered an update problem in the key approval dialog noticed after the previous commit. This problem is fixed by this change because on all model changes updateWithDefaultKey() is called which in turn calls setCurrentKey(). GnuPG-bug-id: 5283
-
Ingo Klöcker authored
We need to look up the keys by the addr-spec of the full user ids GnuPG-bug-id: 5283
-
- 21 Apr, 2021 2 commits
-
-
Ingo Klöcker authored
-
Ingo Klöcker authored
Previously, in mixed mode, if both protocols were enabled, null keys were not ignored resulting in non-compliance. If only one protocol was allowed/enabled, then null keys were ignored by the protocol check (because null keys have UnknownProtocol). GnuPG-bug-id: 5283
-