Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Service Aliases  (Read 11477 times)

0 Members and 1 Guest are viewing this topic.

anizaeger

  • Anope User
  • Offline Offline
  • Posts: 8
Service Aliases
« on: May 06, 2010, 12:46:25 PM »

Version 1.8 had service aliases (NickServAlias, ChanServAlias, etc...) which I can't seem to find on 1.9.  Was the feature removed, and if so, will it be put back eventually or is it a permanent removal?
Logged

LEthaLity

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 307
    • LEthaLity
Re: Service Aliases
« Reply #1 on: May 06, 2010, 02:33:27 PM »

I assume you want to give the *Servs different names, it is still there, look at one of the Serv config blocks, for instance NickServ:
nickserv
{
   nick = "NickServ"
   description = "Nickname Registration Service"

nick sets it..
Logged

n0kS Phr33d0m

  • Contributor
  • *
  • Offline Offline
  • Posts: 25
Re: Service Aliases
« Reply #2 on: May 06, 2010, 02:40:17 PM »

Negative Huston. He wants aliases for his *Serv(s) like:
(in 1.8.4)

NickServName    "NickServ"  "Nickname Server"
ChanServName    "ChanServ"  "Channel Server"
MemoServName    "MemoServ"  "Memo Server"
BotServName     "BotServ"   "Bot Server"
HelpServName    "HelpServ"  "Help Server"
OperServName    "OperServ"  "Operator Server"
GlobalName      "Global"    "Global Noticer"
DevNullName     "DevNull"   "/dev/null -- message sink"
HostServName    "HostServ"  "vHost Server"



... and ...



NickServAlias    "NS"  "Nickname Server Forwarder"
ChanServAlias    "CS"  "Channel Server Forwarder"
MemoServAlias    "MS"  "Memo Server Forwarder"
BotServAlias     "BS"   "Bot Server Forwarder"
HelpServAlias    "Helper"  "Help Server Forwarder"
OperServAlias    "OS"  "Operator Server Forwarder"
GlobalAlias      "System"    "Global Noticer Forwarder"
#DevNullAlias     "DevNull2"   "/dev/null -- message sink Forwarder"
HostServAlias    "HS"  "vHost Server Forwarder"



and then: (/whois)

[15:39:28] * [NickServ] (Services@Politeia.Services): Nickname Server
[15:39:28] * [NickServ] is using modes +iTSqp
[15:39:28] * [NickServ] is connecting from *@Politeia.Services
[15:39:28] * [NickServ] Politeia.Services :Things must be just
[15:39:28] * [NickServ] is a Network Service
[15:39:28] * [nickserv] End of WHOIS list.

... and ...

[15:39:31] * [NS] (Services@Politeia.Services): Nickname Server Forwarder
[15:39:31] * [NS] is using modes +iTSqp
[15:39:31] * [NS] is connecting from *@Politeia.Services
[15:39:31] * [NS] Politeia.Services :Things must be just
[15:39:31] * [NS] is a Network Service
[15:39:31] * [ns] End of WHOIS list.
Logged

anizaeger

  • Anope User
  • Offline Offline
  • Posts: 8
Re: Service Aliases
« Reply #3 on: May 06, 2010, 09:54:39 PM »

Don't worry, I'm kinda having the same issue on the Unreal forums trying to see if there is a way to redirect private messages in the same way in case there's no way to do it on the services; they think I'm talking about their kind of aliases.  LoL
Logged

Naram Qashat

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 192
    • CBX's Sprite Animations
Re: Service Aliases
« Reply #4 on: May 06, 2010, 10:49:47 PM »

Yes, this was removed from 1.9.x as it was deemed worthless since most current IRCds can do aliases from the IRCd end and it's recommended to do things that way instead of wasting more resources on an extra pseudo-client.
Logged

anizaeger

  • Anope User
  • Offline Offline
  • Posts: 8
Re: Service Aliases
« Reply #5 on: May 07, 2010, 01:09:07 AM »

Unfortunately, aliases on IRCDs won't, to my knowledge, redirect an incorrectly addressed message sent to NickServ its proper recipient, NS (assuming a network uses such a naming scheme).  Considering that all the core pseudo-clients are run by BotServ, would it be possible to implement services-side aliasing as a module in for BotServ?
Logged

Naram Qashat

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 192
    • CBX's Sprite Animations
Re: Service Aliases
« Reply #6 on: May 07, 2010, 01:16:07 AM »

Then your knowledge is wrong.  IRCd aliases are designed to send messages to a specific client, and are more secure than using /msg <nick> since there is NO chance of the message going to the wrong target since you set the alias to go to the correct client.
Logged

anizaeger

  • Anope User
  • Offline Offline
  • Posts: 8
Re: Service Aliases
« Reply #7 on: May 07, 2010, 01:54:59 AM »

So you're saying that I can write an alias that would capture "PRIVMSG NickServ :blah" and change it to "PRIVMSG NS :blah"?
Logged

Naram Qashat

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 192
    • CBX's Sprite Animations
Re: Service Aliases
« Reply #8 on: May 07, 2010, 01:59:38 AM »

No, you can't do that unless the IRCd handles that.  But personally, I would educate your users against using PRIVMSG <nick> when messaging Services, and to use IRCd-side aliases instead.  For one, you won't get people trying to masquerade as a Service and getting messages from people accidentally, and for two, you have finer control over where and how the message gets sent.
Logged

Axel Terizaki

  • Anope User
  • Offline Offline
  • Posts: 1
Re: Service Aliases
« Reply #9 on: October 06, 2010, 01:45:48 PM »

Hello.

I've recently ran into the same problem, and can't really understand why this was a good idea to delete that feature.

Following this topic, I asked on UnrealIRCd's forums about it, and they said it wasn't the IRCd's job to do these kind of things.

So I humbly ask, can this come back in a future version of Anope? This would be a great help to me and my users.

Renaming Nickserv / Chanserv and others is quite worthless if you can't make aliases of them since some IRC clients's auto-identify features rely on /msg nickserv and not the /nickserv command itself (which can be aliased to /msg whatever.)

Thanks in advance.
Logged

katsklaw

  • Supporter
  • Anope User
  • Offline Offline
  • Posts: 537
Re: Service Aliases
« Reply #10 on: October 06, 2010, 08:15:59 PM »

To be clear, what I told this user is that it's not the ircd's job to redirect PRIVMSG targets from one nick to another. ie /msg nickserv gets redirected to pseudoserv. This issue isn't about ircd side aliases which for this context I would agree is the job of the ircd.

I said it is *NOT* the ircd's job to forward or redirect from one target to another and if any services package wanting to do so they needed to do so internally, which is what the old *ServAliases did.

Thanx
Logged

katsklaw

  • Supporter
  • Anope User
  • Offline Offline
  • Posts: 537
Re: Service Aliases
« Reply #11 on: October 10, 2010, 03:17:34 PM »

Yes, this was removed from 1.9.x as it was deemed worthless since most current IRCds can do aliases from the IRCd end and it's recommended to do things that way instead of wasting more resources on an extra pseudo-client.

BTW, ircd side aliases are *not* the same thing as *ServAliases. The ircd cannot and should not ever do what *ServAliases done!

ircd alias converts /nickserv into PRIVMSG NickServ@ServicesName whereas *ServAlias allows you to type /msg NickServ and NickServ2 will answer.

Directly from Anope 1.8.4 example.conf:

# ...Alias <nick> <string>  [OPTIONAL]
#     Specify alternate nicknames for services. When a user will /msg
#     NickServAlias something, it will be forwarded to NickServName, and
#     NickServName will answer. This can be used to ease the migration
#     from another network, for example if your services are called
#     NickKeeper, ChanKeeper, etc ... and the other network calls them
#     NickServ, ChanServ, etc ...



Lastly, just because a few people deem the feature worthless, doesn't mean the rest of the world does too.
Logged
Pages: [1]   Go Up