I think simple hostmangling would do the trick. For example, a user with h-123-123-123-123.telia.com would mask to Dalnet-<checksum>.telia.com, where the checksum part would consist of a salt value set in ircd.conf. The real IP can still be shown to IRC Operators. On another note, +b/+E/+I etc should still work on both the mangled host and the real IP, so users don't ban evade with host mangling. We implemented this in fqircd (based on Bahamut 1.8 iirc, development has been stalled for a good number of years) and it has been working great. Should be quite an easy implementation to do with Bahamut, the main issue here seems to be whether to allow some kind of host mangling on DALnet. Regards, Andreas aka ph0x (Sorry for top posting!) -----Original Message----- From: dalnet-services-bounces@lists.dal.net [mailto:dalnet-services-bounces@lists.dal.net] On Behalf Of Jimmy Hess Sent: Saturday, July 20, 2013 12:32 AM To: Holbrook Bunting Cc: dalnet-src@dal.net; dalnet-services@dal.net Subject: [DALnet-services] Re: [DALnet-src] User hostmasking On 7/19/13, Holbrook Bunting <holbrook@dal.net> wrote:
To keep from them changing their host like you suggest would be to place a limit on how often they can change their hostname for said nickname. Once a week? Once a month? [snip] I would say it's important that the Mask displayed not be false. The hostname should be an agreeable hostname according to internet standards; and it should not be possible to display a "fraudulent" mask such as OTHERISP.COM or DomainNotRegisteredToTheIRCUser.com.
The hostname should end with "masked.dal.net" or something else, that clearly demonstrates its a masked name, that could never be registered by anyone else; even under the new ICANN Generic TLDs program. Mandatory inclusion of a HEXCODE as I suggested above, also has great benefits, and I would strongly suggest that. If host masking is implemented; users should not be allowed to create "confusion"; by pretending "this is my real hostname", convincingly, when in fact, it is some kind of fiction. If custom domains are allowed, then the user should be required to demonstrate they can receive mail sent to postmaster@domain.example, or Administrative contact of the domain listed in WHOIS OR that there is a forward A record for that domain to an IP address that user has exclusive control over. -- -JH _______________________________________________ DALnet-services mailing list DALnet-services@lists.dal.net https://lists.dal.net/mailman/listinfo/dalnet-services