Not even Channel Ops. Only IRC Operators can see true hosts.
Most implimentations of this turn the hostname from:
p34-max1.akl.ihug.co.nz
to
random.things.here.co.nz
Thus bans using *!*ident@*.co.nz still apply and work OK.
This method doesnt actually remove a lot of the ban features we still use.
Its usermode +x IRRC.0
Theres advantages and disadvantages to the system.... and thats all im
going to say on the matter.
At 17:00 20/05/2001 -0200, you wrote:
>On Sat, May 19, 2001 at 02:47:00PM +0200, Jean-Edouard BABIN wrote:
> > he ask why on undernet we can look le true host in user@host whereas on
> > infinit.net the host is chat.infinit.net for public, and juste channels op
> > and irc op can see the true host..
> >
> > i add that on other network they crypt it: aaa.bbb.ccc become ZdD.bbb.ccc
> > it's better for protection with bot
> >
> > le 18/05/01 4:00, Dominic Pilon ([EMAIL PROTECTED]) ecrivait:
> >
>[snipped]
>
>Smaller IRC networks actually have this feature, it's called hostname
>cloaking. I heard that it's being discussed for Undernet (I'm new on this
>list so I don't
>really know).
>
>Cloaking hides complete hostnames from end users. Only channel ops are able to
>see them and apply bans accordingly. This feature prevents harassment and
>port scans, but it is nowhere near perfect.
