Gpgtools MacGPG2 → 2.0.18

Comments and changes to this ticket

• You flagged this item as spam.
  

  Mento January 3rd, 2011 @ 05:58 PM

  • Title changed from “Include new versions of gpg-start-agent and pinentry-mac in MacGPG2 installer” to “Include new versions of start-gpg-agent and pinentry-mac in MacGPG2 installer”

• You flagged this item as spam.
  

  Alex (via GPGTools) January 4th, 2011 @ 01:40 PM

  • Milestone cleared.
  • Importance changed from “” to “”

  [bulk edit]

• You flagged this item as spam.
  

  Benjamin Donnachie January 4th, 2011 @ 11:28 PM

  • State changed from “new” to “hold”

  I can understand including the new pinentry, however start-gpg-agent is deprecated and I need more information on what you are trying to achieve.

  See below for copies of my emails on the subject:

  Sorry I haven't been able to contact you about this earlier today -
  busy trying to get things done before heading back to work tomorrow.

  To give a little background, MacGPG2 v2.0.16 is now compiled with the
  new gpg2 --enable-standard-socket ./configure option. This is
  primarily aimed at Windows machines and causes gpg2 to fall back to
  using standard sockets in the absence of any GPG environment variables
  or being unable to contact a running instance of gpg-agent, and will
  daemonise an instance of gpg-agent if needed:

  • If the agent's --use-standard-socket option is active, all tools try to start and daemonize the agent on the fly. In the past this was only supported on W32; on non-W32 systems the new configure option --use-standard-socket may now be used to use this feature by default.

  It was created by gnupg configure 2.0.16, which was generated by GNU Autoconf 2.64. Invocation command line was

  $ ./configure --enable-static=no --disable-endian-check
  

  --disable-dependency-tracking --disable-asm

      --with-pinentry-pgm=/usr/local/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
  

  --enable-standard-socket

  However, start-gpg-agent was written to implement this behaviour in
  earlier versions and the MacGPG2 version already uses
  standard-sockets:

  [...] if gpgAgentRunning > 0 then
  

     do shell script "/usr/local/bin/gpg-agent --daemon
  

  --use-standard-socket --write-env > /dev/null" end if
  [...]

  I have not forced standard sockets within the launchd plist as this is
  the only opportunity for gpg-agent to set system wide environment
  variables and it gives the user to override it if they wish.

  Please let me know what you need from MacGPG2 for it to work
  seamlessly with GPGtools. My ultimate goal is for MacGPG2 to be as
  uninvasive as possible; it should modify as few system files as
  possible and ultimately I want it to use an unpatched copy of GnuPG2.

  and

  From a MacGPG2 perspective, start-gpg-agent is obsolete and has only
  been retained for Tiger compatibility due to it's inferior
  implementation of launchd.

  gpg-agent should be started by launchd during user log in or, from
  v2.0.16, automatically on the fly. In view of the latter behaviour,
  start-gpg-agent will be removed from future releases.

• You flagged this item as spam.
  

  Benjamin Donnachie January 16th, 2011 @ 12:11 PM

  • State changed from “hold” to “resolved”

  start-gpg-agent dropped along with PPC support.

  Updated pinentry included in v2.0.17 (Currently RC)

• You flagged this item as spam.
  

  Alex (via GPGTools) December 28th, 2011 @ 01:27 PM

  • Milestone set to “2.0.18”
  • Importance changed from “” to “”

  [bulk edit]

• 

  steve April 26th, 2013 @ 03:59 PM

  • State changed from “resolved” to “new”
  • Tag cleared.
  • Assigned user cleared.
  • Importance changed from “” to “Low”
• 

  steve May 23rd, 2013 @ 08:57 AM

  • State changed from “new” to “released”