Gpgtools MacGPG2 → 2.2.0

Comments and changes to this ticket

• 

  Support November 19th, 2014 @ 11:44 PM

  Assigned to Tender discussion #29108.

• 

  Support December 21st, 2014 @ 03:10 PM

  Assigned to Tender discussion #150.

• 

  Support June 1st, 2015 @ 04:36 PM

  • Tag set to “”

  Assigned to Tender discussion #756.

• 

  Support June 18th, 2015 @ 12:20 AM

  • Tag cleared.

  Assigned to Tender discussion #10579.

• 

  Support August 14th, 2015 @ 02:46 PM

  • Tag set to “”

  Assigned to Tender discussion #36916.

• 

  Support October 18th, 2016 @ 06:34 PM

  • Tag changed from “” to “#tag id: 460388, name:”

  Assigned to Tender discussion #49958.

• 

  steve October 18th, 2016 @ 06:36 PM

  • Tag cleared.
• 

  Support October 21st, 2016 @ 05:12 PM

  • Tag set to “”

  Assigned to Tender discussion #1965.

• 

  Support February 22nd, 2017 @ 04:12 PM

  • Tag changed from “” to “#tag id: 460388, name:”

  Assigned to Tender discussion #2266.

• 

  Support February 24th, 2017 @ 10:55 AM

  • Tag changed from “#tag id: 460388, name:” to “tag id 460388, name”

  Assigned to Tender discussion #51032.

• 

  Support March 15th, 2017 @ 05:27 PM

  Assigned to Tender discussion #51244.

• You flagged this item as spam.
  

  Wolfgang Glas March 22nd, 2017 @ 10:54 AM

  We have the following issue when trying to generate GPG signatures using SHA-256:

  $ gpg-connect-agent
  > SIGKEY 44A7BBB8FD7AEBB001E0DA06A0A892EFC341C71E
  OK
  > SETHASH 8 79E12A66EFAAD785A443BB9787C8EF8A87F0DF4AA9669C452FCEBC67D323C42B
  OK
  > PKSIGN
  ERR 100663351 Invalid value <SCD>
  

  This is related to https://lists.gnupg.org/pipermail/gnupg-devel/2014-September/028759... and would have been fixed by gnupg-2.1, which is out since 2014.

  Please consider to apply the patch in the mentioned link to you agent code or upgrade to gnupg-2.1

  TIA and best regards, Wolfgang Glas

• 

  steve May 18th, 2017 @ 07:08 PM

  • Tag cleared.
• 

  Support May 29th, 2017 @ 02:25 PM

  • Tag set to “”

  Assigned to Tender discussion #52305.

• 

  Support May 29th, 2017 @ 04:23 PM

  • Tag changed from “” to “#tag id: 460388, name:”

  Assigned to Tender discussion #52227.

• 

  Support May 31st, 2017 @ 06:50 PM

  • Tag changed from “#tag id: 460388, name:” to “tag id 460388, name”

  Assigned to Tender discussion #2558.

• 

  steve June 13th, 2017 @ 10:34 PM

  • State changed from “new” to “started”
  • Tag cleared.
  • Milestone set to “2.2.0”

  Test build sent to users who requested gpg 2.1 support.

• 

  steve June 13th, 2017 @ 11:06 PM

  • Assigned user set to “Mento”

  So for any users cc: on this ticket and not having a discussion on our support platform:

  We have a first GPG Suite test build which integrates gpg 2.1. Here is the signature file for that release.

  It would be great if you could test this build and let us know if run into any trouble. Please note, that downgrading to the current beta release will require additional steps in case new keys were created using this test build. Depending on the test results, gpg 2.1 may soon land in the beta branch.

  All the best,
  steve

• 

  steve June 18th, 2017 @ 06:23 PM

  • State changed from “started” to “verified”

  gpg 2.1 is now in GPG Suite nightly build.

  Disclaimer: This is a development version which has not been thoroughly tested yet - bugs or crashes are to be expected. Thanks for helping us test.

• 

  Support June 18th, 2017 @ 06:51 PM

  • Tag set to “”

  Assigned to Tender discussion #1874.

• 

  Support July 24th, 2017 @ 12:53 PM

  • Tag changed from “” to “#tag id: 460388, name:”

  Assigned to Tender discussion #2021.

• 

  steve July 24th, 2017 @ 03:33 PM

  • Tag cleared.
• 

  Support August 1st, 2017 @ 08:04 PM

  • Tag set to “”

  Assigned to Tender discussion #1984.

• 

  steve September 25th, 2017 @ 04:20 PM

  • State changed from “verified” to “released”

  [bulk edit]