Project

General

Profile

Oident spoofing » History » Version 1

Anonymous, 05/05/2013 03:28 PM

1 1 Anonymous
h1. Using Quassel with oidentd spoofing
2 1 Anonymous
3 1 Anonymous
1) In oidentd's configuration (@/etc/oidentd.conf@ on Linux), add this block (note that the username may differ) and restart oidentd service.
4 1 Anonymous
5 1 Anonymous
<pre>
6 1 Anonymous
user quasselcore {
7 1 Anonymous
    default {
8 1 Anonymous
        allow spoof_all
9 1 Anonymous
    }
10 1 Anonymous
}
11 1 Anonymous
</pre>
12 1 Anonymous
13 1 Anonymous
2) Start quasselcore with --oidentd switch. 
14 1 Anonymous
15 1 Anonymous
If you're using Debian and running it as a service, add this line to @/etc/default/quassel@:
16 1 Anonymous
17 1 Anonymous
<pre>
18 1 Anonymous
DAEMON_OPTS="--oidentd"
19 1 Anonymous
</pre>
20 1 Anonymous
21 1 Anonymous
22 1 Anonymous
If this worked properly,
23 1 Anonymous
24 1 Anonymous
* Quassel core will show up in processes list with the --oidentd switch; and 
25 1 Anonymous
* At the Quassel core user's home directory, you will see an .oidentd.conf file (if not, figure out what directory it is (on Linux, `echo ~quasselcore`) and ensure it is writable); and
26 1 Anonymous
27 1 Anonymous
Now when connecting to IRC:
28 1 Anonymous
* You will see "*** Got ident response" when connecting.
29 1 Anonymous
* At some networks that check oidentd response, a (up to 10 seconds) wait for an ident response will disappear.
30 1 Anonymous
* The username will not contain a tilde (ratbox, charybdis, derived ircds, and others).
31 1 Anonymous
* The username will match the name of the user in the core and user settings regarding username will not override it.