As long as you have successfully setup NeoStats, and installed it correctly, Compiling SecureServ is very simple and straight forward. First you must extract the files from the download package. This is as simple as:

bash$ tar -xzf SecureServ-<ver>.tar.gz

This should then create a directory called SecureServ-<version> where <version> is the Version of SecureServ. Then Proceed to Change into the SecureServ directory, and run Configure as follows:

bash$./configure [--enable-debug | --with-neostats=<dir> --enable-treatchanmsgaspm]

--enable-debug is only useful for diagnostics purposes when used in conjunction with debugging tools. There should be no need to use this option on a day to day basis

--with-neostats=<dir> should be used if your neostats directory is not in a standard location (~/NeoStats/). Replace <dir> with the full path to your NeoStats installation directory (NOT SOURCE DIRECTORY)

--enable-treatchanmsgaspm makes SecureServ treat all messages sent to a monitored channel as messages sent to a individual user. Enabling this option is not recommended as it greatly increases the CPU utilization if you have large, busy channels

Configuring SecureServ will look something like the following screen:

Fishs-Mac:~/Documents/Dev/SecureServ justin$ ./configure       
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no

<snip>

checking To Enable AutoTools Debug Mode?... no
checking silent building of source files... Enabled
configure: creating ./config.status
config.status: creating Makefile
config.status: creating modconfig.h
config.status: modconfig.h is unchanged
config.status: executing depfiles commands
Configuration complete.
Press Enter key to read the release notes

The Configure process will then prompt you to read the release notes. You are encouraged to read this document throughly as it might contain important information about the current version of SecureServ that isn't covered in the manual.

If the configuration did not produce a error, you may then move onto Compiling SecureServ. Compiling is simply just issuing the "make" command (or "gmake" if you are running BSD):

Fishs-Mac:~/Documents/Dev/SecureServ justin$ make
make -s all-am
Compiling Helpers.c:                                                  [OK]     
Compiling SecureServ.c:                                               [OK]     
Compiling scan.c:                                                     [OK]     
Compiling OnJoinBot.c:                                                [OK]     
Compiling SecureServ_help.c:                                          [OK]     
Compiling update.c:                                                   [OK] 

Again, check for Error messages. As long as there are not error messages, "make install" will install SecureServ, this README file, and any auxiliary files needed into your NeoStats directory:

Fishs-Mac:~/Documents/Dev/SecureServ justin$ make install
Installing secureserv.so:                                             [OK]     
Installing viri.dat:                                                  [OK]     
Installing README.SecureServ:                                         [OK]     
Installing README.SecureServ.html:                                    [OK] 

If you receive *ANY* errors at all during the this process, please post them on our Support boards, at http//www.neostats.net/boards/

Once Installation is complete, you can either configure NeoStats to load SecureServ when it starts, or load SecureServ via IRC.

To Configure NeoStats to automatically load SecureServ when it boots, modify the neostats.conf file and add SecureServ to the list of modules to load:

MODULENAME = {
       "statserv",
       "hostserv",
       "secureserv",
} 

You also should now configure a NeoNet account if you wish to take advantage of updated virus definition files. To obtain a account for NeoNet, please go to http://accounts.neostats.net and sign up for a new account. Once you have signed up, you will recieve a email with instructions for configuring your NeoStats to use NeoNet. Please modify your neostats.conf file as per the instructions contained in the email.

To load SecureServ via IRC, you must make sure you have the appropriate permissions and issue the following command:

/msg neostats load SecureServ

Thats it. SecureServ is now loaded and ready for use (in fact, it will already be running now, but read on for further information.)

Exclusion lists allow you to specify certain Hostmasks, Servers, or Channels that should be excluded from monitoring by SecureServ. This exclusion list would allow a administrator to say, allow users on that are matched against Trojans, when the administrator has verified that the Trojan does not in fact exist on the users host.

With NeoStats 3.0, you should also be aware that there are two types of Exclusion Lists. There are "Global" exclusion lists that all modules may optionally use, and there is module specific exclusion lists. SecureServ defaults to not using the Global Exclusion lists. You can enable it by the following command:

/msg SecureServ set exclusions on

Adding a Entry

To add a entry to the Exclusion list, use the following format:

/msg SecureServ exclude add <host/Server/Channel/UserHost> <pattern> <reason>

Where:

<Host/Server/Channel/UserHost> = The type of exclusion you are adding. The different types are:

<pattern> = The pattern you wish to match on. May include wildcard charactors such as * and ?

