diff options
author | Slávek Banko <slavek.banko@axis.cz> | 2020-11-08 18:31:02 +0100 |
---|---|---|
committer | Slávek Banko <slavek.banko@axis.cz> | 2020-11-14 00:28:34 +0100 |
commit | b37f44d6c7444ca20c48a07fdcaf7b2a812db5bd (patch) | |
tree | 971f3503afaaa23770983631a621232ca6fc1347 /debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian | |
parent | ca54da3228ddc925ae804a8b9bcf8037767e13bf (diff) | |
download | extra-dependencies-b37f44d6c7444ca20c48a07fdcaf7b2a812db5bd.tar.gz extra-dependencies-b37f44d6c7444ca20c48a07fdcaf7b2a812db5bd.zip |
DEB pinetry-tqt: Add pinentry built separately only as pinentry-tqt.
The package is taken from Debian upstream, renamed pinentry-tqt so
that it does not conflict with standard pinentry, and dependencies,
patches and files related to other pinetry variants have been
removed from deb packaging.
Signed-off-by: Slávek Banko <slavek.banko@axis.cz>
Diffstat (limited to 'debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian')
-rw-r--r-- | debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian | 83 |
1 files changed, 83 insertions, 0 deletions
diff --git a/debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian b/debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian new file mode 100644 index 00000000..09d64a97 --- /dev/null +++ b/debian/pinentry-tqt/pinentry-tqt-1.1.0/debian/README.Debian @@ -0,0 +1,83 @@ +PIN entry for Debian - TQt flavor +--------------------------------- + +This package is derived from the pinentry Debian package. Only the +pinentry-tqt variant is built because it is not included in the +distribution packages. + +To avoid conflicts with the distribution package and to avoid having +other flavors built here, the source package is renamed pinentry-tqt. + + -- Slávek Banko <slavek.banko@axis.cz> Sun, 08 Nov 2020 16:37:59 +0100 + + +PIN entry for Debian +-------------------- + +This package and its sibling packages are intended to be used as a +pass-phrase entry dialog for the program gpg-agent (Debian package +gnupg-agent). To configure gpg-agent to use one of the provided +pinentry programs, put something like this into your +~/.gnupg/gpg-agent.conf: + + pinentry-program /usr/bin/pinentry-FLAVOR + +You have the following pinentry variants to choose from: + +/usr/bin/pinentry-tqt + Graphical PIN entry program that uses the TQt tool kit + (package pinentry-tqt). + +/usr/bin/pinentry + Generic name that points, via the Debian alternatives system, to + the "best" installed PIN entry program. gpg-agent uses this by + default. + +/usr/bin/pinentry-gnome + Graphical PIN entry program that uses GNOME's gcr prompter. This + package will work on systems that use Wayland as well as X11, and + it is the preferred pinentry for desktop systems (package + pinentry-gnome). + +/usr/bin/pinentry-x11 + Generic name that points, via the Debian alternatives system, to + the "best" installed PIN entry program with X11 support (that is, + one of the GNOME, Qt, GTK+2, or FLTK flavors). + +/usr/bin/pinentry-qt + Graphical PIN entry program that uses the Qt tool kit + (package pinentry-qt). + +/usr/bin/pinentry-curses + Text-mode PIN entry program that uses the curses tool kit (package + pinentry-curses). + +/usr/bin/pinentry-tty + Minimal Text-mode dumb-terminal PIN entry program (package + pinentry-tty). + +/usr/bin/pinentry-gtk-2 + Graphical PIN entry program that uses the GTK+ tool kit version 2 + (package pinentry-gtk2). + +/usr/bin/pinentry-fltk + Graphical PIN entry program that uses the Fast Light Toolkit (FLTK) + (package pinentry-fltk). + +The graphical variants automatically fall back to the curses interface +if no desktop environment is available. So for example, if you +frequently switch between text mode and KDE, and you want to use both +Mutt and KMail with GnuPG pass-phrase agent support, then configuring +/usr/bin/pinentry-qt would work. (In this case, leaving your +configuration alone would also work, if you only have pinentry-qt +installed) + +Note that while pinentry-curses and pinentry-tty will work in some +cases in a non-graphical environment, they are likely to fail when +used while sharing a tty with a terminal-intensive program like emacs. +If a graphical pinentry isn't possible, the recommended workaround is +to have a pinentry-tty or pinentry-curses attached to a separate, +dedicated pseudoterminal. (see https://dev.gnupg.org/T3217 for more +details) + + -- Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Fri, 8 May 2020 12:11:12 -0400 |