IPFilter 4.1.31

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
One of these days I'll get my software release story into shape...

But given the rather stupid mistake I let creep into 4.1.30, I've
got no choice but to say "oops, sorry" and bump it up and make
a new release.  This does give me a chance to attempt to lick
some of the other Solaris problems too.

How did it happen?  The testing I did was to see if the new
port numbers were random, after NAT - they were - but
given that I was testing with a huge port number range, it
was easy for the numbers to be correctly inside that range
whilst actually being wrong. To ensure I got this fixed, it
was necessary to unbackburner some development to test
the "random" port bits and give ipftest a not-so-nearly-random
random function so that deterministic testing could be done
on any platform.

Apologies,
Darren

http://coombs.anu.edu.au/~avalon/ip_fil4.1.31.tar.gz
http://coombs.anu.edu.au/~avalon/patch-4.1.31.gz

MD5 (ip_fil4.1.31.tar.gz) = 086741c4eb528b1e959b6be2ae9650d6
MD5 (patch-4.1.31.gz) = fae8b5aa68370f14c0b30728332e5848

4.1.31 - Release 27 July 2008

* compiling arc4random.c is challenging on solaris 10 or solaris without gcc

* SunOS4 doesn't have a curproc, but it does have u.

* The fix for 2020447 generated random port numbers but not within the
~  range specified in the map rule.  Add in a regression test to verify
~  that the "random" part works.

4.1.30 - Release 24 July 2008

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iEYEARECAAYFAkiMV3kACgkQP7JIXtvLbFUZGACdGLP8UWqyxIn429ZHcS/Ns/5r
5lAAoJVde9IOAWX/6vxEdj97T7fSbQxB
=ZRjP
-----END PGP SIGNATURE-----