0.3 ready

README

@@ -1,8 +1,12 @@
 
 		  GNUPG - The GNU Privacy Guard
 		 -------------------------------
+			  Version 0.3
 
-    THIS IS ALPHA SOFTWARE, YOU MAY ENCOUNTER SOME BUGS.
+
+    As you can see from the version number, the program may have some
+    bugs and some features may not work at all - please report this to
+    the mailing list.
 
     On a Linux box (version 2.x.x, alpha or x86 CPU) it should
     work reliably.  You may create your key on such a machine and
@@ -21,27 +25,22 @@
 
     Please subscribe to g10@net.lut.ac.uk by sending a mail with
     the word "subscribe" in the body to "g10-request@net.lut.ac.uk".
+    This mailing is closed (only subscribers can post) to avoid spam.
 
     See the file COPYING for copyright and warranty information.
 
     Due to the fact that GNUPG does not use use any patented algorithm,
     it cannot be compatible with old PGP versions, because those use
     IDEA (which is patented worldwide) and RSA (which is patented in
-    the United States until Sep 20, 2000).  I'm sorry about this, but
+    the United States until Sep 20, 2000).
-    this is the world we have created (e.g. by using proprietary software).
 
-    Because the OpenPGP standard is still a draft, GNUPG now interoperates
+    GNUPG is in most aspects compatible with other OpenPGP implementations.
-    with it and PGP 5.	The MUA Mutt will soon support GNUPG; it has a
-    mode to fallback to another program if the received message has been
-    created with RSA or IDEA.
 
-    The default algorithms used by GNUPG are ElGamal for public-key
+    The default algorithms are now DSA and ELGamal.  ELGamal for signing
-    encryption and signing; Blowfish with a 128 bit key for protecting
+    is still available, but due to the larger size of such signatures it
-    the secret-key components, conventional and session encryption;
+    is depreciated (Please note that the GNUPG implementation of ElGamal
-    RIPE MD-160 to create message digest.  DSA, SHA-1, CAST and TIGER are
+    signatures is *not* insecure).  Symmetric algorithms are: Blowfish
-    also implemented, but not used by default.	I decided not
+    and CAST5,	Digest algorithms are MD5, RIPEMD160, SHA1 and TIGER/192.
-    to use DSA as the default signing algorithm, because it allows only
-    for 1024 bit keys and this may not be enough in a couple of years.
 
 
 
@@ -321,8 +320,6 @@
     -----------
     This is work in progress, so you may find duplicated code fragments,
     ugly data structures, weird usage of filenames and other things.
-    I will run "indent" over the source when making a real distribution,
-    but for now I stick to my own formatting rules.
 
     The primary FTP site is "ftp://ftp.guug.de/pub/gcrypt/"
     The primary WWW page is "http://www.d.shuttle.de/isil/crypt/gnupg.html"
@@ -330,7 +327,8 @@
     If you like, send your keys to <gnupg-keys@isil.d.shuttle.de>; use
     "gpg --export --armor | mail gnupg-keys@isil.d.shuttle.de" to do this.
 
-    Please direct bug reports to <gnupg-bugs@isil.d.shuttle.de> or better
+    Please direct bug reports to <gnupg-bugs@gnu.org> or better
-    post them to the mailing list <g10@net.lut.ac.uk>.
+    post them to the mailing list <g10@net.lut.ac.uk> (this is a closed list,
+    please subscribe before posting).
 
 

VERSION

@@ -1 +1 @@
-0.2.19d
+0.3.0

zlib/Makefile

@@ -71,6 +71,7 @@ CATOBJEXT = .gmo
 CC = gcc
 CPP = gcc -E
 DATADIRNAME = share
+DYNLINK_LDFLAGS = -rdynamic
 G10_LOCALEDIR = /usr/local/share/locale
 GENCAT = 
 GMOFILES =  de.gmo it.gmo
@@ -91,7 +92,7 @@ POSUB = po
 RANLIB = ranlib
 USE_INCLUDED_LIBINTL = yes
 USE_NLS = yes
-VERSION = 0.2.19c
+VERSION = 0.3.0
 ZLIBS = 
 l = 
 
@@ -121,7 +122,7 @@ LIBRARIES =  $(noinst_LIBRARIES)
 DEFS = -DHAVE_CONFIG_H -I. -I$(srcdir) -I..
 CPPFLAGS = 
 LDFLAGS = 
-LIBS = -lz
+LIBS = -ldl -lz
 libzlib_a_LIBADD = 
 libzlib_a_OBJECTS =  adler32.o compress.o crc32.o gzio.o uncompr.o \
 deflate.o trees.o zutil.o inflate.o infblock.o inftrees.o infcodes.o \