|
|
| Author |
Message |
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
 Posted: Sep 19, 2004 9:45am Post subject: |
 |
|
| pomme wrote: | | uchat wrote: | | ... Even EFnet uses a U:Line. |
The Ulines on Hybrid are -not- the same as the ulines on Unreal. Don't automatically assume that because Hybrid 6 has a U: line in the conf, that it does the same thing as a U: line on Bahamut or Unreal 3.1.x. The Ulines on Unreal determine if a server can use SVS* commands. The Ulines on Hybrid allow opers on remote servers to use remote klines on that server. By setting the oper mask to * and setting the server to your services server, you allow anything from services to place a remote kline on that server. Last I checked, Anope for Hybrid 7 used remote klines for its OperServ akill command, which required a U: line (U:lines are changed to shared klines in version 7) for services to be placed on each server for akills to function globally. |
The purpose of the U:Line is to allow remote changes to the local server. Therefore Unreal and Hybrid BOTH do just that. The U:Line abilities in Bahamut nor Unreal are strictly limited to only SVS* commands.
Bahmut and hybrid may focus the use of their U:Lines for different things .. but that doesn't mean that it's a different type of U:Line. A car is a car .. no matter what your driving style is. You put srvx on Hybrid and srvx will use Hybrid's U:Line abilities no different than that of Anope on Bahamut. |
|
| Back to top |
|
 |
