1
m4_changequote({,})m4_dnl
2
.TH PINENTRY-m4_translit(flavor, {a-z}, {A-Z}) 1 "27 Jan 2005"
4
pinentry\-flavor \- PIN or pass-phrase entry dialog for GnuPG
7
\fBpinentry-flavor\fB [\fIOPTION\fR...]
9
\fBpinentry\-flavor\fR is a program that allows for secure entry of PINs or
10
pass phrases. That means it tries to take care that the entered
11
information is not swapped to disk or temporarily stored anywhere.
12
This functionality is particularly useful for entering pass phrases
13
when using encryption software such as GnuPG or e-mail clients using
14
the same. It uses an open protocol and is therefore not tied to
19
{{\fBpinentry-curses\fR implements a PIN entry dialog
20
using the curses tool kit, meaning that it is useful for users working
21
in text mode without the X Window System. There are other flavors
22
that implement PIN entry dialogs that use an X tool kit. If you
23
have installed any of the latter programs then this program is not necessary
24
because the X flavors automatically fall back to text mode if
27
{{\fBpinentry-gtk\fR implements a PIN entry dialog
28
using the GTK+ tool kit version 1. If the X Window System is not
29
active then an alternative text-mode dialog will be used. There are
30
other flavors that implement PIN entry dialogs using other tool kits.}},
32
{{\fBpinentry-gtk-2\fR implements a PIN entry dialog
33
using the GTK+ tool kit version 2, so it is especially suitable for
34
users of GNOME. If the X Window System is not active then an alternative
35
text-mode dialog will be used. There are other flavors that
36
implement PIN entry dialogs using other tool kits.}},
38
{{\fBpinentry-qt\fR implements a PIN entry dialog
39
using the Qt tool kit, so it is especially suitable for users of KDE.
40
If the X Window System is not active then an alternative text-mode
41
dialog will be used. There are other flavors that implement PIN
42
entry dialogs using other tool kits.}})
44
\fBpinentry\-flavor\fR is typically used internally by \fBgpg-agent\fR.
45
Users don't normally have a reason to call it directly.
49
Print the program version and licensing information.
52
Print a usage message summarizing the most useful command-line options.
54
\fB\-\-debug\fR, \fB\-d\fR
55
Turn on some debugging. Mostly useful for the maintainers. Note
56
that this may reveal sensitive information like the entered pass phrase.
58
\fB\-\-enhanced\fR, \fB\-e\fR
59
Ask for timeouts and insurance, too. Note that this is currently
62
\fB\-\-no\-global\-grab\fR, \fB\-g\fR
63
Grab the keyboard only when the window is focused. Use this
64
option if you are debugging software using \fBpinentry\-flavor\fR;
65
otherwise you may not be able to to access your X session anymore (unless
66
you have other means to connect to the machine to kill
67
\fBpinentry\-flavor\fR).
69
\fB\-\-parent\-wid\fR \fIN\fR
70
Use window ID \fIN\fR as the parent window for positioning the window.
71
Note, that this is not fully supported by all flavors of \fBpinentry\fR.
73
\fB--display\fR \fISTRING\fR, \fB--ttyname\fR \fISTRING\fR, \fB--ttytype\fR \fISTRING\fR, \fB--lc-type\fR \fISTRING\fR, \fB--lc-messages\fR \fISTRING\fR
74
These options are used to pass localization information to
75
\fBpinentry-flavor\fR. They are required because
76
\fBpinentry-flavor\fR is usually called by
77
some background process which does not have any information on the
78
locale and terminal to use. Assuan protocol options are an
79
alternative way to pass these information.
81
m4_ifelse(flavor, {curses}, {}, {.BR pinentry-curses (1),
83
m4_ifelse(flavor, {gtk}, {}, {.BR pinentry-gtk (1),
85
m4_ifelse(flavor, {gtk-2}, {}, {.BR pinentry-gtk-2 (1),
87
m4_ifelse(flavor, {qt}, {}, {.BR pinentry-qt (1),
92
The full documentation for
94
is maintained as a Texinfo manual. If the
96
package is installed, the command
100
should give you access to the complete manual.
102
This manual page was written by Peter Eisentraut for the Debian project.
added
removed
debian/pinentry.1.in
