Re: hostmangling in new ircd

On Mon, Aug 22, 2005 at 10:39:13AM +0000, Andy Smith wrote:
> If you have a spare moment could you log in to one of our testnet
> servers, e.g. strugglers.net port 7500 and try and break[1] or
> otherwise defeat[2] the hostmangling that Mark R has put in?:
> 
> 10:34 -!- grifferz [~andy-zUHCcq+i6BtDM3tNdDN3uDDEoF5KDggSZ+GEbx8BII3YtjvyW6yDsg@public.gmane.org]

Ryan pointed out that Blitzed-0xb8e84e39.blitzed.eu.org could
possibly be a real existing host, and also that if I were to connect
as e.g. foo-rcD4agzmKD/[email protected] then my mangled host is going to be
something like [email protected] which could be registered
by anyone.

Can anyone think of a way we could make the hosts into invalid ones?
Just putting blitzed at the end would do it but then we'd end up
with hosts like:

Blitzed-0xb8e84e39.blitzed.eu.org.blitzed

which when banned by many scripts/clients would give a ban like
*.blitzed.eu.org.blitzed - doesn't get banned when user is set -q
again.

We could change the "-" into an underscore:

foo@Blitzed_0x12345678.net

That isn't a valid domain.  Still has problems:

- Although "_" isn't valid in internet hostnames, some broken DNS
  servers do allow it and as a result there are real hosts on the
  internet with "_" in them.

- Since "_" is technically not valid there may be scripts and
  clients that will not accept that in hostnames.

What do other networks with masking/mangling do?  As far as I can
see the only way to make completely invalid hosts is to add your own
TLD on the end.

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

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

iD8DBQFDCv37IJm2TL8VSQsRAl84AJ9LkAadNVU9OguhSJJEKwOQFZ74SwCgqruC
w1YMlzRnEfLsDVIiESGfj4o=
=N1V5
-----END PGP SIGNATURE-----