Proto
Lurker
Joined: 23 May 2004
Posts: 150
Location: IRC
|
| Posted: Sep 19, 2004 11:47am Post subject: |
|
|
To bad you can't link srvx to hybrid since it only has bahamut and P10 protocols  |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
| Posted: Sep 19, 2004 12:49pm Post subject: |
|
|
which ever .. the point that a U:Line is a U:Line remains .. usage does not dictate type. Regardless if U:lines are used by opers or services or even a mIRC script that uses sockets to open another connection to the IRCd and connects as a U:Lined connection.
ircd-ratbox has a "shared" block. In the conf it compares it to a U:Line .. names are simple semantics.
Dodge calls one color "patriot blue" Chevy says "Midnight blue metallic" .. still the same damned color. |
|
| Back to top |
|
|
pomme
none
Joined: 05 Aug 2004
Posts: 28
|
| Posted: Sep 19, 2004 8:36pm Post subject: |
|
|
| You totally missed the point. Hybrid allows certain opers (on certain servers) to use remote klines on the local server. Unreal, Bahamut, etc allow certain servers to use special, and potentially abusive SVS* remote commands on local servers. Since when did Hybrid have an svsnick command? |
|
| Back to top |
|
|
pomme
none
Joined: 05 Aug 2004
Posts: 28
|
| Posted: Sep 19, 2004 8:41pm Post subject: |
|
|
| katsklaw wrote: | | You put srvx on Hybrid and srvx will use Hybrid's U:Line abilities no different than that of Anope on Bahamut. |
This is totally wrong!!! U:lines on Bahamut and Unreal were designed to allow certain servers to change a user's nick, change a user's usermodes, and change a user's hostname, among other things. U:lines on Bahamut do not do anything for bans. Hybrid uses U:lines for allowing remote opers to place local bans, and nothing else.
With Bahamut or Unreal, I HAVE to place a Uline for services on every server. With Hybrid, I only do that if I want services to be able to place klines on that server for Anope OperServ Akill functionality. Don't go around speaking out about Hybrid using Ulines the same way as other IRCds when it's totally wrong. |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
| Posted: Sep 20, 2004 5:02am Post subject: |
|
|
| pomme wrote: | | You totally missed the point. Hybrid allows certain opers (on certain servers) to use remote klines on the local server. Unreal, Bahamut, etc allow certain servers to use special, and potentially abusive SVS* remote commands on local servers. Since when did Hybrid have an svsnick command? |
It is YOU that missed the point .. it does NOT matter if OPERS do the changes or SERVERS are doing the changes! The fact is that remote changes are done through a U:Line and without U:Lines those changes can NOT be made! Period!
| Quote: |
Don't go around speaking out about Hybrid using Ulines the same way as other IRCds when it's totally wrong.
|
Show me exactly where I said that. OH! by the way .. my IRC Services includes ChanServ and I use ircd-ratbox which is almost completely Hybrid .. In fact you can link hybrid and ratbox. I have the option to have the channel bot in the channels or not .. and without the bot in channels it uses a U:Line to set channel modes. |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
| Posted: Sep 20, 2004 2:21pm Post subject: |
|
|
| Quote: |
U:lines on Bahamut do not do anything for bans. Hybrid uses U:lines for allowing remote opers to place local bans, and nothing else.
|
On Bahamut, ChanServ and OperServ/RootServ can change channelmodes, akills/glines and all sorts of channel functions. I'll say it again, Bahamut and Unreal do not limit U:Line usage to just svs* commands.
Hybrid-like U:Lines can be used by services to set channelmodes as well because my Services uses them! |
|
| Back to top |
|
|
openglx
none
Joined: 17 Jul 2003
Posts: 28
|
| Posted: Sep 21, 2004 6:04am Post subject: |
|
|
| katsklaw wrote: | | Hybrid-like U:Lines can be used by services to set channelmodes as well because my Services uses them! |
You miss the point, Hybrid-like U: doesn't do it. :P
Check your example.conf.short and make sure it tells you this:
| Code: |
#
# server "clusters"
# U: lines treat each of these servers as being part of your server cluster
# klines placed on this server will be forwarded to the servers named
# in the U lines here. LOCOPS will also be forwarded, but will appear
# as "SLOCOPS" instead of "LOCOPS"
#
# i.e. irc_hub.somewhere.net has leaf servers irc1.somewhere.net
# irc2.somewhere.net
# Hub server would have
U:irc1.somewhere.net:
U:irc2.somewhere.net
# each client server would have
U:irc_hub.somewhere.net
|
Got it? |
|
| Back to top |
|
|
katsklaw
Guru
Joined: 28 Jun 2004
Posts: 1114
|
| Posted: Sep 21, 2004 12:01pm Post subject: |
|
|
That's funny .. I see servers in that U:Line example .. perhaps that because servers can use U:Lines as well as opers. which by the way, is EXACTLY my point .. thanks for proving me correct.
All the debating of how the U:Line works isn't the issue to start with .. what was originally stated was that EFnet has U:Lines .. guess what .. they do!
If you want to continue to argue the semantics of how U:Lines are used .. go right ahead .. I know that my Services can affect my network the same as Bahamut type Services can. They affect channel modes including channel bans, giving ops/voice and other functions as well as do global network bans. I also know that it can be done whether the bot in the channel or not. I also know that my Services Server needs a U:Line.
Also as a side note Bahamut opers with umode +a can also manipulate channels in the same fashion as Services without being in channel. At one point in time opers could also ban users from the network without Services .. its called /akill and /rakill (not to be confused with /operserv akill). Not sure if Bahamut still does that because I haven't used it for a few years.
So appearently there isn't a difference in what happens .. and I could care less as to the semantics of how it happens. The fact is .. it happens on both Hybrid-like IRCds as well as Bahamut-like. It's with great irony that this debate has happened since Bahamut is Hybrid based to begin with. |
|
| Back to top |
|
|
pomme
none
Joined: 05 Aug 2004
Posts: 28
|
| Posted: Sep 21, 2004 5:58pm Post subject: |
|
|
| Quote: | | Hybrid-like U:Lines can be used by services to set channelmodes as well because my Services uses them! |
You're wrong once again. Ulines on Hybrid do not allow mode changes! Any server can set a mode, Ulined or not. That is handled with the MODE* command, regardless of Ulines... and Ulines don't do anything except allow remote klines.
* - Here is an example taken from m_mode.c: sendto_one(uplink, ":%s MODE %s %s",
source_p->name, parv[1], (parv[2] ? parv[2] : ""))
Also, if you look here near the top of that file:
struct Message mode_msgtab = {
"MODE", 0, 0, 2, 0, MFLG_SLOW, 0,
{m_unregistered, m_mode, m_mode, m_mode}
The server allows the MODE command to be sent by registered users, remote servers, and IRC operators. For unregistered users, the m_unregistered function is called.
Just to clarify this, a "registered" user is a user who has passed a certain point during the initial stage of connecting to the IRC server. It has no relation to services.
| Quote: | | All the debating of how the U:Line works isn't the issue to start with .. what was originally stated was that EFnet has U:Lines .. guess what .. they do! |
Yeah. Hybrid has Ulines. Bahamut has Ulines. But that's where the similarity ends. Ulines on Bahamut are -not- the same as Ulines on Hybrid. Just because the sky is the same colour as water, doesn't mean it's the same as water. |
|
| Back to top |
|
|
aquanight
Lurker
Joined: 14 Jun 2004
Posts: 118
Location: Boise, ID
|
| Posted: Sep 22, 2004 1:20am Post subject: |
|
|
| pomme wrote: | | Just to clarify this, a "registered" user is a user who has passed a certain point during the initial stage of connecting to the IRC server. It has no relation to services. |
(To clarify this further, it is better to say "logged in" or just plain "connected" than "registered", because of the confusion with nickname/channel registration. Mind, "register" in the sense of the actual connection was around before "register" became associated with NickServ  . Specifically, this occurs when the PASS/USER/NICK or PASS/optional PROTOCTL/SERVER have been sent and acknowledged. For user logins, a PING/PONG exchange may also be required (NOSPOOF). A user will know of a successful "login" upon receipt of the RPL_WELCOME 001 numeric (which is targeted to the nick the user has logged in as). A server will know of a successful "login" upon receipt of the other server's PASS/optional PROTOCTL/SERVER.) |
|
| Back to top |
|
|
jcle
none
Joined: 11 Mar 2005
Posts: 25
|
| Posted: Mar 11, 2005 12:25pm Post subject: RE; Newb irc admin |
|
|
Interesting debate thats for sure, however i think there is some things to take into consideration:
-How well the users can deal with individuals
and
-How quicklly a person can use.
In one month i went from a regular user to an aop to a csop sucessfully i might add. I was new with irc, knew the nickserv cmds and that was all. Now add to that im also female (which on the networks i use is very rare) that gave me a whole lot to deal with.
However i knew how to program popups and went thru the /cs help /ns help /os help etc etc and programmed everything in so that if i didn't know the answer off of the top of my head i could get it in under 10 seconds.
You can be a irc noob and an admin, only however if you have the desire to succeed. |
|
| Back to top |
|
|
PingBad
Guru
Joined: 05 Feb 2005
Posts: 2064
Location: New Zealand
|
| Posted: Apr 04, 2005 9:08am Post subject: |
|
|
Bit late to post, but oh well
U:lines are nothing more than keys to certain servers.
Dont forget, Anope Services etc declare nicks to the rest of the network (NickServ, ChanServ, etc). It is these nicks that issue the commands, not the server itself. in the SVSNICK example, the raw code being fed to the server your services are connected to (usually main hub) is this: | Code: | | :NickServ SVSNICK Nick1 Nick2 TimeStamp |
All a U:Line would do is allow a nick on that server to issue those commands. In theory (if IRCds didn't have code to block this), U:Lining an IRCd would allow its opers the same access to those commands. With that in consideration, U:Lines on one IRCd are more or less the same as U:Lines on another IRCd. |
|
| Back to top |
|
|
|
Register
Log in