<reason> = a short description of the exclusion, for operator reference only.

The output is as follows:

[13:20] -SecureServ- Added *.blah.com (userhost) to exclusion list
[13:20] SecureServ Fish added *.blah.com (userhost) to the exclusion list

Listing an Entry

To list the Exclusions simple type:

/msg SecureServ exclude list

And all the current exclusions are listed. Additionally, a Position number is provided for use with the delete command. The output is as follows:

[13:21]  -SecureServ- Exclusion list:
[13:21]  -SecureServ- #bothouse (Channel) Added by Fish on Sat Aug 13 2005 01:20 AM SGT for Requested
[13:21]  -SecureServ- #ircop (Channel) Added by Fish on Sat Aug 13 2005 07:40 PM SGT for IRCop channel
[13:21]  -SecureServ- *irc-chat.net (Host) Added by Fish on Tue Aug 09 2005 10:13 PM SGT for Services Exclusion
[13:21]  -SecureServ- chieftess!*@* (Userhost) Added by Fish on Tue Aug 09 2005 10:14 PM SGT for buggy client
[13:21]  -SecureServ- *.blah.com (Userhost) Added by Fish on Sun Jan 15 2006 01:20 PM SGT for Cause Blah.com is cool
[13:21]  -SecureServ- End of list.

Deleting an Entry

To delete a entry, you should first lookup the Position of the entry that you wish to delete. The format of the command is as follows:

/msg SecureServ exclude del <pattern>

Where:

<pattern> is the pattern of the entry you wish to delete in the list

The output of the command is as follows:

[13:22]  SecureServ Fish used EXCLUDE
[13:22]  -SecureServ- *.blah.com delete from exclusion list

Helper lists let you grant non-privileged users the ability to maintain your Virus help channel and help users that are infected with virus's that could be removed with simple instructions (such as Spam Virus's that infect Mirc). These users are granted the ability to "release" a infected user from SecureServ or kill un-cooperative, or unresponsive users that SecureServ has identified as being infected. Users that have been joined to the help channel are "held" by SecureServ and are usually prevented from joining other channels (if your IRCd supports this option). This can be helpful so you can clean up users that are infected with simple script based virus's and you require their attention to help you clean their computer. More information about the commands available to use on infected users is available via the assist command detailed below.

Adding a Entry

To add a entry to the Helper list, use the following format:

/msg SecureServ helpers add <login> <pass> 

Where:

<login> = The login name to use to gain access. Does not have to be a nickname.

<pass> = The password to use to login

The output is as follows:

>secureserv< helpers add myhelper mypass
-SecureServ- Successfully added Helper myhelper with Password mypass to Helpers List

Listing an Entry

To list the helpers simple type:

/msg SecureServ helpers list

And all the helpers are listed. Additionally, if a nickname is provided after the login name, it means that this nick is logged into this particular helper account.

The output is as follows:

>secureserv< helpers list
-SecureServ- Helpers List (2):
-SecureServ- fish (Fish)
-SecureServ- myhelper (Not Logged In)
-SecureServ- End of List.

Deleting an Entry

To delete a entry, you must provide the login name you wish to delete. The format of the command is as follows:

/msg SecureServ helpers del <login>

Where:

<login> is the login account you wish to delete.

The output of the command is as follows:

>secureserv< helpers del myhelper
-SecureServ- Deleted myhelper from Helpers List

In order to update SecureServ's Detection, you need to register a account at http://accounts.neostats.net/ and apply for access to the Secure IRC-Chat website. Once your application for access has been recieved, you will be able to download updated dat files either automatically (as they are released) or manually. You also get access to some advanced reporting capabilities such as weekly reports on virus infections on your Network, as well as real time statistics.

When applying for access to the Secure IRC-Chat website, it might take a while for the application to be approved, as one of the Admins has to review the application and ensure its valid. Once your access has been granted, you will recieve a email informing you that your access has been granted.

Once you have received confirmation that you can now access Secure IRC-Chat via email, you can proceed to configure SecureServ to update Dat files automatically for you. SecureServ can be configured to check for updates on a Daily Basis. You can, disable this automatic update if you wish, but this is covered in the "Settings" Section.

For more information on the NeoNet configuration, please refer to the NeoStats Manual.

SecureServ sends different messages to users depending on whats happening. Examples of the messages its send is messages when they are AKILedL or warn a user about a possible "Trojan/Infection" etc. These messages can be customized to suit your network, or language of choice easily. The different messages that you can set are:

