bintopia.com - BlackDragon

Linux iai.iais.com.au 3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64
Apache
221.121.155.106
78 Domain

URL to Upload

File Name

Upload Method

Upload from URL

File Name : README

PIN Entry
---------

This is a collection of simple PIN or passphrase entry dialogs which
utilize the Assuan protocol as described by the aegypten project; see
http://www.gnupg.org/aegypten/ for details.

There are programs for different toolkits available.  For all GUIs it
is automatically detected which modules can be built, but it can also
be requested explicitely.

GUI		OPTION			 DEPENDENCIES
Curses		--enable-pinentry-curses Curses library, for example ncurses
GTK+ V1.2	--enable-pinentry-gtk	 Gimp Toolkit Library Version 1.2
			 		 eg. libgtk-1.2 and libglib-1.2
GTK+ V2.0	--enable-pinentry-gtk2	 Gimp Toolkit Library, Version 2.0
					 eg. libgtk-x11-2.0 and libglib-2.0
Qt		--enable-pinentry-qt	 Qt, eg. libqt or libqt-mt
Qt4		--enable-pinentry-qt4	 Qt4

The GTK+ and Qt pinentries can fall back to the curses mode.  The
option to enable this is --enable-fallback-curses, but this is also
detected automatically in the same way --enable-pinentry-curses is.
The fallback to curses also works if --disable-pinentry-curses is
specified.  So to disable linking to curses completely you have to
pass --disable-fallback-curses to the configure script as well.

Examples:
* To only build the GTK+ 1.2 pinentry with curses support:
./configure --enable-pinentry-gtk --enable-fallback-curses \
	--disable-pinentry-curses --disable-pinentry-qt

* To build the Qt pinentry, and the other pinentries if they are
  supported:
./configure --enable-pinentry-qt

* To build everything that is supported (complete auto-detection):
./configure

Some of the code is taken from Robert Bihlmeyer's Quintuple-Agent.
For security reasons, all internationalization has been removed.  The
client is expected to tell the PIN entry the text strings to be
displayed.

Curses Pinentry
---------------

The curses pinentry supports colors if the terminal does.  The colors
can be specified by the --colors=FG,BG,SO option, which sets the
foreground, background and standout colors respectively.  The standout
color is used for error messages.  Colors can be named by any of
"black", "red", "green", "yellow", "blue", "magenta", "cyan" and
"white".  The foreground and standout color can be prefixed by
"bright-", "bright", "bold-" and "bold", and any of these prefixes has
the same effect of making the color bolder or brighter.  Two special
color names are defined as well: "default" chooses the default color,
and "none" disables use of colors.  The name "none" is only meaningful
for the standout color and in this case a reversed effect is used for
error messages.  For the other colors, disabling colors means the same
as using the defaults.  The default colors are as follows:

Foreground:	Terminal default
	Background:	Terminal default
	Standout:	Bright red

Note that color support is limited by the capabilities of the display
terminal.  Some color combinations can be very difficult to read, and
please know that colors are perceived differently by different people.

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	root/root	drwxr-xr-x	2016-12-12 03:23:50
..	dir	-	root/root	drwxr-xr-x	2026-01-07 03:21:50
AUTHORS	file	364 B	root/root	-rw-r--r--	2007-07-06 12:52:35
COPYING	file	14.78 KB	root/root	-rw-r--r--	2005-09-03 10:55:16
ChangeLog	file	69.69 KB	root/root	-rw-r--r--	2010-12-16 03:55:30
NEWS	file	5.11 KB	root/root	-rw-r--r--	2010-12-16 12:36:21
README	file	2.89 KB	root/root	-rw-r--r--	2008-10-17 12:59:45
THANKS	file	290 B	root/root	-rw-r--r--	2010-05-03 02:05:56
TODO	file	869 B	root/root	-rw-r--r--	2008-11-12 10:34:00