Re: ALL_TRUSTED hitting because of "has reserved IP"?

[Justin Mason <jm...@jmason.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Kris Deugau writes:
> I understand some of why these are hardcoded like this, but this is VERY
> dangerous - just because it's reserved by IANA does NOT mean it can't be
> allocated to someone tomorrow!  I once had a number of these "reserved"
> /8 blocks listed in my firewall, and it caused some truly annoying
> trouble.  Several months later, I was looking at the listing for some
> other reason, and noticed that one such block question was no longer
> reserved.  I removed *all* such entries immeditately in order to prevent
> further such problems.

agh, I thought we had this fixed previously.  Regardless, it's
thoroughly fixed in current SVN...

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFB5YotMJF5cimLx9ARAvuGAKCsm/ER5nQdaNQhsfs69TQMWAet/ACdEXKM
CGFj2S5TtuFRIaiVX45rZlc=
=zgHz
-----END PGP SIGNATURE-----

Re: ALL_TRUSTED hitting because of "has reserved IP"?

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

Justin Mason wrote:
> agh, I thought we had this fixed previously.  Regardless, it's
> thoroughly fixed in current SVN...
> 
> - --j.

It (removing 71/8 etc) wasn't committed to 3.0, only trunk.  3.0 hasn't 
been changed since September.


Daryl