Display results as :

Rechercher Advanced Search

Web Applications
install Joomla Wordpress Phpbb Drupal FluxBB PunBB osCommerce simple-machines MYBB moodle vBulletin Dolphin-v.7.1.1 PHPNUKE XOOPS
install BorkNet Services X3 Services Anope Atheme Services Srvx IRC Srervices
install Snircd IRCU INSPIRCD UNREAL Nefarious Bircd Bahamut Asuka Charybdis
TCL SCRIPT FOR EGGDROP Allprotection4.7 Antiproxy
Bots install FishBot bobot++ Eggdrop janus Omega Security Services Botnix Bopm SupyBot PyLink Hopm
Latest topics
» mIRCx IRC Network Config
Sat Aug 04, 2018 2:39 pm by Chief

» מדריך הגנות אופרים בגירסאות IRCD
Mon May 14, 2018 5:50 am by Chief

» install irssi v1.2-1.2-dev in freebsd
Thu Mar 22, 2018 5:43 am by Chief

» install ZNC in Ubuntu 14.04
Sun Mar 04, 2018 5:50 am by Chief

» מדריך שינוי גירסאות ב FREEBSD
Fri Mar 02, 2018 8:35 am by Chief

» מדריך התקנה ZNC על WINDOWS 7
Wed Feb 21, 2018 3:30 am by Chief

» Guide install Znc in FreeBsd
Sun Feb 18, 2018 7:58 am by Chief

» Guide install InspIRCd v3.0.0a5 in FreeBsd
Thu Jan 18, 2018 9:52 pm by Chief

» מדריך התקנה Pylink על unrealircd4 && inspircd
Sat Nov 18, 2017 6:35 am by Chief

November 2018

Calendar Calendar

free forum

free forum

Guide install Omega Security Services

Go down

Guide install Omega Security Services

Post  Chief on Sat Oct 13, 2012 5:06 am

Omega Security Service
Omega is a modular security service that has features such as dynamic configuration IP/DNSBL and OPM. Network administrators can also edit the configuration, load modules, and manage your networks security with no
Supported IRCd's
ok today we learn about configure omega and how we can fix conf but first you need download omega you have also some version for download
if download not working then try from here
after you download you need configure

tar zxvf omega-0.7.7-stable.tar.bz2
cd omegairc-source
make install
when you config your omega you need Answer on Question its look like this

after you finish with configure you need fix conf you need to inside in folder omega and in etc you see file in name example.cfg you need to change to security.cfg and after you change name you need to inside to your folder inspircd link.conf and put block like this

<link name=""
after you set block you need rehash your server and fix Security.cfg and now i explain what you need to fix... if you run something version like inspircd version 2 you need write in security.cfg like this

<protocol name="inspircd20" ts6="no">
next step you need to write name network like this

<server name="" sid="44X" numeric="9">
after this you need write link name and you write like this

<link name="yourIP" network="Name network" port="7000" pass="pass" gnutls="no">
next step you have fix settings and you need write like this

<settings ip="yourIP" pidfile="" privmsg="no" operonly="yes" umode="+o">
next step you need fix your Access Directive and you have fix
name  (required) Access name we are storing under
 flags (required) What flags are we going to assign
 host  (required) Host we are going to set the access on
and in Access you can write like this

<access name="yourNick" flags="root" host="*@*">
next step Die Directive if you see this you need to block like this

#<die msg="You should make sure to remove all die tags - yes they are a pita, but it makes you read :)">
next step you have Logging Directive then you can put your chan Admin and only you and oper can see log and you can set like this

<logging channel="#mIRCx" nicks="yes" channels="yes" users="yes">
next step Guardian Directive if in this you change something in host and try run security and you see problem like this

then this say you have Error and you need fix this and you can put like this

<guardian nick="Guardian" host="" ident="security" channels="#mIRCx,#Services,#Security">
next step you have Module directive and no change something in module.... after you have more module is name and you can remove # from
after you have g_bl is module from proxy and you look blacklist like this

<blacklist host="" reason="Your host has been found on a dronebl blacklist">
you can put more blacklist and try your bot... after you fix all conf you need run you bot

