About me
I'm Bram Matthys ("Syzop") and I'm one of the
UnrealIRCd head coders.
I like the OpenSource philosophy and work on UnrealIRCd on a daily basis for free.
I offer custom coding, special modules and IRC consulting as a way to get
some money out of UnrealIRCd. I've registered myself as an official company (VULNSCAN,
Dutch registry # 30201562).
My coding projects range from small coding
for non-commercial networks, to large projects for various commercial companies.
If you are curious, you can also take a look at my resume
here.
General information
- Payment goes via paypal (credit card) or international bank transfer
- All prices include any VAT
- All products come with an installer, documentation and support.
- For at least 1 year any upgrades (bugfix only) will be provided free-of-charge
- All products are licensed network-wide (you only have to buy them once per-network).
- All products can be tweaked or extended if you have special wishes
- Discounts are available if you buy multiple products (contact me prior to purchase).
- Unfortunately I had to
disable the display of prices in USD due to the quick
changes in conversion rates. I hope to come up with a solution sooner or later. It just takes
too much effort to accurately track everything at the moment.
- If you have any questions,
mail me!
Product list
SQLAuth
This module requires everyone to authenticate before (s)he is allowed in. Useful for restricted or paid chat systems
You can either authenticate by nick+pass or by pass only (in the form of 'UserName/Pass'), then the
SQL server is queried to see if you are allowed in or not.
This is not a complete system, but only the authentication module... you'll need to code an online registration&administra
tion
system yourself (or ask me to do it). Then, you can simply use the module, everything is configurable: db login/pass, database
, table,
field names of user/pass, backdoor password, error msgs, etc.
NEW: Besides MySQL, this module now also supports PostgreSQL.
Price: 100 EUR
[Request more info]
SQLMod
Like SQLAuth but a lot more advanced. This module can be fully customized to suit your needs.
- - user and channel access/authorization info is all stored in an SQL database.
- - on-connect authorization, various options:
- - optional (only for registered nicks)
- - mandatory (everyone needs a regged nick in order to get in)
- - depending on host (very useful for abusive ISPs)
- - only 1 server needs access to the SQL server.
- - nickchanges to registered nicks are not permitted unless the correct password is supplied (so if you see a nick
you can be SURE it is that person, such nickchanges are simply denied, not after 1 minute like with many services).
- - in case of a main- or SQL-server failure it can be configured to still allow users in but with Guest nicks
- - +v/+h/+o/+a/+q access is stored in the database and access is given on-join or via a command.
- - as usual everything is highly configurable: sql db, usertable layout, chantable layout, fail messages, backdoor password
,
encrypted passwords, etc etc
- - Additional customizations are possible like retrieving age (date of birth) from the SQL database and "18+" chanmodes,
or any other crazy ideas you can think of ;).
The only main requirement for this module is a fast SQL server and a reasonable stable net (just like with services).
This module is currently in use for:
- paid/restricted chat systems (chatsites requiring you to register first, dating sites, etc.)
- integration with existing SQL infrastructure, like forums (vbulletin, ubb.threads, ..)
|
 |
 |
