Date: Mon, 22 Dec 2014 09:46:30 +0000 From: Matt Smith <fbsd@xtaz.co.uk> To: Jonathan Chen <jonc@chen.org.nz> Cc: freebsd-ports@freebsd.org Subject: Re: gnupg & pinentry Message-ID: <20141222094630.GF52267@xtaz.uk> In-Reply-To: <CAJuc1zPtDsOQG2oAKoTVB%2BpVyox8h1mGZOW6CtMBw1GN7=vnOg@mail.gmail.com> References: <CAJuc1zPtDsOQG2oAKoTVB%2BpVyox8h1mGZOW6CtMBw1GN7=vnOg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 22 22:33, Jonathan Chen wrote: >Hi, > >Once upon a time, installing gnupg didn't require pinentry, and I >could run it quite happily on the command line. However, nowadays if I >install the port it drags in pinentry and a whole set of graphical >libraries that I don't really need on a headless box. Is pinentry >really required for gnupg to run correctly? > I believe in version 2.1.x they made entering the passphrase via pinentry basically mandatory and deprecated being able to do it via stdin methods. So it probably pulls in pinentry by default now. For binary packages this is unfortunatly going to default to all the front ends which includes ones for X. For port based source installs you can deselect the ones for X and only leave the ncurses one which then just pulls in one extra dependancy. Unfortunately that's the downside of binary package installs. FYI, you can also re-enable passphrases by stdin if required by adding allow-loopback-pinentry to .gnupg/gpg-agent.conf and using the --pinentry-mode=loopback command line switch to gpg. -- Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141222094630.GF52267>