update manual
This commit is contained in:
parent
0e1e3718e3
commit
7732d68f20
3 changed files with 143 additions and 44 deletions
|
@ -26,19 +26,21 @@ SecureServ Manual
|
|||
3.9. MULTICHECK Setting
|
||||
3.10. MONBOT Setting
|
||||
3.11. MONCHANCYCLE Setting
|
||||
3.12. REPORT Setting
|
||||
3.13. AUTOSIGNOUT Setting
|
||||
3.14. JOINHELPCHAN Setting
|
||||
3.15. AKILL Setting
|
||||
3.16. AKILLTIME Setting
|
||||
3.17. DOJOIN Setting
|
||||
3.18. NFCOUNT Setting
|
||||
3.19. VERBOSE Setting
|
||||
3.20. CYCLETIME Setting
|
||||
3.21. AUTOUPDATE Setting
|
||||
3.22. SAMPLETIME Setting
|
||||
3.23. HELPCHAN Setting
|
||||
3.24. BOTECHO Setting
|
||||
3.12. MONCHANCYCLETIME Setting
|
||||
3.13. REPORT Setting
|
||||
3.14. AUTOSIGNOUT Setting
|
||||
3.15. JOINHELPCHAN Setting
|
||||
3.16. AKILL Setting
|
||||
3.17. AKILLTIME Setting
|
||||
3.18. DOJOIN Setting
|
||||
3.19. NFCOUNT Setting
|
||||
3.20. VERBOSE Setting
|
||||
3.21. CYCLETIME Setting
|
||||
3.22. AUTOUPDATE Setting
|
||||
3.23. SAMPLETIME Setting
|
||||
3.24. HELPCHAN Setting
|
||||
3.25. BOTECHO Setting
|
||||
3.26. TREATCHANMSGASPM
|
||||
|
||||
4. Operational Commands
|
||||
|
||||
|
@ -499,6 +501,7 @@ Note
|
|||
* MULTICHECK
|
||||
* MONBOT
|
||||
* MONCHANCYCLE
|
||||
* MONCHANCYCLETIME
|
||||
* REPORT
|
||||
* AUTOSIGNOUT
|
||||
* JOINHELPCHAN
|
||||
|
@ -512,6 +515,7 @@ Note
|
|||
* SAMPLETIME
|
||||
* HELPCHAN
|
||||
* BOTECHO
|
||||
* TREATCHANMSGASPM
|
||||
|
||||
To change any of these settings, you use the Set Interface in
|
||||
SecureServ. Eg:
|
||||
|
@ -656,14 +660,26 @@ Warning
|
|||
3.11. MONCHANCYCLE Setting
|
||||
|
||||
This setting specifies if SecureServ should cycle the MONCHAN's
|
||||
periodically (by default, it cycles one channel each time a new
|
||||
channel is checked with the Onjoin Bots). This can help detect OnJoin
|
||||
virus's in the channels you specify a monitor bot should be placed.
|
||||
periodically (by default, it cycles one channel interval specified by
|
||||
the MONCHANCYCLETIME setting). This can help detect OnJoin virus's in
|
||||
the channels you specify a monitor bot should be placed.
|
||||
|
||||
To Change this setting, issue the following Command:
|
||||
/msg SecureServ set MONCHANCYCLE <ON/OFF>
|
||||
|
||||
3.12. REPORT Setting
|
||||
3.12. MONCHANCYCLETIME Setting
|
||||
|
||||
This setting specified the interval that SecureServ will cycle one of
|
||||
the monchans. By Default, if MONCHANCYCLE is enabled, every 30
|
||||
minutes, one of the MONCHAN's be selected and the monbot will cycle
|
||||
the channel looking for ONJOIN virus's. For example, if you are
|
||||
monitoring 4 channels, each channel will only be cycled every 2 hours
|
||||
(30 minutes x 4 channels) so you should adjust this value accordingly.
|
||||
|
||||
To Change this setting, issue the following Command:
|
||||
/msg SecureServ set MONCHANCYCLETIME <seconds>
|
||||
|
||||
3.13. REPORT Setting
|
||||
|
||||
SecureServ has the option to report positive infections to
|
||||
secure.irc-chat.net site for both statistically and in future a
|
||||
|
@ -677,7 +693,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set REPORT <ON/OFF>
|
||||
|
||||
3.13. AUTOSIGNOUT Setting
|
||||
3.14. AUTOSIGNOUT Setting
|
||||
|
||||
SecureServ has the ability to automatically logout helpers that set
|
||||
away while being logged in. This ensures that infected users are only
|
||||
|
@ -686,7 +702,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set AUTOSIGNOUT <ON/OFF>
|
||||
|
||||
3.14. JOINHELPCHAN Setting
|
||||
3.15. JOINHELPCHAN Setting
|
||||
|
||||
SecureServ can optionally join the help channel with the first helper
|
||||
logs in, and leave the help channel when the last helper logs out. No
|
||||
|
@ -697,7 +713,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set JOINHELPCHAN <ON/OFF>
|
||||
|
||||
3.15. AKILL Setting
|
||||
3.16. AKILL Setting
|
||||
|
||||
If you do not wish SecureServ to ever AKILL a user for a positive
|
||||
match, turn this option off. It will then just issue a warning to all
|
||||
|
@ -707,7 +723,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set AKILL <ON/OFF>
|
||||
|
||||
3.16. AKILLTIME Setting
|
||||
3.17. AKILLTIME Setting
|
||||
|
||||
This setting changes the Timeout value for AKILL's that SecureServ
|
||||
sets when it detects a "infection"
|
||||
|
@ -715,7 +731,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set AKILLTIME <SECONDS>
|
||||
|
||||
3.17. DOJOIN Setting
|
||||
3.18. DOJOIN Setting
|
||||
|
||||
IF SecureServ detects a user is infected with a virus, it can
|
||||
optionally join that user to a Antivirus channel. If you do not
|
||||
|
@ -725,7 +741,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set DOJOIN <ON/OFF>
|
||||
|
||||
3.18. NFCOUNT Setting
|
||||
3.19. NFCOUNT Setting
|
||||
|
||||
SecureServ monitors the number of nick changes a user makes in a 10
|
||||
second period. If the user exceeds a threshold, it considers the user
|
||||
|
@ -737,7 +753,7 @@ Warning
|
|||
To Change this Setting, issue the following Command:
|
||||
/msg SecureServ set NFCOUNT <number>
|
||||
|
||||
3.19. VERBOSE Setting
|
||||
3.20. VERBOSE Setting
|
||||
|
||||
If you like to know what SecureServ is doing (and like to be flooded
|
||||
in the #services channel, then enable this option.
|
||||
|
@ -749,7 +765,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set VERBOSE <ON/OFF>
|
||||
|
||||
3.20. CYCLETIME Setting
|
||||
3.21. CYCLETIME Setting
|
||||
|
||||
SecureServ automatically creates new "pseudo" users that randomly join
|
||||
channels looking for OnJoin virus's or SPAM. This option changes the
|
||||
|
@ -761,7 +777,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set CYCLETIME <SECONDS>
|
||||
|
||||
3.21. AUTOUPDATE Setting
|
||||
3.22. AUTOUPDATE Setting
|
||||
|
||||
If SecureServ has been Configured with a username and password (as
|
||||
Covered in Section 2.2, you can optionally Setup SecureServ to
|
||||
|
@ -772,7 +788,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set AUTOUPDATE <ON/OFF>
|
||||
|
||||
3.22. SAMPLETIME Setting
|
||||
3.23. SAMPLETIME Setting
|
||||
|
||||
As previously mentioned, SecureServ monitors the number of joins on a
|
||||
particular channel over a period of Time. Within SecureServ, this
|
||||
|
@ -786,7 +802,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set SAMPLETIME <SAMPLETIME> <JOINS>
|
||||
|
||||
3.23. HELPCHAN Setting
|
||||
3.24. HELPCHAN Setting
|
||||
|
||||
If your network has a AntiVirus Channel setup, HELPCHAN sets that
|
||||
channel name. The default is #nohack
|
||||
|
@ -794,7 +810,7 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set HELPCHAN <NAME>
|
||||
|
||||
3.24. BOTECHO Setting
|
||||
3.25. BOTECHO Setting
|
||||
|
||||
This option enables SecureServ sending messages any of the onjoin
|
||||
bots, or monbot receives to the services channel. This can help you
|
||||
|
@ -803,6 +819,30 @@ Warning
|
|||
To Change the setting, issue the following Command:
|
||||
/msg SecureServ set BOTECHO <ON/OFF>
|
||||
|
||||
3.26. TREATCHANMSGASPM
|
||||
|
||||
This option changes the way that SecureServ treats Channel Messages
|
||||
sent to channels that either a Onjoin bot is a member off, or a
|
||||
channel that is being monitored via a MonBot. SecureServ has its own
|
||||
list of channel messages that it considers as "bad" and will act on
|
||||
accordingly, but sometimes Spambots will spam a channel instead of a
|
||||
individual user. Enabling this option will cause SecureServ to check
|
||||
channel messages against both the list of Signatures for Private
|
||||
Messages as well as the list of Signatures for Channel Messages.
|
||||
|
||||
Warning
|
||||
|
||||
Enabling this option is NOT a good idea if you have large channels
|
||||
with lots of chatter, as it is very very CPU intensive (and will get
|
||||
worse as we add more PM signatures to the official Viri.dat file). You
|
||||
should only enable this if you enjoy wasting your CPU cycles. Its
|
||||
added benifit is very small in terms of detection rates. As a extra
|
||||
pre-caution, we make it difficult for you to enable this option. This
|
||||
should give you a idea of how *bad* it is to enable.
|
||||
|
||||
To Change this setting, issue the following Command:
|
||||
/msg SecureServ set TREATCHANMSGASPM <ON/OFF>
|
||||
|
||||
4. Operational Commands
|
||||
|
||||
SecureServ has a number of commands that you can issue it in order to
|
||||
|
@ -966,12 +1006,16 @@ Warning
|
|||
This option allows you to manipulate the list of channels that will be
|
||||
monitored all the time by SecureServ for Private Message type virus's.
|
||||
The bot that joins these channels is specified in the monbot section
|
||||
of the set command.
|
||||
of the set command. You should also investigate the MONCHANCYCLE and
|
||||
MONCHANCYCLETIME options listed above on how to enable the monbot to
|
||||
cycle these monitored channels, as a OnJoin bot will not check a
|
||||
MONCHAN channel.
|
||||
/msg SecureServ monchan list
|
||||
|
||||
This option lists all the channels that will be monitored. If the
|
||||
channels do not exist when SecureServ is started, they will
|
||||
automatically be deleted from this list.
|
||||
channels do not exist when SecureServ is started, they will be joined
|
||||
when the first user joins the channel. When the last user leaves the
|
||||
channel, they will also leave the channel.
|
||||
/msg SecureServ monchan add <chan>
|
||||
|
||||
This option adds a channel to be monitored.
|
||||
|
|
File diff suppressed because one or more lines are too long
|
@ -559,6 +559,10 @@ ld -shared -o SecureServ.so SecureServ.o SecureServ_help.o http.o OnJoinBot.o F
|
|||
<para>MONCHANCYCLE</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>MONCHANCYCLETIME</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>REPORT</para>
|
||||
</listitem>
|
||||
|
@ -610,6 +614,10 @@ ld -shared -o SecureServ.so SecureServ.o SecureServ_help.o http.o OnJoinBot.o F
|
|||
<listitem>
|
||||
<para>BOTECHO</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>TREATCHANMSGASPM</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>To change any of these settings, you use the Set Interface in
|
||||
|
@ -789,16 +797,31 @@ ld -shared -o SecureServ.so SecureServ.o SecureServ_help.o http.o OnJoinBot.o F
|
|||
<title>MONCHANCYCLE Setting</title>
|
||||
|
||||
<para>This setting specifies if SecureServ should cycle the
|
||||
MONCHAN's periodically (by default, it cycles one channel each time
|
||||
a new channel is checked with the Onjoin Bots). This can help detect
|
||||
OnJoin virus's in the channels you specify a monitor bot should be
|
||||
placed. </para>
|
||||
MONCHAN's periodically (by default, it cycles one channel interval
|
||||
specified by the MONCHANCYCLETIME setting). This can help detect OnJoin
|
||||
virus's in the channels you specify a monitor bot should be placed.</para>
|
||||
|
||||
<para>To Change this setting, issue the following Command:</para>
|
||||
|
||||
<screen>/msg SecureServ set MONCHANCYCLE <ON/OFF></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>MONCHANCYCLETIME Setting</title>
|
||||
|
||||
<para>This setting specified the interval that SecureServ will cycle one
|
||||
of the monchans. By Default, if MONCHANCYCLE is enabled, every 30
|
||||
minutes, one of the MONCHAN's be selected and the monbot will cycle
|
||||
the channel looking for ONJOIN virus's. For example, if you are
|
||||
monitoring 4 channels, each channel will only be cycled every 2 hours
|
||||
(30 minutes x 4 channels) so you should adjust this value accordingly.
|
||||
</para>
|
||||
|
||||
<para>To Change this setting, issue the following Command:</para>
|
||||
|
||||
<screen>/msg SecureServ set MONCHANCYCLETIME <seconds></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>REPORT Setting</title>
|
||||
|
||||
|
@ -980,6 +1003,34 @@ ld -shared -o SecureServ.so SecureServ.o SecureServ_help.o http.o OnJoinBot.o F
|
|||
|
||||
<screen>/msg SecureServ set BOTECHO <ON/OFF> </screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>TREATCHANMSGASPM</title>
|
||||
|
||||
<para>This option changes the way that SecureServ treats Channel
|
||||
Messages sent to channels that either a Onjoin bot is a member off, or a
|
||||
channel that is being monitored via a MonBot. SecureServ has its own
|
||||
list of channel messages that it considers as "bad" and will act
|
||||
on accordingly, but sometimes Spambots will spam a channel instead of a
|
||||
individual user. Enabling this option will cause SecureServ to check
|
||||
channel messages against both the list of Signatures for Private
|
||||
Messages as well as the list of Signatures for Channel Messages. </para>
|
||||
|
||||
<warning>
|
||||
<para>Enabling this option is NOT a good idea if you have large
|
||||
channels with lots of chatter, as it is very very CPU intensive (and
|
||||
will get worse as we add more PM signatures to the official Viri.dat
|
||||
file). You should only enable this if you enjoy wasting your CPU
|
||||
cycles. Its added benifit is very small in terms of detection rates.
|
||||
As a extra pre-caution, we make it difficult for you to enable this
|
||||
option. This should give you a idea of how *bad* it is to enable.
|
||||
</para>
|
||||
</warning>
|
||||
|
||||
<para>To Change this setting, issue the following Command:</para>
|
||||
|
||||
<screen>/msg SecureServ set TREATCHANMSGASPM <ON/OFF></screen>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1>
|
||||
|
@ -1211,13 +1262,17 @@ ld -shared -o SecureServ.so SecureServ.o SecureServ_help.o http.o OnJoinBot.o F
|
|||
<para>This option allows you to manipulate the list of channels that
|
||||
will be monitored all the time by SecureServ for Private Message type
|
||||
virus's. The bot that joins these channels is specified in the
|
||||
monbot section of the set command.</para>
|
||||
monbot section of the set command. You should also investigate the
|
||||
MONCHANCYCLE and MONCHANCYCLETIME options listed above on how to enable
|
||||
the monbot to cycle these monitored channels, as a OnJoin bot will not
|
||||
check a MONCHAN channel.</para>
|
||||
|
||||
<screen>/msg SecureServ monchan list</screen>
|
||||
|
||||
<para>This option lists all the channels that will be monitored. If the
|
||||
channels do not exist when SecureServ is started, they will
|
||||
automatically be deleted from this list.</para>
|
||||
channels do not exist when SecureServ is started, they will be joined
|
||||
when the first user joins the channel. When the last user leaves the
|
||||
channel, they will also leave the channel. </para>
|
||||
|
||||
<screen>/msg SecureServ monchan add <chan></screen>
|
||||
|
||||
|
|
Reference in a new issue