-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial commit from unversioned code from 2007
- Loading branch information
Showing
5 changed files
with
7,874 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
# pyRCX | ||
A Python based IRCX server built on version 2.3 in 2007 | ||
A python IRCX server originally written with Python 2.3 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
The pyRCX chat server | ||
- | ||
written by Christopher J. Webb | ||
- | ||
This server supports IRCX | ||
- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,233 @@ | ||
# pIRCX release 2.4.1 - python release of cppIRCX | ||
# | ||
# A free open source IRCX server | ||
# | ||
# This is the config for your python IRCX server | ||
# Here can you modify the server details and some of the characteristics of it's operation | ||
# Make sure you finish the line with the ';' character. | ||
# | ||
# Note: This server is open source, due to the nature of open source, you can change it how you wish | ||
# You can change the code how you wish, thus making it pointless allowing you to change the server | ||
# raw messages using the conf file. If you ARE an advanced user and understand python, then feel free | ||
# to modify any code with the understanding that I will not be held responsible for any damages. | ||
# | ||
|
||
# Disable features | ||
|
||
# D:IRCX:<oper exempt>; | ||
# | ||
# The above example would disable the use of the IRCX command, | ||
# hence making this a standard IRC server, use upper case only | ||
|
||
# Note: This will not disable ACCESS and PROP, you can disable these though by using D:ACCESS; | ||
|
||
D:USERS:0; | ||
D:SUMMON:0; | ||
D:EVENT:0; | ||
D:WHOWAS:0; | ||
|
||
# the commands below will take out most of the IRCX features | ||
|
||
#D:IRCX:0; | ||
#D:PROP:0; | ||
#D:ACCESS:0; | ||
|
||
# A security focus on many IRC servers is the ability to change nicknames rapidly | ||
# the server by default will not allow any more than 5 changes in 30 seconds but you can modify this | ||
|
||
# N:<AMOUNT OF CHANGES UNTIL PROTECTION>:<TIME WAIT ONCE FLOOD PROTECTION ACTIVATES>; | ||
|
||
|
||
# E <NEW> extensions to the server | ||
# Exempts from server max connections per IP | ||
|
||
# E:IP ADDRESS WILDCARD HERE; | ||
|
||
E:192.168.0.2; | ||
|
||
# Bind address of the server | ||
|
||
# I:12.32.33.199; | ||
|
||
I:; | ||
|
||
f:JOIN; | ||
f:PRIVMSG; | ||
f:INVITE; | ||
f:WHO; | ||
# | ||
# Setting up your server name | ||
# | ||
# S:<server address>:<Servername>:Network; | ||
|
||
S:irc.yourserver.com:irc.lollerchat.com:server; | ||
|
||
|
||
# | ||
# Setting up your Administration | ||
# | ||
# A:<Admin Name>:<Admin Organisation>:<AdminPassword>; | ||
|
||
A:lolname:The pyRCX chat network admin:mypassword; | ||
|
||
|
||
# | ||
# Setting up server security password | ||
# | ||
# P:Password:message; | ||
|
||
P::This server requires a password, please use /pass <PASS>; # Leave null for no password | ||
|
||
|
||
# | ||
# Nickserv security | ||
# | ||
# This key simply implements security into nickserv passwords, this means that an admin cannot view passwords. The key MUST be used, use something random and don't change it | ||
|
||
n:sldffsd@@@@@:1; | ||
|
||
|
||
# | ||
# Setting up your server ports | ||
# | ||
# p:port; | ||
# | ||
# Note: running the server on multiple ports on slow machines may be a detriment to peformance | ||
# Note: case difference, using upper case P will set up a password, not a port | ||
# Note: ports can only be set up before pYRCX is run | ||
|
||
p:6667; | ||
|
||
# | ||
# User rules, how many users can connect | ||
# | ||
# U:<max users>:<max users per connection> | ||
|
||
U:1024:1:Rf; | ||
|
||
|
||
s:~; | ||
|
||
# | ||
# Oper rules, server control | ||
# | ||
# O:<user name>:<password>:<Flags>:<oper motd file>; | ||
# | ||
# o = Sysop, ao = Sysop Manager, aoO = Administrator, aoAO = system administrator | ||
# g = guide, w = watch mode (can see connections), s = secret mode, normal users won't see you as an oper | ||
|
||
O:4:mypassword:aoAO:opermot.conf; | ||
O:3:mypassword:aoAO:opermot.conf; | ||
O:1:mypassword:oaO:opermot.conf; | ||
O:2:mypassword:o:opermot.conf; | ||
|
||
# | ||
# Channel block | ||
# | ||
# C:<default modes>:<max channels>:<max channels per user>:<chanlockdown 1=cannot create new channels>; | ||
# | ||
# Note: I have decided not to add support for +k in the default modes | ||
|
||
C:ntl 75:1024:20:0; | ||
|
||
|
||
# | ||
# Filter rules | ||
# | ||
# F:<level>:<word>:<override> | ||
# | ||
# possible levels, chan, nick, profanity | ||
# | ||
# using the override 1,2,3,4 you can allow staff to use the names | ||
# 0 means totally forbidden | ||
# | ||
# highly recommended to stop users from using your server name, i.e. my server name is pyRCXchat01, so I will forbid it | ||
|
||
F:nick:Global:0; | ||
F:nick:system:0; | ||
F:nick:Guide:1; | ||
F:nick:':1; | ||
F:nick:Sysop:1; | ||
F:nick:Admin:3; | ||
F:nick:server:0; | ||
F:nick:notice:0; | ||
F:nick:nickserv:0; | ||
F:nick:chanserv:0; | ||
|
||
# | ||
# Do not modify this if you don't know what you're doing, if you don't want to use it, just comment it using # | ||
# for example: | ||
# | ||
# F:profanity:*irc.[\-a-z0-9A-Z]+.com*:0; | ||
# | ||
|
||
F:profanity:*irc.[\-a-z0-9A-Z]+.(net|com|co.uk|org)*:0; | ||
|
||
# This will block only complete IRC strings, DO NOT play with this regular expression code unless you fully understand regex and have read below: | ||
# | ||
# * is translated to "(.+|)" | ||
# . has been translated to \. | ||
|
||
F:profanity:*fuck*:0; | ||
F:profanity:*cunt*:0; | ||
F:profanity:*shit*:0; | ||
F:profanity:*wank*:0; | ||
F:profanity:*cum*:0; | ||
F:profanity:*slut*:0; | ||
F:profanity:*piss*:0; | ||
F:profanity:*pussy*:0; | ||
F:profanity:*twat*:0; | ||
|
||
# | ||
# Host masking | ||
# | ||
# H:<level of host mask>:<param>; | ||
# | ||
# 0 - nickname!ident@<no host masks> | ||
# 1 - nickname!ident@80.182.XXX.XXX | ||
# 2 - nickname!ident@shortalgorithm.dsl.in-addr.zen.co.uk (requires parameter), would look like AE3F.in-addr.zen.co.uk | ||
# 3 - nickname!ident@custom.ircpnetwork.com (requires parameter) | ||
# 4 - secure algorithm on IP, i.e. nickname!ident@AE163FB1CD98DD5C (requires parameter) | ||
# 5 - MSN chat style nickname!AE163FB1CD98DD5C@Servername | ||
# 6 - nickname!ident@80.182.FE4.2AA (requires parameter) | ||
|
||
H:6:asuidt@heh; | ||
|
||
# | ||
# Bot lines | ||
# | ||
# B:botconffile | ||
|
||
B:bots.conf; | ||
|
||
|
||
# | ||
# Access entries | ||
# | ||
# X:<max server entries>:<max channel entries> | ||
|
||
X:100:50:20; | ||
|
||
|
||
#Time synchronising | ||
|
||
T:time.apple.com; | ||
|
||
|
||
# | ||
# Linking servers, THIS IS NOT IMPLEMENTED YES, THIS IS FOR FUTURE WORK | ||
# | ||
# Each server must have this line, the server being connected to must have the same password | ||
# | ||
# 1 - listen | ||
# 2 - connect | ||
# | ||
# L:<method>:<server name>:<server address>:<port>:<password>:<server information>; | ||
# | ||
# | ||
# for the server address when you're listening, use the address you want to bind to | ||
|
||
# This is being currently programmed, you can play with it if you want but for now it only lets you connect to another server | ||
# That is stable but I recommend not doing it because I haven't tested it fully. | ||
|
||
L:2:loller02:192.168.0.3:2577:itrDGDFGHkdaq7dd77ajaja91235:UK, Birmingham; |
Oops, something went wrong.