[Request] Hide Server in /whois

[Kito]

Good Morning,

I want to request a module which hides the server the user is on, in a whois.

I have seen it several times on a few networks. It look like this:

XY is using *.network.com Desc

If there is a module like this please post me a link.
And if there is a volunteer who could make it for me please answer in this post.
I would be VERY happy if someone could help me.

Greets
Danilo (Kito)

[Syzop]

There's no such option or module, and I thought there was a FAQ item about it.. but I guess I'm mistaken.

If you want to hide which server a user himself is currently connected to, that is not usefu as the user can see this by netstat and such.
If you are asking this so users won't be attacking your hub servers, then have a look at Doc: 8.6 Denial of Service attacks (DoS) [or: how to protect my hub].
You can also hide to users which servers are currently linked to which, by using set::options::flat-map to 'hide' your network map in /MAP and some other places, but that doesn't help much as whenever a server splits a user can see how the servers were linked
Your best protection is the first link I gave you.

EDIT: Sorry I initially missed the fact that you posted this in ''Unreal 3.2 Modules' and wasn't a regular support question, my reply however is still valid

[katsklaw]

MOD: Well lets just put it where it belongs.

my 2 cents, HIS* settings as found in ircu are a false sense of security, there are a bgillion other ways to get you network topology. While HIS* looks pretty for the girlies, It just causes any would be attacker to find other ways. DNS every server as they connect to them and just hit them randomly until desired effect is reached. If you are dumb enough to use load balancing software on your round robins it makes it even easier, attackers only have to hit your RR's which could spread the attack evenly but now all servers are being attacked instead of just one. If the attack is large enough it can saturate more than one server so not even you can get in! not to mention you just turned a single target DoS into a multi-target DDoS by distributing the attack yourself.

Yes, HIS* does cause an inconvenience to the attack, but only in the same way a chainlink fence stops your yard from flooding.

Long story short, if you allow access to users, it's impossible to block access from attacks. In this case you have to take the good with the bad.

[o_O]

This could be done if you make changes in m_whois.c and web.tv but you wouldn't get any support if you do it so better leave as it is

[katsklaw]

This could be done if you make changes in m_whois.c and web.tv but you wouldn't get any support if you do it so better leave as it is

Long story short, it doesn't really matter. Attackers can simply nslookup the roundrobin(s) and presto, 3 seconds later have all the server IPs in the pool so no sense in hiding those in /whois. The ones not in the pool can also be found with nslookup simply by reversing the server name. Any network that doesn't publish server names/IPs has empty servers and thus not worth attacking.

The only time not publishing servers is a benefit is for dedicated hubs and services and they shouldn't resolve at all since non-opers should be on them in the first place.