summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--ChangeLog8
-rw-r--r--NEWS4
-rw-r--r--README172
3 files changed, 168 insertions, 16 deletions
diff --git a/ChangeLog b/ChangeLog
index 64e83cf18..e4f30cdcf 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2002-07-01 Werner Koch <wk@gnupg.org>
+
+ Released 1.1.90.
+
+ * INSTALL: Replaced by generic install file.
+ * README: Marked as development version and moved most stuff of
+ the old INSTALL file to here.
+
2002-06-30 Werner Koch <wk@gnupg.org>
* configure.ac: Link W32 version against libwsock32.
diff --git a/NEWS b/NEWS
index 51c42b666..143062950 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,5 @@
-Noteworthy changes in version 1.1.90
-------------------------------------------------
+Noteworthy changes in version 1.1.90 (2002-07-01)
+-------------------------------------------------
* New commands: --personal-cipher-preferences,
--personal-digest-preferences, and
diff --git a/README b/README
index de3093ec2..1e9f1b934 100644
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
GnuPG - The GNU Privacy Guard
-------------------------------
- Version 1.0
+ Version 1.1
Copyright 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
@@ -13,6 +13,14 @@
WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+
+ ****************************************************
+ ** Please note that is is a DEVELOPMENT VERSION **
+ ** and as such not suitable for production use **
+ ** unless you really know what you are doing. **
+ ****************************************************
+
+
Intro
-----
@@ -42,13 +50,11 @@
Installation
------------
+ Please read the file INSTALL and the sections in this file
+ related to the installation. Here is a quick summary:
- Please read the file INSTALL!
-
- Here is a quick summary:
-
- 1) Check that you have unmodified sources. The below on how to do this.
- Don't skip it - this is an important step!
+ 1) Check that you have unmodified sources. The below on how
+ to do this. Don't skip it - this is an important step!
2) Unpack the TAR. With GNU tar you can do it this way:
"tar xzvf gnupg-x.y.z.tar.gz"
@@ -62,10 +68,6 @@
6) "make install"
7) You end up with a "gpg" binary in /usr/local/bin.
- Note: Because some old programs rely on the existence of a
- binary named "gpgm" (which was build by some Beta versions
- of GnuPG); you may want to install a symbolic link to it:
- "cd /usr/local/bin; ln -s gpg gpgm"
8) To avoid swapping out of sensitive data, you can install "gpg" as
suid root. If you don't do so, you may want to add the option
@@ -74,7 +76,6 @@
How to Verify the Source
------------------------
-
In order to check that the version of GnuPG which you are going to
install is an original and unmodified one, you can do it in one of
the following ways:
@@ -121,7 +122,6 @@
Documentation
-------------
-
The manual will be distributed separate under the name "gph".
An online version of the latest manual draft is available at the
GnuPG web pages:
@@ -143,7 +143,6 @@
Introduction
------------
-
Here is a brief overview on how to use GnuPG - it is strongly suggested
that you read the manual and other information about the use of
cryptography. GnuPG is only a tool, secure usage requires that
@@ -453,6 +452,151 @@
detailed information about the errors.
+ Configure options
+ -----------------
+ Here is a list of configure options which are sometime useful
+ for installation.
+
+ --enable-static-rnd=<name>
+ Force the use of the random byte gathering
+ module <name>. Default is either to use /dev/random
+ or the standard Uix module. Value for name:
+ egd - Use the module which accesses the
+ Entropy Gathering Daemon. See the webpages
+ for more information about it.
+ unix - Use the standard Unix module which does not
+ have a very good performance.
+ linux - Use the module which accesses /dev/random.
+ This is the first choice and the default one
+ for GNU/Linux or *BSD.
+ none - Do not linkl any module in but rely on
+ a dynmically loaded modules.
+
+ --with-egd-socket=<name>
+ This is only used when EGD is used as random
+ gatherer. GnuPG uses by default "~/.gnupg/entropy"
+ as the socket to connect EGD. Using this option the
+ socket name can be changed. You may use any filename
+ here with 2 exceptions: a filename starting with
+ "~/" uses the socket in the homedirectory of the user
+ and one starting with a "=" uses a socket in the
+ GnuPG homedirectory which is bye default "~/.gnupg".
+
+ --with-included-zlib
+ Forces usage of the local zlib sources. Default is
+ to use the (shared) library of the system.
+
+ --with-included-gettext
+ Forces usage of the local gettext sources instead of
+ the one provided by your system.
+
+ --disable-nls
+ Disable NLS support (See the file ABOUT-NLS)
+
+ --enable-m-guard
+ Enable the integrated malloc checking code. Please
+ note that this feature does not work on all CPUs
+ (e.g. SunOS 5.7 on UltraSparc-2) and might give
+ you a bus error.
+
+ --disable-dynload
+ If you have problems with dynamic loading, this
+ option disables all dynamic loading stuff.
+
+ --disable-asm
+ Do not use assembler modules. It is not possible
+ to use this on some CPU types.
+
+
+ Installation Problems
+ ---------------------
+ If you get unresolved externals "gettext" you should run configure
+ again with the option "--with-included-gettext"; this is version
+ 0.10.35 which is available at alpha.gnu.org.
+
+ If you have other compile problems, try the configure options
+ "--with-included-zlib" or "--disable-nls" (See ABOUT-NLS) or
+ --disable-dynload.
+
+ We can't check all assembler files, so if you have problems
+ assembling them (or the program crashes) use --disable-asm with
+ ./configure. The configure scripts may consider several
+ subdirectories to get all available assembler files; be sure to
+ delete the correct ones. The assembler replacements are in C and
+ in mpi/generic; never delete udiv-qrnnd.S in any CPU directory,
+ because there may be no C substitute. Don't forget to delete
+ "config.cache" and run "./config.status --recheck".
+
+ Some make tools are broken - the best solution is to use GNU's
+ make. Try gmake or grab the sources from a GNU archive and
+ install them.
+
+ On some OSF you may get unresolved externals. This is a libtool
+ problem and the workaround is to manually remove all the "-lc -lz"
+ but the last one from the linker line and execute them manually.
+
+ On some architectures you see warnings like:
+ longlong.h:175: warning: function declaration isn't a prototype
+ or
+ http.c:647: warning: cast increases required alignment of target type
+ This doesn't matter and we know about it (actually it is due to
+ some warning options which we have enabled for gcc)
+
+
+ Specific problems on some machines
+ ----------------------------------
+
+ * IBM RS/6000 running AIX:
+
+ Due to a change in gcc (since version 2.8) the MPI stuff may
+ not build. In this case try to run configure using:
+ CFLAGS="-g -O2 -mcpu=powerpc" ./configure
+
+ * Compaq C V6.2 for alpha:
+
+ You may want to use the option "-msg-disable ptrmismatch1"
+ to get rid of the sign/unsigned char mismatch warnings.
+
+ * SVR4.2 (ESIX V4.2 cc)
+
+ Due to problems with the ESIX as, you probably want to do
+ CFLAGS="-O -K pentium" ./configure --disable-asm
+ Reported by Reinhard Wobst.
+
+
+
+ The Random Device
+ -----------------
+
+ Random devices are available in Linux, FreeBSD and OpenBSD.
+ Operating systems without a random devices must use another
+ entropy collector. One entropy collector called rndunix and
+ available as an extension module. You should put the line:
+ load-extension rndunix
+ into your ~/.gnupg/options file unless you have used the proper
+ configure option.
+
+ This collector works by running a lot of commands that yield more
+ or less unpredictable output and feds this as entropy into the
+ random generator - It should work reliably but you should check
+ whether it produces good output for your version of Unix. There
+ are some debug options to help you (see cipher/rndunix.c).
+
+ Creating an RPM package
+ -----------------------
+ The file scripts/gnupg.spec is used to build a RPM package (both
+ binary and src):
+ 1. copy the spec file into /usr/src/redhat/SPECS
+ 2. copy the tar file into /usr/src/redhat/SOURCES
+ 3. type: rpm -ba SPECS/gnupg.spec
+
+ Or use the -t (--tarbuild) option of rpm:
+ 1. rpm -ta gnupg-x.x.x.tar.gz
+
+ The binary rpm file can now be found in /usr/src/redhat/RPMS, source
+ rpm in /usr/src/redhat/SRPMS
+
+
How to Get More Information
---------------------------