Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Point]

I think that NickServ INFO command should store and show the real IP/HOSTname to the services staff who can issue /ns info <nickname> ALL

Is possible for something like this to be added to anope? 

[katsklaw]

Anope already does, except it shows the host as received by the ircd.

See /ns help set hide

[Point]

Anope already does, except it shows the host as received by the ircd.

See /ns help set hide

I have to describe it better.

This is a WHOIS:

Testing is test@testnet-572A1B61.urp.isp.tld * Test
Testing is connecting from *@adsl10.55.urp.isp.tld 123.222.111.100

For a regular user NS INFO (without hide usermask on) it should return:

 -NickServ- Last seen address: test@testnet-572A1B61.urp.isp.tld

But for a services staff member (NS info ALL) it should return:

-NickServ- Last seen address: test@adsl10.55.urp.isp.tld

[katsklaw]

I'll explain it better, NickServ stored the address it's given by the ircd. That means that if your ircd sends a crypted host to Anope, that is what Anope displays. In the case of Unreal it sends an intro string that contains the real IP for users, then changes it when the use gets mode +x and wipes out the real IP from before.

Lets notice that we recieve the real IP, in this case 192.168.2.9, then when +x is set the ircd ovewrites it and broadcasts a crypted host.

Code: [Select]

[Sep 20 20:01:44.445483 2008] debug: Received: NICK katsklaw 1 1221955303 darkness 192.168.2.9 irc.foonet.com 0 +iwx C48A576F.435C9371.A910A945.IP wKgCCQ== :Haunting your Dreams
[Sep 20 20:01:44.445650 2008] debug: new user: katsklaw
[Sep 20 20:01:44.445710 2008] LOGUSERS: katsklaw (darkness@192.168.2.9 => C48A576F.435C9371.A910A945.IP) (Haunting your Dreams) [192.168.2.9] connected to the network (irc.foonet.com).

Now it changes the host which overwrites what it was:

Code: [Select]

[Sep 20 20:01:44.446483 2008] debug: Changing mode for katsklaw to +iwx
[Sep 20 20:01:44.446507 2008] debug: katsklaw changes its host to C48A576F.435C9371.A910A945.IP

So as I said before, Anope stores the address given by the IRCd. Anope can not control the address it receives. You see a different address in a /whois because the ircd stores both addresses as it should.

Anope stores the last mask in na->last_usermask which is the only mask a module would be able to use. I doubt this can be done without modifying the core, which in that case won't happen for quite some time.

[Trystan Scott Lee]

Problem is that the NickServ Alias struct which is what NS INFO prints out does not hold the host that the user is on, just the last host mask. This is only stored in the User Struct, which is for online users only.

1. NS INFO could be modified if user is online to show the true host, but that is what WHOIS is for
2. Alias struct updated to have that information in it, but this is much more work to find all the places where this is updated

The last has a down side and that is that the info can't be saved any where, since there are no db changes in the 1.7.x branch, thus adding to the complexity of the issue.

[katsklaw]

and to make it worse, EVENT_NEWNICK only has 1 parameter, the nick. So we can't capture the host there and store it in seperate db either. I did forget about the user struct, but as Trystan said, it's pointless since you can get the info via /whois anyway.

[Point]

Yes you can do that by whois but sometimes i need to know what IP some user had.

Besides that, if i ban a real IP on a channel from server 1 a user with this ip from server 2 is banned, so the network always knows user's real IP, so why not anope?

[Jobe]

Try /whowas then?

A standard feature of most IRCd's

Example:
/whowas Jobe 1

Displays the last entry for Jobe.

[Point]

Try /whowas then?

A standard feature of most IRCd's

Example:
/whowas Jobe 1

Displays the last entry for Jobe.

Not always. The entries of whowas are not permanent 

[Jobe]

That all depends on how YOU set your IRCd up as MOST allow you to configure the WHOWAS setup quite a bit.

[Jan Milants]

a module can easily append output to the INFO command and store for all registered users their IP - if the ircd supplies it  - in a seperate DB..

[Point]

That all depends on how YOU set your IRCd up as MOST allow you to configure the WHOWAS setup quite a bit.

On a large network if whowas configured to keep entries for long time it could cause some problems. (i suppose?)

a module can easily append output to the INFO command and store for all registered users their IP - if the ircd supplies it  - in a seperate DB..

Easily for you Viper 

[Jobe]

On a large network if whowas configured to keep entries for long time it could cause some problems. (i suppose?)

Yes, but you should also have log files available to you to find the information too. If Anope stores it that's like potentially 269 bytes per user having to be stored additionally to everything else, have 1000 users and that becomes 269000 bytes, OK so that isnt much, 10000 users, 2690000 bytes (around 2MB extra), it all starts adding up. When the alternative is to spread this additional info amongst the IRCd's in either /whowas or log files.

[Point]

Yes, but you should also have log files available to you to find the information too. If Anope stores it that's like potentially 269 bytes per user having to be stored additionally to everything else, have 1000 users and that becomes 269000 bytes, OK so that isnt much, 10000 users, 2690000 bytes (around 2MB extra), it all starts adding up. When the alternative is to spread this additional info amongst the IRCd's in either /whowas or log files.

You already said it. Even with 10000 users (a big number) the db will be only 2mb.
In other words nothing.

I'm just trying to say that it could be useful to have the user's real address permanently stored on an extra line on the info output.

[Jobe]

2MB is a lot when it comes to memory, bearing in mind Anope keeps the ENTIRE DB in the memory while using it, and dumps it periodically.

[Point]

2MB is a lot when it comes to memory, bearing in mind Anope keeps the ENTIRE DB in the memory while using it, and dumps it periodically.

How many networks have 10000 users? And ofc i dont think that a network with many users will have its services to a low-end server.

[katsklaw]

Yes you can do that by whois but sometimes i need to know what IP some user had.

Besides that, if i ban a real IP on a channel from server 1 a user with this ip from server 2 is banned, so the network always knows user's real IP, so why not anope?

That's been explained already 3 times. Sorry you didn't understand.

Cliff notes: Anope currently CANNOT store the real IP as it's currently written. It will take some code re-writing to do this. Which will not happen before 1.9 devel

No one said your idea was a bad idea .. what we said is Anope cannot do it right now ... period. Do you understand now?

Additionally, there are 73 networks with more 1000 users at the time of this post. Some of them use Anope.

[Point]

That's been explained already 3 times. Sorry you didn't understand.

Cliff notes: Anope currently CANNOT store the real IP as it's currently written. It will take some code re-writing to do this. Which will not happen before 1.9 devel

No one said your idea was a bad idea .. what we said is Anope cannot do it right now ... period. Do you understand now?

Additionally, there are 73 networks with more 1000 users at the time of this post. Some of them use Anope.

Okay

Then i'll have to wait for the 1.9 branch