cd omega/bin/
you can using in my Security

// $Id: example.cfg 2390 2012-05-04 15:08:35Z twitch $

 *   (C) 2008-2012 Omega Development Team
 *        Configuration file v0.2

/*  Omega allows multiple comment types within the configuration
 *   below are the recognized comment types:
# Single line comment
// Single line comment
/* Multi line comment */

/* Include Directive
*    Allow additional files to be included in configuration
 *  file (required) path of the file to be included.

#<include file="etc/access.cfg">

 * Omega Configuration ID Tag [REQUIRED]
* configuration format may change
 * between versions. If their is no version
 * Omega will assume current version.

<?omega version="2">

  * Protocol Directive
  *  name (required) the name of the protocol to use
  *  ts6  (optional) Weather or not to force TS6 support
  * Supported Protocols:
  * bahamut     (Bahamut IRCd)
  * unreal32    (Unreal 3.2+)
  * ratbox      (ratbox-ircd 2.2+)
  * ratbox3     (ratbox-ircd 3.0+)
  * hybrid      (Hybrid IRCd)
  *     inspircd    (Inspircd 1.1)
 * inspircd12  (Inspircd 1.2)
  *     inspircd20  (Inspircd 2.0)
 *     kcircd      (KC-IRCd)
  *     plexus      (Plexus IRCd)
  *     nafarious   (Nafarious IRCd)
  * Also note if there is not TS6 support for the specified
  * protocol it will be overridden to use non-ts6.  
<protocol name="inspircd20" ts6="no">

 * Server Directive
 *  name (required) Name of our server
 *  sid  (optional) Our server ID (used for TS6 protocols)
 *  numeric (optional) Our Server Numeric (Used for Non-TS6 Links)
*  Note: If numeric or sid is not defined here - It will assume default
 *        values.
<server name="" sid="44X" numeric="9">

 * Link Directive
 *  name    (required) Host/IP of the server we are connecting to
 *  network (required) Network name  
 *  pass    (required) Password sent to our uplink on connect.
 *  port    (optional) Port to connect on default 6667
 *  gnutls  (optional) Use GNUTLS (SSL) while connecting default no

<link name="" network="Omega" port="7000" pass="asher" gnutls="no">

 * Settings Directive
 *  pidfile  (Optional) ( File that stores our pid
 *  ip       (Optional) (Ip)          Our current IP to bind to used for
*                                    inbound/outbound connections
 *  privmsg  (Optional) (Yes|No|1)    Use privmsg to communicate with users
*  operonly (Optional) (Yes|No|1)    Weather Omega is for oper only use,
 *                                    Omega will default to operonly.
 *  umode    (Optional)               Default usermode assigned to local bots.

<settings ip="" pidfile="" privmsg="no" operonly="yes" umode="+o">
 * Access Directive
 * name  (required) Access name we are storing under
 * flags (required) What flags are we going to assign
 * host  (required) Host we are going to set the access on
* Please note, that if there are no flags the core
 * will assume the access entry already exists.
 * For multiple hosts separate the list with a space.
 * IE:
 *  <access name="dev" host="myhost@example.tld" flags="root">
 *  host does a standard wildcard match on the following formats:
 *   nick!user@ip/host
 * user@ip/host
 * *@ip/host
 * You can define access flags 1 of two ways using predefined access
 * such as
 *  <access name="dev" host="myhost@example.tld" flags="root">
 * Or you can define the flags individually
 *  <access name="dev" host="myhost@example.tld" flags="oamljsDdru">
 * Flags
 *    Predefined Access:
 *      Root - amljsDdr
 *      Admin - ralmjsd
 *      Staff - sljr
 *      Oper -  al
 *    Access Flags:
 *       Access - a   Can use Access commands
 *         List - l   Access to LIST commands
 *          Set - s   Access to set commands
 *        Debug - d   Use debug commands (Debug mode must be enabled)
 *          Die - D   Can RESTART/SHUTDOWN Omega
 *       Module - m   Load/Unload Modules
 *         Join - j   Join client to a channel using invite
 *       Rehash - r   REHASH the server.
<access name="ASHER" flags="root" host="*@*">

 * Die Directive
* Do not start the server under any circumstance, bail and die.

#<die msg="You should make sure to remove all die tags - yes they are a pita, but it makes you read :)">

 * Logging Directive (optional)
* channel (optional)  (#channel)  Channel to display log messages to.
 * nicks    (optional) (yes|no)    NICK changes to log channel.
* users    (optional) (yes|no)    Log CONNECT/QUITS/NICKS from the server
 *                                 implies both nicks="yes" connects="yes"
* commands (optional) (yes|no)    Log CONNECT/QUITS
* connects (optional) (yes|no)    Log Connects

<logging channel="#Admin" nicks="yes" channels="yes" users="yes">

 * Guardian Directive
 * Sets the information to the Guardian client
*   nick      (Required) - Sets guardians nickname
 *   host      (Required) - Sets the hostname of guardian
 *   ident     (Required) - Sets Guardians gecos
 *   channels  (Optional) - Sets the channels for guardian to join
 *                          (Guardian will automatically join logchan)
<guardian nick="Guardian" host="" ident="security" channels="#Admin">

 * Module directive
 *  name (Required)  - Module filename
 *  dir  (Optional)  - If dir is specified load all modules in the dir
 *                     name does not need to be specified if dir is given.
*  load (Optional)  - When the module should be loaded
 *        Load Order:
 *              a) Pre  
 *              b) Standard
 *              c) post
 *    Note: If depenancies are not met at the time of load, if module load is
 *          Pre or Standard, the core will push modules down to the next load time
 *          to insure depenancies are met properly, if it still isnt met then we
*          by post, bail on the module load.

 * Guardian Modules
*   Guardian core commands and features

<module name="g_core, g_log, g_access, g_die, g_modlist, g_modreload, g_modunload, g_update, g_modload, g_userinfo, g_opm, g_sessions, g_joinflood">

 * bantime      (Optional) - Length of time for gline/kline/zline, use 0 for permenant
 * defaultflags (Optional) - Default flags for new entries, seperate flags by comma
 * Available flags:
 *    - REGEX

#<module name="g_watch" load="post">

<watch bantime="4h" defaultflags="IGNOREOPERS">

 * pattern    (Required) - Channel/Nickname pattern
 * action     (Required) - Action to be taken
 * reason     (Required) - Reason used for kick or network ban
 * flags      (Optional) - Flags for the watch entry, seperate flags by comma
 * bantime    (Optional) - Length of ban
 * Available actions:
 *    kick, kickban, gline, kline, zline, gzline

# Example channel watch entry
<watchentry pattern="#goaway" action="kickban" reason="Go Away!">

# Example nickname pattern watch entry
<watchentry pattern="BadNick" action="gline" reason="Bad user">

 * Provides Split Tracking

<module name="m_splitserv" load="post">
<splitserv nick="SplitServ" ident="splitserv" host="" channel="#Admin" timeout="2d" splitsave="no" splitexpire="no">  

 * Configure fantasy prefix.
 * Configure fantasy commands prefix, ie a value of ! will have services respond to !<command>
*      within a channel they are presently in. This must be a single character, or only the first
*      character will be taken as prefix.
 *      NOTE: This tag is not required to be present in the configuration file, if it is not present
 *            server will assume value of !

<fantasy prefix="!">

 * Provide DNSBL based proxy lookups

<module name="g_bl">

 *  Black list configration
 *  Configure blacklist lookups, this will allow you to use configure zone block lists
 *  such as dronebl. You can use multiple directives to configure each blacklist.
 *  host   (Required)  The host to use when querying the zone for an IP blacklist entry.
 *  reason (Optional)  Reason string returned to the user which is used in the XLINE entry.
*     Note: IPs are reversed prior to zone lookup IE: will be looked up as
 *  any DNS returns on this address will result in an xline being
 *           placed on the IP address.

<blacklist host="" reason="Your host has been found on a dronebl blacklist">
Guide By mIRCx staff
mIRCx the old Community

מספר הודעות : 224
Join date : 2011-12-09
מיקום : mIRCx IRC Network

View user profile

Back to top Go down

Back to top

- Similar topics

Permissions in this forum:
You cannot reply to topics in this forum