From 8cfab42bc3a063f48a3934326818f1c5f2ca9721 Mon Sep 17 00:00:00 2001 From: David Bremner Date: Thu, 5 May 2022 08:29:21 -0300 Subject: refactor use of gnupg in CONSFIGURATOR.DATA.PGP Add a new low level function GPG, and a function GPG-FILE-AS-STRING intended for use in the pgp data source and the future pass(1) data source. Both of these functions support a new parameter *DATA-SOURCE-GNUPGHOME*, which allows the user (or test suite) to control where key material is stored for accessing data sources. Signed-off-by: David Bremner --- src/data.lisp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/data.lisp') diff --git a/src/data.lisp b/src/data.lisp index 7bdc0f3..9a219c3 100644 --- a/src/data.lisp +++ b/src/data.lisp @@ -510,3 +510,9 @@ chance of those passwords showing up in the clear in the Lisp debugger." (print-unreadable-object (passphrase stream) (format stream "PASSPHRASE"))) passphrase) + +(defvar *data-source-gnupghome* nil + "Home directory for gnupg when used in a data source. + +Because gnupg uses Unix domain sockets internally, this path should be short +enough to avoid the 108 char limit on socket paths.") -- cgit v1.2.3