Setting these three types of messages is simple. Just issue the following commands:

/msg SecureServ set akillmesg <message>

/msg SecureServ set nohelpmsg <message>

This setting allows you to change the Nickname that SecureServ uses when it connects to your network. If you change this setting make sure you update your NeoNet account, otherwise you might loose access to the Secure IRC-Chat site if we perform a check on your network and can't find "SecureServ" running.

/msg SecureServ set NICK <nickname>

This setting allows you to set a "Backup" nickname used for SecureServ. If the primary Nickname in the NICK Setting is not available, SecureServ will use this nickname, and if that is not available, it will use a automatically generated nickname

/msg SecureServ set ALTNICK <nickname>

This option allows you to customize the "user" or ident portion of the SecureServ Bot.

/msg SecureServ set USER <user>

This option allows you to customize the Hostname that SecureServ uses when it signs onto your Network. It defaults to the Standard Hostname specified in your NeoStats configuration.

/msg SecureServ set HOST <host>

This option allows you to customize the realname (or Gecos) that SecureServ uses when it signs onto your Network.

/msg SecureServ set REALNAME <realname>

This option enables SecureServ to use the Global Exclusions list that is control by the main NeoStats bot. This allows you to maintain a "global" exclusion list that is applicable to all modules in NeoStats, and then only apply individual exclusions to SecureServ.

If you wish to enable or disable the Global Exclusions lists, issue the following command

/msg SecureServ set EXCLUSIONS <ON/OFF>

When users sign onto your IRC network, SecureServ or NeoStats will issue a "CTCP VERSION" command to the clients, as many Trojans/WarScripts/Virus's have unique replies to CTCP Version requests.

When SecureServ receives the reply, it compares it to the Definitions, and if there is a Match, will take action based on the Definition File (Either AKILL the user, Join them to a AV help channel, Warn the Operators, or just issue a warning message to the users)

If you wish to turn off the CTCP VERSION checks, issue the following command

/msg SecureServ set VERSION <ON/OFF>

SecureServ can Detect the Fizzer Worm on your IRC network. If you are not affected by Fizzer, its advisable to turn this option off, as it affects performance.

To Change the setting, issue the following Command:

/msg SecureServ set CHECKFIZZER <ON/OFF> 

This setting decides if SecureServ should perform OnJoin Virus Checking. When enabled, every CYCLETIME Seconds, SecureServ will create a psydo user and join a random channel. When this setting is off, SecureServ will not check random channels for OnJoin Virus's.

To Change this Setting, issue the following Command:

/msg SecureServ set DOONJOIN <ON/OFF>

This option defines what usermodes the OnJoin Bots will have when they "Sign-On" to your network. By default no modes are assigned, but you may wish to assign some Oper or Helper or Services flags so that users at least can easily identify that the OnJoinBot is part of your services if they Whois the OnJoin Bot

If you wish to change the modes, issue the following command

/msg SecureServ set ONJOINBOTMODES <modes>

SecureServ automatically creates new "pseudo" users that randomly join channels looking for OnJoin virus's or SPAM. This option changes the interval that SecureServ will Cycle the random users and channels. On a Large network, you should aim for a smaller value, so it covers more of your channels quicker, but on a smaller network, this may become annoying for your users, so a higher value is recommended.

To Change the setting, issue the following Command:

/msg SecureServ set CYCLETIME <SECONDS> 

This setting controls if SecureServ's will check Private Channels. Private Channels are defined by the Channel Modes +I, +k +s +p or +O. Enabling this option forces SecureServ to check these channels. Disabling this feature means SecureServ will never check these channels unless forced via a /msg SecureServ check <chan>

To Change this Setting, issue the following Command:

/msg SecureServ set DOPRIVCHAN <ON/OFF>

By Default, when SecureServ identifies a Positive Match for a Trojan/VIrus etc, it takes action straight away, and discontinues checking for any other matches. This option tells SecureServ, that even if it does find a Match, to continue checking, so that the user is warned of all matches, and not just the first one found.

To Change the setting, issue the following Command:

/msg SecureServ set MULTICHECK <ON/OFF> 

SecureServ has the option to assign one of the random bots to stay in a channel all the time, instead of cycling like the ONJOIN bots do. This option sets which bot will be used to monitor the channels specified in the MONCHAN command. A listing of available bots is obtained via the Bots Command. .

To Change the setting, issue the following Command:

/msg SecureServ set MONBOT <bot> 

This setting specifies if SecureServ should cycle the 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.

To Change this setting, issue the following Command:

