1. 11 Jun, 2018 2 commits
  2. 08 Jun, 2018 1 commit
    • Werner Koch's avatar
      gpg: Sanitize diagnostic with the original file name. · 2326851c
      Werner Koch authored
      * g10/mainproc.c (proc_plaintext): Sanitize verbose output.
      --
      
      This fixes a forgotten sanitation of user supplied data in a verbose
      mode diagnostic.  The mention CVE is about using this to inject
      status-fd lines into the stderr output.  Other harm good as well be
      done.  Note that GPGME based applications are not affected because
      GPGME does not fold status output into stderr.
      
      CVE-id: CVE-2018-12020
      GnuPG-bug-id: 4012
      (cherry picked from commit 13f135c7a252cc46cff96e75968d92b6dc8dce1b)
      2326851c
  3. 13 Apr, 2018 1 commit
  4. 19 Dec, 2017 1 commit
  5. 18 Dec, 2017 1 commit
    • NIIBE Yutaka's avatar
      po: Update Japanese translation. · 1338bce5
      NIIBE Yutaka authored
      
      
      * po/ja.po: Fix message with no "%s".
      
      --
      
      Backport of master commit from: 77e2fcb4ffbad8577a2cf41f17bf92dec6a93ad8
      
      The wrong message caused segmentation fault for key generation when
      no expiration is specified.
      
      GnuPG-bug-id: 3619
      Signed-off-by: NIIBE Yutaka's avatarNIIBE Yutaka <gniibe@fsij.org>
      1338bce5
  6. 04 Dec, 2017 1 commit
    • NIIBE Yutaka's avatar
      g10: Fix regexp sanitization. · 9441946e
      NIIBE Yutaka authored
      
      
      * g10/trustdb.c (sanitize_regexp): Only escape operators.
      
      --
      
      Backport from master commit:
      	ccf3ba92087e79abdeaa0208795829b431c6f201
      
      To sanitize a regular expression, quoting by backslash should be only
      done for defined characters.  POSIX defines 12 characters including
      dot and backslash.
      
      Quoting other characters is wrong, in two ways; It may build an
      operator like: \b, \s, \w when using GNU library.  Case ignored match
      doesn't work, because quoting lower letter means literally and no
      much to upper letter.
      
      GnuPG-bug-id: 2923
      Co-authored-by: default avatarDamien Goutte-Gattat <dgouttegattat@incenp.org>
      Signed-off-by: NIIBE Yutaka's avatarNIIBE Yutaka <gniibe@fsij.org>
      9441946e
  7. 11 Nov, 2017 1 commit
  8. 10 Nov, 2017 1 commit
  9. 02 Nov, 2017 1 commit
  10. 06 Sep, 2017 1 commit
  11. 04 Aug, 2017 1 commit
  12. 02 Aug, 2017 3 commits
  13. 01 Aug, 2017 1 commit
  14. 19 Jul, 2017 5 commits
  15. 07 Jul, 2017 7 commits
  16. 04 Jul, 2017 1 commit
  17. 03 Jul, 2017 1 commit
  18. 10 May, 2017 1 commit
    • Ineiev's avatar
      g10: Fix secmem leak. · 2c2121ff
      Ineiev authored and NIIBE Yutaka's avatar NIIBE Yutaka committed
      
      
      * g10/keygen.c (proc_parameter_file): Fix secmem leak.
      
      --
      
      proc_parameter_file adds certain parameters to the list in the PARA
      argument; however, these new entries are leaked because they
      are added to head, while the PARA list is released by the caller
      of proc_parameter_file.
      
      GnuPG-bug-id: 1371
      Signed-off-by: Ineiev's avatarIneiev <ineiev@gnu.org>
      2c2121ff
  19. 30 Mar, 2017 1 commit
    • Werner Koch's avatar
      gpg: Fix exporting of zero length user ID packets. · bb61191a
      Werner Koch authored
      
      
      * g10/build-packet.c (do_user_id): Avoid indeterminate length header.
      --
      
      We are able to import such user ids but when exporting them the
      exported data could not be imported again because the parser bails out
      on invalid keyrings.  This is now fixed and should be backported.
      
      Note that in 1.4 and 2.0 this is only an issue for attribute packets.
      In 2.1 user IDs were also affected.a
      
      Signed-off-by: default avatarWerner Koch <wk@gnupg.org>
      bb61191a
  20. 02 Nov, 2016 2 commits
  21. 18 Aug, 2016 1 commit
  22. 17 Aug, 2016 5 commits