Re: hostmangling in new ircd

On Thu, Aug 25, 2005 at 10:04:51PM +1000, Andryan Gunawan wrote:
> On 8/25/05, Andy Smith <[email protected]> wrote:
> > What is the problem with banning *.some.isp.com when you see
> > blitzed-w52g1.some.isp.com?
> 
> That one is fine, well most of the time. What happens when you need to
> ban several hosts on the same ISP but some other legit from same ISP
> from different location (perhaps normally it would include the
> location name in the hostname but got replaced up to the domain name)?

The current mangling code only replaces non-alphanumerics up to the
first dot.  Have a look at the big list of real -> mangled hosts I
posted earlier and see if you can finda problematic one.

David found one problematic one where they have the IP in hex in the
middle of the hostname, so it's still visible in the mangled host.

_______________________________________________
public mailing list
public-Hb7ITwsGSD4lroQnaJEqWdi2O/[email protected]
http://lists.blitzed.org/listinfo/public

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDDc4aIJm2TL8VSQsRAos9AJ9mPErDSugDlLUYXc1nU3jEt2c9QQCfQITm
6coRjHIAaTERNc4B7K94bjU=
=pIQ1
-----END PGP SIGNATURE-----