| Logging in with a registered nick |
After-auth |
Channel auth & mysql |
Price: 150 EUR
[Request more info]
NSAuth
This module integrates the power of services and nick registration in the ircd itself, it comes with 2 modules:
- an UnrealIRCd module
- a services module (currently supported: ircservices, anope)
SUMMARY:
Nobody can take a registered nick unless they identified for it (for example, on-connect the user will be prompted for a password). Unregistered users can join without requiring a password, though the module can be configured to only allow registered users (ideal if you have spam problems and use nick-registration-via-the-web). See below for a more detailed list of features.
FULL LIST OF FEATURES:
- You cannot use a registered nick BEFORE you have authenticated yourself, if you connect with for example 'Test' (a registered nick) the server will say: * This is a registered nick, please enter the password via /PASS or choose another nick. Also '/nick Test' afterwards is not permitted if you have not identified yourself, you'll have to use '/nick Test:password' instead. This feature pro-actively enforces registered nicks rather than that you can change to the nick and have 1 minute to identify yourself. With this system if you see 'YourFriend' you can really be sure it's him, this also affects various other things, for example, just to name something: using nicks in exempts (+e Somenick!*@*) is 100% safe.
- When identifying for a nick (either on connect or /nick regnick:pass afterwards) the old session is automatically killed ("auto ghost").
- By default unregistered nicks are allowed in (without requiring a password), but you can optionally turn 'mandatory auth' on which forces everyone to identify with a registered nick + password before allowed in, might be helpful in some cases (eg: heavy spam problems). Note that in such a case nickregistration-via-the-web is recommended, or else no new users can come in.
- 'forced registration glines': if you place a gline on %nick@host it forces them to identify themselves before allowed in. This is very useful for abusive ISPs or during clone attacks, you just: /gline %*@*.bezeqint.net 0 This ISP has abuse problems, please use a registered nick to identify yourself. And then all users from *.bezeqint.net will have to identify themselves.
- (related to above) Exempts are also fully supported (except tkl { type gline; mask "%user@host"; }).
In short, this module can be an excelent tool for secure nick enforcement or in case of spam problems.
Price: 150 EUR
[Request more info]
Monitor

