Does anyone have any ideas how to get around the identd daemon so that the ident of an eggdrop can be changed to something other than the shell account login?
I know it was possible back when I use to run a BNC through a shell, but the shell provider has to have a certain program installed (to which the name of the program escapes me at the moment). Maybe someeone else can provide the name of it.
I thought you had to be a superuser to change settings for privaledged ports? Is it possible to tell the irc to server to send an ident request on another port maybe? And run your own identd on that port while connecting.
This is a much talked about subject, yet there is no real clarity on it.
the identd deamon is used to check the identity of the user, making a connaction to a server, on a specified port. In reality (not allways the case), the identd deamon should reply with the username of the person, currently using the ports involved.
As linux/unix is a true multi-user system, with a range of port, designed for use by only the superuser (AKA, root, or the good old internals of the kernal itself).
This means, that (in theory, remember) a program listening on one of these ports, should be gurenteed to give truthful information, and not that as provided by a user.
With standard identd implimentations, it is not possible to change the ident reply to a IRC server.
There are however, programs that will allow you to change your ident reply, that must be installed by the superuser (remember, these programs are running on reserved ports).
Once installed, the process to change the ident is not even complete, and won't be completed (not with the current status of eggdrop, anyway).
Whilst the changing identd software is installed, you have to tell the software, that you want the ident changing. To do this, the program requiring this change, must tell identd so.
Eggdrop does not do this.
Another solution, is to kindly (though, I have never seen this done) ask the shell admin to provide you with muliple login names, each one providing you with one process (AKA, one bot per login) each.
The second one, means the admin looses out of good login names, for other customers, while meaning a way of tracking down customers breaking TOS.
The first means, the admin can provided stupid login names like "user667", whist giving the ability to use whatever ident you want (as stated, providing the software supports these identd deamons (eggdrop doesn't)). It also makes it harder for the admin to track breaks in TOS, as 2 user (or many more) could use the same ident, and then break the TOS. It also leaves the greater risk of DOS and buffer attacks, as these are not as well supported software, whilst stock identd deamons are.