move gpg tmp home to system temp dir
authorJoey Hess <joeyh@joeyh.name>
Tue, 12 Oct 2021 17:22:46 +0000 (13:22 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 12 Oct 2021 17:29:56 +0000 (13:29 -0400)
commitc2a44eab509d8f6e773e84d83623e499f9d3aef0
tree1d00b432fbccb18f33a0025f22ad1563b3b6f6eb
parentb7d5d54b065fe848266018d6dbaa9e3cda9f070b
move gpg tmp home to system temp dir

test: Put gpg temp home directory in system temp directory, not filesystem
being tested.

Since I've found indications gpg can fail talking to the agent when the
socket ends up on eg, fat. And to hopefully fix this bug report I've
followed up on.

The main risk in using the system temp dir is that TMPDIR could be set to a
long directory path, which is too long to put a unix socket in. To
partially amelorate that risk, it uses either an absolute or a relative
path, whichever is shorter. (Hopefully gpg will not convert it to a longer
form of the path..)

If the user sets TMPDIR to something so long a path to it +
"S.gpg-agent" is too long, I suppose that's their issue to deal with.

Sponsored-by: Dartmouth College's Datalad project
CHANGELOG
Test.hs
doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_3_d3a478e3f7da91ab14c9b1e24d3e07d6._comment [new file with mode: 0644]