/msg SecureServ set MONCHANCYCLE <ON/OFF>

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>

This option enables SecureServ sending messages any of the onjoin bots, or monbot receives to the services channel. This can help you monitor for potentially new onjoin virus's, or monitor for spam users.

To Change the setting, issue the following Command:

/msg SecureServ set BOTECHO <ON/OFF> 

This option specified the "Quit" message that a Onjoin bot will use when its finished scanning. If not set, it uses a default message

To Change the setting, issue the following Command:

/msg SecureServ set BOTQUITMSG <msg> 

This option enables the SecureServ Helper SubSystem. It allows you to grant users access to SecureServ to manage any user that is joined to your help channel. See the Helpers section in the introduction for more information on helpers.

To Change the setting, issue the following Command:

/msg SecureServ set HELPERS <ON/OFF> 

SecureServ has the ability to automatically logout helpers that set away while being logged in. This ensures that infected users are only joined to the help channel if a helper is available to help them.

To Change the setting, issue the following Command:

/msg SecureServ set AUTOSIGNOUT <ON/OFF> 

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 additional functionality is provided when SecureServ joins the channel, its only for the "look" and "feel" of having SecureServ in your antivirus channel.

To Change the setting, issue the following Command:

/msg SecureServ set JOINHELPCHAN <ON/OFF> 

If you dont want SecureServ to automatically join some infected users to your help channel, then turn of SVSJOIN and instead if a user is matched against a signature that specifies it should SVSJOIN the user, it will akill the user instead.

To Change the setting, issue the following Command:

/msg SecureServ set SVSJOIN <ON/OFF> 

If your network has a AntiVirus Channel setup, HELPCHAN sets that channel name. The default is #nohack

To Change the setting, issue the following Command:

/msg SecureServ set HELPCHAN <NAME> 

If there are no helpers logged into SecureServ and a user is infected with a Signature that specifies SVSJOIN, this is the message that is sent to the user informing them there are no users available, and it then proceeds to AKILL the infected user.

To Change the setting, issue the following Command:

/msg SecureServ set NOHELPMSG <msg> 

