I know Quension was against hostmasking, in general. There have been many threads about general hostmasking; all were shot down or left to die without change.If it could be done, to help those nonopers who help the network, it would be very much appreciated by those of us who help in official help channels.
@Holbrook
Wouldn't there be a way to ID to nickserv before using the nick (to bypass your point); i.e. /nickserv identify nickname nickpass? The user should be able to connect with one nickname, ID to nickserv with the aforementioned command, then change to the nickname (whereby the IRCd would auto-change the hostmask)?
Perhaps I am mistaken. Thanks for the replies.
PapaSmurf
On Monday, January 26, 2015 1:31 AM, Holbrook Bunting <holbrook@dal.net> wrote:
Yes and no. If I remember correctly, bahamut contains an SVScommand to change a users hostname as it appears in a whois.
So to get something like this would mean adding into services a flag for say, helpers, into nickserv for a registered nickname.
The only problem here is that until the user has identified to nickserv, or is using the applicable nickname when connecting and matching a user@host mask in that nicknames access list; the period between successful connection and services telling the ircd to change the visible hostname, their real hostname is exposed.
All I need to do is to put them on notify and have my irc client Whois them. The only way around that would be to have them connect using a different/random nickname, identifying first, then change/join channels.
- Holbrook
On Sunday, January 25, 2015, Jimmy Hess <mysidia@gmail.com> wrote:
On Tue, Jan 20, 2015 at 11:48 AM, PapaSmurf <freedried@yahoo.com>
wrote: > Hello all.
Hi,
I believe the matter of choosing to apply masks to the people who are
help channel operators or not is purely a policy matter, as the
technical means already exists within Ircd to implement that; it is
just services that needs to take actions to set hostmasks as desired.
There might be some minor changes required to services code; however,
we cannot very well submit patches or specific suggested changes on
sources we cannot see.
I would say the situation is unfortunate, but the _real_ problem is
that Ircd is revealing user IP addresses by default, in the first
place. This is historical, and reflects the fact that in the 1980
/ 1990s internet, it was perfectly acceptable to reveal the IP
address of end users of a service, but these days that results in
breach of privacy and indeed facilitates abuse such as DoS or directed
hacking attacks against IRC users.
And hostmasking for the general public would address at least a major
aspect of the problem, which affects or can affect many users beyond
the help channel AOPs.
Basically, the argument is cherrypicking helpers or opers for
hostmasking functionality is not a good approach to begin with ---
the protection could be extended to more users.
> I am PapaSmurf on DALnet. This post has nothing to do with hostmasking for
> the general public. I have been assisting users, in DALnet help channels,
> since August/September 1998. Non-oper helpers, ever since I have been on IRC, have been subjected to packeting, DDoS, and computer invasions from annoying individuals.
--
-JH
_______________________________________________
DALnet-src mailing list
DALnet-src@lists.dal.net
https://lists.dal.net/mailman/listinfo/dalnet-src
--
holbrook / zort / srd
SA: The halcyon team