Dear colleagues, We have made available the new release of RIPE Perl database software at our fto site. You can find it at ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.3.1.tar.gz Please find attached notes of the new release. Best regards, RIPE NCC DB Group ----------------- RELEASE NOTES for RIPE Database 2.3.1 This is a bugfix release with no new functionality added. There are some operational changes which should be transparent to the end user but ease the database maintenance and (dramatically) improve performance. SUPPORTED SYSTEMS ================= This release has been tested with perl 5.004_04 on bsdi3.1 and Solaris 2.6 systems. Please let us know if you have problems running it on other systems. CHANGES ======= Incorporated MAXLISTLENGTH and MAXSTRINGCOMPONENTS variables into the configuration file. They define the internal buffer sizes for reindexing; MAXLISTLENGTH defines the max length of the list of index entries, MAXSTRINGCOMPONENTS (name preserved for historical reasons) determines the number of entries for classless indices. Whoisd: added a 3 seconds delay before denied connections are dropped. In the inet6num objects, quads are zero padded to improve readability. Comparison of objects set to ignore the differences in number of whitespaces. BUG FIXES ========= Maintainer checks for dbupdate -T (test database) were not correct. Fixed setpriority parameters for whoisd {-L|-M|-m}. If invoked with wrong uid, dbupdate would fail silently. Now prints a message and exits 75. A range in class A ending with ?.?.?.0 would be changed to ?.255.255.255. Also fixed /32 ranges (beginning=end). PERFORMANCE FIXES ================= Turning splits and joins into a regexp substitution in key handling code decreased the CPU usage. Nic-handle generation algorithm takes 30-40 steps now instead of up to a few thousand.
Hello All, I have modified the RIPE Whois database code version 2.3.0 to support the (public domain) GNU Privacy Guard program instead of the (commercial) PGP International program for the PGP authentication. The patch is attached. I'll port this patch to 2.3.1 in the next week or so. GNU Privacy Guard does not use any patented algorithms and is under the GPL licence, so you do not need to purchase any licences to use it. Adding support for both PGP and GNU PG to the RIPE whois database was not that straightforward so this work is not yet in production. I would appreciate any feedback on anyone who decides to try it. GNU Privacy Guard and PGP International can both be used to update the database as GNU PG supports PGPi 5.x keys as well as the IETF standard for OpenPGP (RFC2440). Thanks to the RIPE-NCC for making their code available as always! Paulg. References:: GNU Privacy Guard: http://www.gnupg.org PGP International: http://www.pgpi.org OpenPGP WG: http://www.ietf.org/html.charters/openpgp-charter.html __________________________________________________________________________ For PGP Key ID B49E3514, mailto:paulg@apnic.net send mail with Subject: pgp-key-request phoneto:+61-7-3367-0490 Paul Gampe - Technical Team - APNIC Pty Ltd faxto:+61-7-3367-0482 __________________________________________________________________________
Hi Paul, this is great! We'll be looking at this. We have been interested in GNU PG for a long time and it is nice to see that it has finally come to a usable state. We'll be looking into the possibility of making this patch a standard part of the current database. As you know we are really busy with the re-implementation now and would like to finish that as soon as possible. Joao At 12:54 +1000 13/10/99, Paul Gampe wrote:
Hello All,
I have modified the RIPE Whois database code version 2.3.0 to support the (public domain) GNU Privacy Guard program instead of the (commercial) PGP International program for the PGP authentication. The patch is attached. I'll port this patch to 2.3.1 in the next week or so.
GNU Privacy Guard does not use any patented algorithms and is under the GPL licence, so you do not need to purchase any licences to use it.
Adding support for both PGP and GNU PG to the RIPE whois database was not that straightforward so this work is not yet in production. I would appreciate any feedback on anyone who decides to try it.
GNU Privacy Guard and PGP International can both be used to update the database as GNU PG supports PGPi 5.x keys as well as the IETF standard for OpenPGP (RFC2440).
Thanks to the RIPE-NCC for making their code available as always! Paulg.
References::
GNU Privacy Guard: http://www.gnupg.org PGP International: http://www.pgpi.org OpenPGP WG: http://www.ietf.org/html.charters/openpgp-charter.html
__________________________________________________________________________
For PGP Key ID B49E3514, mailto:paulg@apnic.net send mail with Subject: pgp-key-request phoneto:+61-7-3367-0490 Paul Gampe - Technical Team - APNIC Pty Ltd faxto:+61-7-3367-0482 __________________________________________________________________________
Attachment converted: Joao:gnupg.patch (TEXT/ALFA) (0003083A)
participants (3)
-
Joao Luis Silva Damas -
Paul Gampe -
RIPE Database Administration