Summary: | >=app-crypt/gnupg-2.1.0 set GPG_AGENT_INFO for legacy apps | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Reuben Martin <reuben.m> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | alonbl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Reuben Martin
2015-10-11 02:17:05 UTC
gpg-agent should be executed within the context of the user. GPG_AGENT_INFO is to be set by the user taken out of the output of gpg-agent. (In reply to Alon Bar-Lev from comment #1) > gpg-agent should be executed within the context of the user. Yes... Nothing has changed here. > GPG_AGENT_INFO is to be set by the user taken out of the output of gpg-agent. I have no clue what you're getting at. I have never seen any STOUT/STERR output from gpg-agent to specify the socket location. With version 2,1 the socket location cannot be changed. From the man page: --use-standard-socket --no-use-standard-socket --use-standard-socket-p Since GnuPG 2.1 the standard socket is always used. These options have no more effect. (In reply to Reuben Martin from comment #2) > (In reply to Alon Bar-Lev from comment #1) > > gpg-agent should be executed within the context of the user. > > Yes... Nothing has changed here. > > > > GPG_AGENT_INFO is to be set by the user taken out of the output of gpg-agent. > > I have no clue what you're getting at. I have never seen any STOUT/STERR > output from gpg-agent to specify the socket location. With version 2,1 the > socket location cannot be changed. From the man page: > It is part of the output for <2.1 in eval output for --daemon, you are correct in that for 2.1 it is standard socket which is fixed name in gnupg homedir in question (so it is changed depending on the location of the homedir, it isnt a fixed location as such). Additionally it is possible to use socket redirection, which is useful e.g. for NFS /home mounts that doesnt support sockets. That'd require a text file in its place with %Assuan% socket= informations to specify the location (e.g. in /var/run, exported variables are supported using ${VAR} syntax) In any case, this seems to be an issue with applications using gnupg more than anything else, and as such they should be updated. |