SecureServ has the option to report positive infections to secure.irc-chat.net site for both statistically and in future a blacklist type setup. Enabling this option means that statistics about infections can be reported to you on the secure.irc-chat.net site as well as providing Summarized data to the public (No Private information, such as infected hostnames, or your networks infection rate is reported to the public though - See the secure.irc-chat.net site for more information.

To Change the setting, issue the following Command:

/msg SecureServ set REPORT <ON/OFF> 

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 operators about the Client, and Operators are free to do as they see fit.

To Change the setting, issue the following Command:

/msg SecureServ set AKILL <ON/OFF> 

This setting changes the Timeout value for AKILL's that SecureServ sets when it detects a "infection"

To Change the setting, issue the following Command:

/msg SecureServ set AKILLTIME <SECONDS> 

This option allows you to customize the message sent to users when they are AKILLED. You can point them to your website or provide additional information to help them if required.

To Change the setting, issue the following Command:

/msg SecureServ set AKILLMSG <MSG> 

If SecureServ has been Configured with a username and password (as Covered in Section 2.2, you can optionally Setup SecureServ to automatically check and download new dat files if available on a Daily basis. If you prefer to manually update the DAT files via /msg secureserv update, then disable this option

To Change the setting, issue the following Command:

/msg SecureServ set AUTOUPDATE <ON/OFF> 

This option specifies how often to Check for new Dat files.

To Change the setting, issue the following Command:

/msg SecureServ set AUTOUPDATETIME <SECONDS> 

If you like to know what SecureServ is doing (and like to be flooded in the #services channel, then enable this option.

To Change the setting, issue the following Command:

/msg SecureServ set VERBOSE <ON/OFF> 

The help command allows the users to access the online help for the different commands available. You can get general help about the available commands, or can access more specific information about a command.

To see the help pages, use the following format:

/msg SecureServ help [command]

command is optional and only required if you want more specific information about a particular command

This command displays the Version of SecureServ, and the dat files.

The format of the command is as follows:

/msg SecureServ version

The about command shows a brief description of the Bot and its purpose.

The format of the command is as follows:

/msg SecureServ about

The credits command shows details about the authors or contributors of to the Module

The format of the command is as follows:

/msg SecureServ credits

The levels command allows you to adjust the security of each command available in this module. You can make certian commands only available to higher "level" users in NeoStats.

For more information about NeoStats Levels and Security, please consult the NeoStats Manual

To list the currently configured levels, issue the following command:

/msg SecureServ levels list

To change the minimum level required to execute a command, issue the following command:

/msg SecureServ levels <command> <level>

Where:

command = is the actual command name you wish to modify

level = a number between 0 and 200 that specifies the new level.

The set command allows you to modify settings applicable to this module. For a complete description of the available set options, please consult the Detailed Configuration Section of this manual.

This command allows a "helper" or trusted user that mans your Antivirus or help channel to login to SecureServ to gain additional functionality with regards to handling infected users. The helpers must have a valid login account and password as set in the helpers command.

The format of the command is as follows:

/msg SecureServ login <login> <pass>

This command allows a logged in helper to logout of SecureServ if he is going to be away or not paying attention to the help channel for a period of time. You should encourage your users to logout if they can not provide timely response to infected users that may be forcejoined to the channel.

The format of the command is as follows:

/msg SecureServ logout

This option is only available to "helpers" that have logged into secureserv and is used to control SecureServ's limits over users that have been identified as infected with simple virus's and joined to a help channel. They allow the "helpers" to either release a user from SecureServ's restrictions, or kill un-cooperative, or un-responsive users from the network. The helpers may only perform these actions on users that SecureServ has identified as infected with a simple virus, and automatically joined to the help channel. Helpers may not "kill" users that SecureServ has NOT identified as infected.

The format of the assist command is as follows:

/msg SecureServ assist release/kill <target>

The release option allows the user to join all previous channels and continue as normal. After release is used on a user, a helper can no longer kill the target.

The kill option removes the user from the network via a akill command and broadcasts a message to all opers indicating the helper that used the kill command, and the initial virus the users was detected as having.

This option is only available to "helpers" that have logged into secureserv and is used to change thier password that they use to login to SecureServ.

The format of the chpass command is as follows:

/msg SecureServ chpass <newpass>

Where:

newpass = The new password to set your helper account to

If you suspect that a user in a Channel is infected with a OnJoin virus, you can force SecureServ to check the channel on your behalf. If SecureServ finds any infection in the channel, it will take the normal action associated with that virus.

The format of the command is as follows:

/msg SecureServ checkchan <chan>

The List command shows a brief list of all the Definitions that SecureServ currently has loaded. These are direct from the Dat file that is downloaded from the http://secure.irc-chat.net website.

The format of the command is as follows:

/msg SecureServ list

More detail about each "Virus" can be found at the http://secure.irc-chat.net/ site by searching for the Virus Name.

This command gives the Administrator statistics on the how SecureServ is performing, how many checks it has conducted, and currently logged in "helper" users.

The format of the command is as follows:

/msg SecureServ status

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. 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 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.

/msg SecureServ monchan del <chan>

This option lists will delete a channel from the monitored list.

This option allows you to manipulate the random bot list that is used to join random channels (or channels monitored with the monchan command, as detailed below). The available options are:

/msg SecureServ bots list

This option lists all available bots.

/msg SecureServ bots add <nick> <ident> <host> <realname>

This option adds a bot with the nickname, ident, host and realname as specified in the command to the list of bots that will be used to randomly join a channel.

/msg SecureServ bots del <num>

This option lists will delete a bot from the available bots if its not currently in use.

This command forces SecureServ to part the existing channel it is checking and join the next random Channel.

The format of the command is as follows:

/msg SecureServ cycle

The next channel is chosen at random, but is guaranteed not to be the previous channel it checked.

This option reloads the viri.dat and customviri.dat files. Its no the same as a update command, as it does not attempt to download new dat files from http://secure.irc-chat.net site. Its useful if you make a change to your customviri.dat file.

The format of the reload command is as follows:

/msg SecureServ reload

Helper lists let you grant non-privileged users the ability to maintain your Virus help channel and help users that are infected with virus's that could be removed with simple instructions (such as Spam Virus's that infect Mirc). These users are granted the ability to "release" a infected user from SecureServ or kill un-cooperative, or unresponsive users that SecureServ has identified as being infected. Users that have been joined to the help channel are "held" by SecureServ and are usually prevented from joining other channels (if your IRCd supports this option). This can be helpful so you can clean up users that are infected with simple script based virus's and you require their attention to help you clean their computer. More information about the commands available to use on infected users is available via the assist command detailed below.

Adding a Entry

To add a entry to the Helper list, use the following format:

/msg SecureServ helpers add <login> <pass> 

Where:

<login> = The login name to use to gain access. Does not have to be a nickname.

<pass> = The password to use to login

The output is as follows:

>secureserv< helpers add myhelper mypass
-SecureServ- Successfully added Helper myhelper with Password mypass to Helpers List

Listing an Entry

To list the helpers simple type:

/msg SecureServ helpers list

And all the helpers are listed. Additionally, if a nickname is provided after the login name, it means that this nick is logged into this particular helper account.

The output is as follows:

>secureserv< helpers list
-SecureServ- Helpers List (2):
-SecureServ- fish (Fish)
-SecureServ- myhelper (Not Logged In)
-SecureServ- End of List.

Deleting an Entry

To delete a entry, you must provide the login name you wish to delete. The format of the command is as follows:

/msg SecureServ helpers del <login>

Where:

<login> is the login account you wish to delete.

The output of the command is as follows:

>secureserv< helpers del myhelper
-SecureServ- Deleted myhelper from Helpers List

Exclusion lists allow you to specify certain Hostmasks, Servers, or Channels that should be excluded from monitoring by SecureServ. This exclusion list would allow a administrator to say, allow users on that are matched against Trojans, when the administrator has verified that the Trojan does not in fact exist on the users host.

With NeoStats 3.0, you should also be aware that there are two types of Exclusion Lists. There are "Global" exclusion lists that all modules may optionally use, and there is module specific exclusion lists. SecureServ defaults to not using the Global Exclusion lists. You can enable it by the following command:

/msg SecureServ set exclusions on

Adding a Entry

To add a entry to the Exclusion list, use the following format:

/msg SecureServ exclude add <host/Server/Channel/UserHost> <pattern> <reason>

Where:

<Host/Server/Channel/UserHost> = The type of exclusion you are adding. The different types are:

<pattern> = The pattern you wish to match on. May include wildcard charactors such as * and ?

<reason> = a short description of the exclusion, for operator reference only.

The output is as follows:

[13:20] -SecureServ- Added *.blah.com (userhost) to exclusion list
[13:20] SecureServ Fish added *.blah.com (userhost) to the exclusion list

Listing an Entry

To list the Exclusions simple type:

/msg SecureServ exclude list

And all the current exclusions are listed. Additionally, a Position number is provided for use with the delete command. The output is as follows:

[13:21]  -SecureServ- Exclusion list:
[13:21]  -SecureServ- #bothouse (Channel) Added by Fish on Sat Aug 13 2005 01:20 AM SGT for Requested
[13:21]  -SecureServ- #ircop (Channel) Added by Fish on Sat Aug 13 2005 07:40 PM SGT for IRCop channel
[13:21]  -SecureServ- *irc-chat.net (Host) Added by Fish on Tue Aug 09 2005 10:13 PM SGT for Services Exclusion
[13:21]  -SecureServ- chieftess!*@* (Userhost) Added by Fish on Tue Aug 09 2005 10:14 PM SGT for buggy client
[13:21]  -SecureServ- *.blah.com (Userhost) Added by Fish on Sun Jan 15 2006 01:20 PM SGT for Cause Blah.com is cool
[13:21]  -SecureServ- End of list.

Deleting an Entry

To delete a entry, you should first lookup the Position of the entry that you wish to delete. The format of the command is as follows:

/msg SecureServ exclude del <pattern>

Where:

<pattern> is the pattern of the entry you wish to delete in the list

The output of the command is as follows:

[13:22]  SecureServ Fish used EXCLUDE
[13:22]  -SecureServ- *.blah.com delete from exclusion list

That command forces SecureServ to check the Dat File version at http://secure.irc-chat.net/ and download the latest version if required.

The format of the command is as follows:

/msg SecureServ update

If you wish to create your own custom definition, follow these steps:

If you come across a new "Trojan" or Virus or attack on your network, it might be possible to update SecureServ to be able to detect these new "Virus's"

If you wish us to consider adding support to SecureServ's Definition files for new "Virus's" please provide us with the following information via http://secure.irc-chat.net/ using the "submit new" link (only available when logged in as a member)

The following information is required:

Before adding new items to the Definitions, we do as much research as possible, and also share this information with other "IRC Security" professionals or teams in order to determine the most effective way to detect this "infection"

Additionally, we will add "warning" messages to users that are running old copies of IRC software that are vulnerable to security issues (such as allows a Hacker to break into the users computer via IRC) and advise the user to upgrade their IRC client. If you are a client Author of a script or IRC client that has had Security Issues in the past, and wish us to add this "warning" to the Definitions, please contact us directly.