1. 15 Apr, 2022 1 commit
    • Martin Liska's avatar
      Include <iterator>. · 5c4b8edb
      Martin Liska authored and Heiko Becker's avatar Heiko Becker committed
      In order to fix:
      [   16s] /home/abuild/rpmbuild/BUILD/libkleo-21.12.3/src/kleo/keyserverconfig.cpp:73:44:   required from here
      [   16s] /home/abuild/rpmbuild/BUILD/libkleo-21.12.3/src/utils/algorithm.h:35:30: error: no matching function for call to 'begin(QStringList&)'
      [   16s]    35 |     std::transform(std::begin(c), std::end(c), std::begin(c), op);
      [   16s]       |                    ~~~~~~~~~~^~~
      
      The change is documented here:
      https://gcc.gnu.org/gcc-12/porting_to.html#header-dep-changes
      
      (cherry picked from commit f290218a)
      5c4b8edb
  2. 09 Apr, 2022 1 commit
  3. 08 Apr, 2022 1 commit
  4. 21 Mar, 2022 1 commit
  5. 19 Mar, 2022 1 commit
  6. 12 Mar, 2022 1 commit
  7. 11 Mar, 2022 1 commit
  8. 10 Mar, 2022 2 commits
  9. 08 Mar, 2022 1 commit
  10. 03 Mar, 2022 3 commits
    • Ingo Klöcker's avatar
      Make the model used for the key selection combo a single-column model · 6de644bf
      Ingo Klöcker authored
      If we don't do this, then QAccessibleTable, which is used for the
      QListView of the combo box pop up, miscalculates the child from the
      logical index. The causes the weird effect that, when you move the
      cursor down in the pop up, then the screen reader reads the model
      items in columns-first order, i.e. for the second entry in the
      combo box it reads the second column of the first row (i.e. the first
      entry) instead of the first column of the second row.
      This is clearly a bug in QAccessibleTable which shouldn't consider the
      column count if QAccessibleTable provides the interface for a list view.
      
      For the combo box we anyway need the first column of the key list model
      only, so we can simply pretend that there is only one column.
      
      GnuPG-bug-id: 5845
      6de644bf
    • Ingo Klöcker's avatar
      Fix check for resolved signing keys · 023f88d5
      Ingo Klöcker authored
      This makes sure that AllResolved is returned only if signing keys have
      been found for the required protocols.
      
      GnuPG-bug-id: 5869
      023f88d5
    • Ingo Klöcker's avatar
      Add two more recipient-only test keys/certificates · 57412770
      Ingo Klöcker authored
      Add a fully trusted public OpenPGP key for openpgp-only@example.net and
      a trusted public S/MIME certificate for smime-only@example.net.
      
      GnuPG-bug-id: 5869
      57412770
  11. 24 Feb, 2022 3 commits
  12. 23 Feb, 2022 5 commits
  13. 22 Feb, 2022 2 commits
    • Ingo Klöcker's avatar
      Return more accessible text representations for some model entries · 7b88f13d
      Ingo Klöcker authored
      GnuPG-bug-id: 5841
      7b88f13d
    • Ingo Klöcker's avatar
      Add helpers for more accessible dates and hex id strings · 241398d8
      Ingo Klöcker authored
      These helpers create strings that are more suitable for screenreaders
      than the corresponing strings created for displaying on screen.
      
      For dates we use the system's long format. Unfortunately, this may contain
      the day of the week which is a bit too verbose, but it's certainly better
      understandable than a string of three numbers.
      
      For hex ids (i.e. key ids and fingerprints) we take groups of four
      separating all characters with spaces (to avoid strings of digits to
      be read as numbers) and separating all groups with commas (to force
      a pause between the groups).
      
      GnuPG-bug-id: 5841
      241398d8
  14. 15 Feb, 2022 2 commits
  15. 11 Feb, 2022 8 commits
  16. 09 Feb, 2022 2 commits
  17. 03 Feb, 2022 1 commit
  18. 27 Jan, 2022 2 commits
  19. 25 Jan, 2022 2 commits