(click to enlarge)
[Why I sell unethical modules]
This module is meant as an replacement for the old +I (invisibility) usermode.
But it's actually lot better: you can add/remove targets to the Monitor list, then all the
traffic sent to one of these monitor targets is forwarded to 1 central channel.
Take a look at the screenshot for a simple example.
Full feature list:
- - Everything is logged to 1 channel:
- - other opers can see what's going on.
- - makes it easy for opers (as a group) to take decisions regarding the situation
- - Access control
- - Specify an operlevel that is required to join the monitor channel (eg: admin and higher)
- - Specify an operlevel that is required to use the /MONITOR command (add/remove targets).
- - Optionally, require opers to login with a password (/MONITOR LOGIN pass) before they can use Monitor.
- - Possible to monitor private messages too (although this is considered unethical, and thus disabled by default)
- - If the above is enabled, all commands executed by the user will be shown too (MAP, LINKS, WHO, etc)
This is a highly advanced (~1600 lines of code) and powerful module, it's typically used for monitoring of: suspected hackers,
attackers, trading of illegal material, etc..
NOTE: You must provide me with a good reason before you can order this module, so please contact me prior to purchase.
Price: 120 EUR
[Request more info]
SQLLog
This module allows you to log all kinds of events to an SQL database rather than a logfile.
Features:
- - Logging of:
- - connects, disconnects
- - tkls (kline, zline, gline, gzline, shun)
- - kills
- - oper ups (also failed attempts)
- - operoverrides
- - Network-wide: only 1 server needs access to the SQL server/database, all other servers forward their events.
Requires MySQL.
This module has been in use for over 1.5 years and has proven to be useful :)
Price: 100 EUR
[Request more info]
RestrictedOper
With the Restricted Oper (roper) module you can create "opers" with (very) restricted oper rights. The opers do not in fact have real oper privileges, except for the commands you explicitly specify.
Ideal for opers in training. If configured right, it will even not disclose server (and user) ips and other sensitive info to your restricted oper.
A few examples of what is possible:
- - An oper that can only kill, but cannot see or do anything else than a normal user (cannot even see server ips, etc).
- - An oper that can "only": kill and use join OperOverride and SAMODE.
- - Etc..
The module is very flexible and allows you to individually enable commands, while keeping the rest disabled. Snomasks can also be completely turned off. Naturally, every roper block can be configured on it's own, so all the examples from above can be used at the same time.
Technical note: services do not see the user as an oper (users do however, in /whois), this is usually the prefered behavior anyway (so the restricted oper does not have extra services privileges), but might be something you have to take into account.
Price: 80 EUR
[Request more info]
SQLRegCheck
Yet another SQL module, but a "simple" one:
This module was requested by someone who has a web portal and wanted to have the users register there,
and if they did that they could use that login+pass to register with NickServ too.
If the user tries to register via nickserv (either via /msg nickserv register.... or /ns register...) then the
module checks in an SQL database if the user is already registered with that username+password, if not.. then
a notice is posted (eg: "Please register first at www.myirc.net/register.php").
Price: 70 EUR
[Request more info]
ConnThrottle
This module throttles connections to a specified rate (eg 20 connections per minute local, 40 connections per minute global). It tries to this in an "inteligent" way, thus avoiding needless blocked out users due to false alarms, while still protecting against mass (bot/clone) attacks.
The following options are present:
- - local-throttle: throttles local incoming connections to X in Y seconds
- - global-throttle: throttles network-wide incoming connections to X in Y seconds
- - reason: the reason you specify for throttling (default: "Too many users trying to connect, please wait a while and try again")
- - start-delay: when the ircd starts up there are usually a lot of clients connecting initially, therefore during this specified period no throttling will be enabled, this default period is 3 minutes.
- - netsynch-delay: when a server links to the net, it might have been since it just booted up or due to network problems, therefore the incoming client count on such a "just-linked-server" will not be used for the global throttling counter.
Additionally, this module provides a /THROTTLE command which allows you to (temporary) suspend throttling and lets you view statistics.
Price: 75 EUR
[Request more info]
IRCOpProtect
This module comes with 2 features:
- protect opers from killing or [zkg]lining "higher opers". So: an co-admin cannot kill or kline
an admin/netadmin/services admin, a normal global oper cannot kill a co-admin/admin/.., etc...
If such an attempt is made, a global warning message is sent.
- ability to limit the amount of kills/*lines to X per XX seconds (for non-netadmins).
Price: 60 EUR
[Request more info]
WebTV/WebDetect
This consists of 2 modules, but they are usually sold together.
WebDetect will automatically detect WebTV (or now called MSN TV) users and
put them +V, this means all your non-webtv users can stay -V.
The 2nd module 'WebTV' provides several enhanced features for webtv users, the ability to:
- see nick changes
- see mode changes
- see the banlist via /msg irc banlist #chan
- see the ban exceptions list via /msg irc exceptlist #chan
This module is currently in use on several networks.
Price: 60 EUR
[Request more info]
Helpop Login System
This module makes it easy to have helpops without ircop rights.
HelpOps can simply log in with /hlogin username password and then they get usermode +h, are autojoined to the help channel(s),
and you can optionally give them a vhost too.
You simply add them with helpop { } blocks in your unrealircd.conf, just like you add opers.
Price: 60 EUR
[Request more info]
QFloodBan
This module can be useful if you have users (or bots/drones) that repetetive go excess flood when trying to herass other users.
The modules makes it possible to take action upon excess flood and sendq exceeded. If a a certain specified threshold is exceeded (eg: 2 in 10 minutes) then it will place a *line/shun. Threshold are counted globally, so if the user connected to another server after getting disconnected after a flood (s)he will still be catched. The threshold, bantime, bantype (gline/kline/zline/etc) and ban reason are all configurable (both for excess flood and sendq exceeded individually).
Price: 70 EUR
[Request more info]
Setup&Support
For installation and support of IRCds+services+bopm etc, see
IRCDSETUPS.COM
Price: Varies
[Request more info]
Custom coding
I can probably code "anything" you want, to name a few things:
- - new commands (/cmd)
- - new usermodes
- - new channelmodes, extended bans
- - customized windows versions (build-in modules, tiny modifications, more connections, ..)
- - special authorization modules
- - web interfaces or part of websites related to IRC (eg: registration, statistics, admin/user config panels, online chat,
etc).
- - I've now done various IRC+SQL projects, so if you need something like that you are at the right place ;).
- - Other IRC-related coding: services (anope&ircservices only), eggdrop/TCL, etc.
- - IRC consulting
- - etc..
Price heavily depends on the request and time involved to code it. Modules are usually ~$100, $50/$75 for simple requests.
NOTE: custom coding is currently (as of April 2007) unavailable. I still sell existing modules, though.
Price: varies
[Request more info]
Products and services are subject to this user agreement