Tue Oct 20 16:25:30 1998  Janne Snabb  <snabb@ripe.net>

	* Makefile.config, etc/attr-desc.config, etc/objs-desc.config,
	etc/ripedb.config-dist, Makefile.in, dbadd.pl, enparse.pl,
	maintainer.pl, pgp.pl, processdata.pl, rconf.pl, syntax.pl,
	template.pl: Added PGP authentication support.

	* adderror.pl: Don't add undef warnings (i.e. empty warning
	lines)

Tue Oct 20 14:47:44 1998  Janne Snabb  <snabb@ripe.net>

	* syncdb.pl: completed support for -p <portno> option
	in syncdb. It was only half-implemented.

	* pgpdata2ring.pl: Made a simple script for converting an
	existing DB key-certificate data file to a file with all
	the keys in it in normal PGP ASCII armored format. It can
	be used to import key-certificates to PGP key ring if for
	example key ring gets corrupted at some point or if setting
	up a mirror.

Mon Oct 19 14:08:34 1998  Janne Snabb  <snabb@ripe.net>

	* whoisd.pl: added setting of "real" user & group ids in
	addition to setting the efective ones. This is allows
	killing the server by UID in SYSV'ish machines (signal
	authentication is different from BSD) and should also
	prevent changing back to root if someone is able to crack
	to shell through whoisd.

	* whoisd.pl: replaced extremely non-portable 
	ioctl(.., XXX, ..) call with POSIX::setsid(). XXX was 
	hard-coded as TIOCNOTTY value from BSDI system header-files.

Thu Oct  1 16:10:52 1998  Janne Snabb  <snabb@ripe.net>

	* syntax.pl: change the parsing of date in "changed:"
	and "withdrawn:" so that entering a date in invalid format
	results in proper error message, instead of complaining about
	invalid e-mail address. (Fixed bug 1998-1)

Mon Sep 28 19:12:51 1998  Janne Snabb  <snabb@ripe.net>

	* syntax.pl: made some "as-in:" and "as-out:" error messages
	more descriptive -- now they print the complete offending entry
	instead of some partially parsed values. (Fixed bug 1998-45)

	* syntax.pl, misc.pl: Previously the word "brackets" meant
	symbols "{}" and "braces" meant the symbols "()". As far
	as I know, these terms are not exactly correct, and it
	seems that the implementor wasn't even quite sure about
	them, as they were mixed up in some places. I changed the
	error messages and subroutine names so that they are now
	consistent: braces = "{}", parenthes = "()" and
	brackets = "[]".

	* syntax.pl: some typo fixes in error messages (neigbor ->
	neighbour etc.)

Mon Sep 28 16:42:50 1998  Janne Snabb  <snabb@ripe.net>

	* whoisd.pl: added support for specifying option arguments
	with no intervening space. (for example "-Tinetnum
	193.166.28.1" works now) (Fixed bug 1998-2)

Thu Sep 24 18:13:52 1998  Janne Snabb  <snabb@ripe.net>

	* enparse.pl: fixed line-continuation problem (bug ID 1998-38),
	which caused attributes with continuation lines to eat up
	some lines from previous attributes. Commented out also some
	redundant and confusing code.

Thu Sep 24 16:23:11 1998  Janne Snabb  <snabb@ripe.net>

	* cross-notify.pl: changed sub add_cross_notify to
	return an empty list instead of undef (which is a list
	with one undef value) if there is no need to send mail
	about cross-notifications. This prevents obscure error
	messages "sh: syntax error at line 1: `end of file' unexpected",
	which were printed in sub send_cross_notifications when it
	tries to exec $MAILCMD with stdin redirected from file named
	(undef) (i.e. empty string).

Wed Sep 23 15:57:32 1998  Janne Snabb  <snabb@ripe.net>

	* dbadd.pl, internicstats2inetnums.pl, misc.pl, rconf.pl,
	syntax.pl, whoisd.pl: Many y2k fixes. Now "changed:" &
	"withdrawn:" dates are always converted to YYYYMMDD format
	when importing them. (Fixed bug 1998-31)

	Please notice that the log files are now also written with
	8 digit dates, which means that some changes might be needed
	in the support scripts.

Mon Nov 10 11:58:23 1997  Chris Fletcher  <chris@ripe.net>

	* src/net2net.pl (quad2int): fixed following
	with inc/dec kludge.
	
 * >If you send in an update of a route object in the classful
 * >net notation (e.g. 193.0.0.0) instead of the classless
 * >representation, you will get a warning message indicating
 * >that the route was rewritten to 127.255.255.255/24.
 * >You should find that you can lookup the original 
 * >route object in the database.  You should also find
 * >that you cannot lookup the new spurious route object,
 * >127.255.255.255\24.


