This file is indexed.

/etc/pyirct.conf.xml is in jabber-irc 0.4cvs20080505-1.1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<?xml version="1.0" ?>
<pyirct>
    <!-- This file contains options to be configured by the server administrator. -->
    <!-- Please read through all the options in this file -->
    
    <!-- The JabberID of the transport -->
    <jid>irc.localhost</jid>

    <!-- The component JID of the transport. Unless you're doing clustering, leave this alone -->
    <!-- <compjid>irc1</compjid> -->

    <!-- The public IP or DNS name of the machine the transport is running on -->
    <!-- This is used to select the outgoing IP address used to connect to IRC networks -->
    <!--  otherwise known as the vanity address, it's safe to leave it commented -->
    <!--<host>vanity.host.example.net</host>-->

    <!-- The name of the transport in the service discovery list. -->
    <!-- <discoName>IRC Transport</discoName> -->

    <!-- The location of the spool file.. if relative, relative to the PyIRCt dir. -->
    <!-- Include the jid of the transport, if running multiple copies of the same transport -->
    <spoolFile>ircuser.dbm</spoolFile>

    <!-- The location of the PID file, relative to the PyIRCt directory -->
    <!-- Comment out if you do not want a PID file -->
    <pid>PyIRCt.pid</pid>

    <!-- The IP address or DNS name of the main Jabber server -->
    <mainServer>127.0.0.1</mainServer>

    <!-- The JID of the main Jabber server -->
    <mainServerJID>jabber.localhost</mainServerJID>

    <!-- The TCP port to connect to the Jabber server on (this is the default for Jabberd2) -->
    <port>5347</port>

    <!-- The authentication token to use when connecting to the Jabber server -->
    <secret>secret</secret>

    <!-- SASL username used to bind to Jabber server. -->
    <!-- secret, above, is used for sasl password -->
    <!--<saslUsername>username-for-jabberd2-connection</saslUsername>-->

    <!-- Allow users to register with this transport -->
    <allowRegister/>

    <!-- Require users to be registered before allowing them to join a room -->
    <!-- <requireRegister/> -->

    <!-- Send activity messages to users (for clients that don't support MUC)  -->
    <activityMessages/>

    <!-- Use external component binding. -->
    <!-- This dodges the need to manually configure all jids that talk to this transport. -->
    <!-- Jabberd2 requires saslUsername and useRouteWrap for this to work. -->
    <!-- Wildfire as of 2.6.0 requires just this. -->
    <!--<useComponentBinding/>-->

    <!-- Wrap stanzas in <route> stanza. -->
    <!-- Jabberd2 requires this for useComponentBinding. -->
    <!--<useRouteWrap/>-->

    <!-- You can choose which users you wish to have as administrators. These users can perform some tasks with Ad-Hoc commands that others cannot -->
    <!--<admins>
        <jid>romeo@montague.net</jid>
        <jid>juliet@capulet.com</jid>
    </admins>-->

    <!-- The file to log to. Leave this disabled for stdout only -->
    <debugFile>ircerror.log</debugFile>

    <!-- Show the raw data being sent and received from the xmpp and irc servers -->
    <!--<dumpProtocol/>-->

    <!-- The default charset to use for the transport, if not supplied by the user when registering -->
    <!-- <charset>utf-8</charset> -->

</pyirct>