Project

General

Profile

Oident spoofing » History » Version 5

public, 01/10/2018 03:48 AM
added "at boot, identd should be started before quassel" remark (Sveta, Llamatron2112)

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 3 Anonymous
        allow spoof
9 1 Anonymous
        allow spoof_all
10 1 Anonymous
    }
11 1 Anonymous
}
12 1 Anonymous
</pre>
13 1 Anonymous
14 1 Anonymous
2) Start quasselcore with --oidentd switch. 
15 1 Anonymous
16 1 Anonymous
If you're using Debian and running it as a service, add this line to @/etc/default/quassel@:
17 1 Anonymous
18 1 Anonymous
<pre>
19 1 Anonymous
DAEMON_OPTS="--oidentd"
20 1 Anonymous
</pre>
21 1 Anonymous
22 5 public
Note that at boot, identd should be started before quassel. Otherwise Quassel core connects to irc at the time when identd is not yet running.
23 1 Anonymous
24 1 Anonymous
If this worked properly,
25 1 Anonymous
26 1 Anonymous
* Quassel core will show up in processes list with the --oidentd switch; and 
27 4 rixon
* At the Quassel core user's home directory (echo ~quasselcore), you will see an .oidentd.conf file. Ensure this file is writable by quasselcore, and the directory is world readable (so that oidentd can read the file.)
28 1 Anonymous
29 1 Anonymous
Now when connecting to IRC:
30 2 gry
* At some networks that check oidentd response, a (up to 10 seconds) wait for an ident response will disappear. You will see "*** Got ident response" when connecting.
31 1 Anonymous
* The username will not contain a tilde (ratbox, charybdis, derived ircds, and others).
32 1 Anonymous
* The username will match the name of the user in the core and user settings regarding username will not override it.