security/gnupg

[Jun Kuriyama]

2013/2/2 Jason Helfman <jgh at freebsd.org>:
>> > [ ] STD_SOCKET  Use standard socket for agent
...
> Agreed with all of stated above, and please use the documentation as well to
> see if it is noted there. Enabling the flag in the port adds
> --enable-standard-socket to the CONFIGURE arguments for the ports build
> process.
>
> http://www.gnupg.org/documentation/manuals/gnupg/Agent-Options.html
> --use-standard-socket--no-use-standard-socket By enabling this option
> gpg-agent will listen on the socket named S.gpg-agent, located in the home
> directory, and not create a random socket below a temporary directory. Tools
> connecting to gpg-agent should first try to connect to the socket given in
> environment variable GPG_AGENT_INFO and then fall back to this socket. This
> option may not be used if the home directory is mounted on a remote file
> system which does not support special files like fifos or sockets. Note,
> that --use-standard-socket is the default on Windows systems. The default
> may be changed at build time. It is possible to test at runtime whether the
> agent has been configured for use with the standard socket by issuing the
> command gpg-agent --use-standard-socket-p which returns success if the
> standard socket option has been enabled.

I'd like to change description for STD_SOCKET option to summerize
above if someone suggests better wordings.


-- 
Jun Kuriyama <kuriyama at FreeBSD.org> // FreeBSD Project
         <kuriyama at s2factory.co.jp> // S2 Factory, Inc.