Free neostats irc services software for linux

Open Project Services (OPS) is a project collaboration platform, integrating server components such as e-mail, calendaring, timesheets, documents, knowledge, etc. with standards complient clients. Open Project Services consists of a project server and a set of client extensions.
We are building a project collaboration platform. It consists of a project server that integrates with services needed within a project, e.g. e-mail, calendaring, timesheets, documents, knowledge, etc.
The project server is a Webservices hub based on Java (J2EE). The persistence layer for project information is LDAP. We use OpenLDAP now, but others should also be possible. The e-mail backend makes use of a standard IMAP server. Our reference implementation uses Courier.
We are building extensions/plugins for clients, making them OPS-enabled. We support e.g. Mozilla Thunderbird (XUL) and Squirrelmail (PHP) for e-mail clients. For the calendaring and timesheet components we have a Mozilla Sunbird extension (XUL).
In short: we are building a project collaboration environment on an OSS stack, enriching services with project information, using COTS clients/servers and open standards.
Enhancements:
- This release includes some changes to the underlying LDAP schema to make it possible to disable tasks when they are completed.
- To make use of this new feature, the Web services and the sunbird timesheet client have to be updated.

Libircservice provides an event-driven API to develop IRC services working from a pseudo-server connection.
The library provides functions so that the developer does not need to care about the inter-server protocol and can keep the focus on the service programming logic.
Enhancements:
- This release adds timer stats, global messaging, and channel mode lock functions.
- The samples have been updated to compile with the latest API changes, and several bugs have been fixed.

NeoStats is a powerful and extendable set of *services* for IRC. By Services, we do not mean NickServ/Chanserv etc but additional services.
These additional services include things like StatServ which gives you statistics on the number of users/operators/channels/servers, and MoraleServ, which is a *fun* module, to send funny messages to users, and utility modules.
Some modules have a useful function on your network, other modules are developed for fun, and to make your IRC network more attractive to users.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
NeoStats uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Lots of bugfixes and code cleanups were done.
- Several new modules were added, including quoteserv, textserv, and limitserv.
- This version introduces the ability to write modules in Perl rather than C, as well as the ability to extend the existing modules with Perl code.
- Internally, the code was fixed up to not be as resource intensive as previous versions.
- The module API was enhanced to make it easier for module coders to take advantage of the advanced features of NeoStats.

IRC Services are Services for IRC Networks (or just Services for short) provides for definitive nickname and channel ownership, automatic channel mode setting, memo (short message) storage and retrieval, and greater IRC operator control over the network.
Main features:
- Nickname management. Services allows users to "register" nicknames, and will prevent users other than the registrant from using them. Services also maintains information about each registered nickname, including the last time the nicks owner was online as well as a URL and E-mail address that can be set by the user.
- Channel management. Like nicknames, Services allows users to register channels as well. A channels owner can give privileges to other users of the channel, such as auto-opping or the ability to set various channel options, or conversely deny other users the ability to obtain channel operator privileges or even enter the channel altogether. Services will remember the topic on the channel even after the last user leaves, and can automatically set modes on the channel whenever a user joins it.
- Messages to offline users. Probably every IRC user has gone through the experience of waiting and waiting for someone to come online in order to pass a message along or ask a question. Services alleviates this with a "memo" system, allowing users to leave messages for other users even if the recipient is not online at the time; the recipient will be notified of the memo the next time they log on.
- Centralized network control. Services includes features which allow IRC operators greater control over the IRC network through a single point, and also defines multiple privilege levels for IRC operators with respect to Services itself. For example, IRC operators with sufficient privileges can use Services to set modes on any channel; it is also possible to ban users or groups of users from connecting to the network entirely, and such bans ("autokills" in Services terminology) will remain active even if a server, or Services itself, splits from the network.
Furthermore, each of these sets of features can be configured or disabled to match individual networks policies.
Whats New in 5.1pre4 Development Release:
- This release corrects various minor issues in the previous beta release and updates the ratbox protocol module to better support current versions of the ircd-ratbox server (note that versions earlier than 2.1 are no longer supported).
Whats New in 5.0.61 Stable Release:
- This release fixes a bug which allows users to crash Services on x86-64 (and potentially other non-x86) platforms.

swordcoast.net IRCd is a fork of Undernets IRCu 2.10.12 that features more possibilities for network services, less power for IRC operators, some of QuakeNets Asuka patches, more versatile host hiding, customizable whois information lines, improvements for silence masks, and a few other things.
Enhancements:
- Apart from integrating all changes made in ircu 2.10.12 and Asuka 1.2.1, this release fixes compile issues, EPITHETs, and issues with privilege propagation.
- It adds a command to adjust MAXOPLEVEL per channel, a user mode to shun people (prevent them from doing anything possibly visible to other users except services), extended host hiding (see README), and forced joins and relaying join to services as requests.

The QDS library allows Qt applications to access features provided in common desktop APIs in a portable way, without requiring dependencies on any desktop platform library.
This is especially useful for applications targeting the Unix desktops, because Qt/X11 is very generic and only provides features it can implement on all sub platforms. All library code is licenced under 2-clause BSD licence.
Service implementations are loaded from plugins which link to the respective desktop libraries. The plugin to use can be specified on the applications commandline, in the QDS configuration file or QDS can try to autodetect the currently running platform.
Enhancements:
- Autodetection to use GNOME plugin in case GNOME_DESKTOP_SESSION_ID is set
- Replaced the primitive example application with a simple but network aware text editor application
- Support for wildcards in mailcap entries

Configuration with no services supported script is for a single host firewall configuration with no services supported by the firewall machine itself.

Sample:

# USER CONFIGURABLE SECTION

# The name and location of the ipchains utility.
IPTABLES=iptables

# The path to the ipchains executable.
PATH="/usr/local/sbin"

# Our internal network address space and its supporting network device.
OURNET="10.5.0.0/24"
OURBCAST="10.5.0.255"
OURDEV="eth0"

# The outside address and the network device that supports it.
ANYADDR="0/0"
ANYDEV="ppp0"

# The TCP services we wish to allow to pass - "" empty means all ports
# note: comma separated
TCPIN="ssh,ftp,ftp-data"
TCPOUT="smtp,www,ssh,telnet,ftp,ftp-data,irc,http"

# The UDP services we wish to allow to pass - "" empty means all ports
# note: comma separated
UDPIN="domain"
UDPOUT="domain"

# The ICMP services we wish to allow to pass - "" empty means all types
# ref: /usr/include/netinet/ip_icmp.h for type numbers
# note: comma separated
ICMPIN="0,3,11"
ICMPOUT="8,3,11"

# Logging; uncomment the following line to enable logging of datagrams
# that are blocked by the firewall.
# LOGGING=1

# END USER CONFIGURABLE SECTION
####################################
# Flush the Input table rules
echo -n Flushing forward... && {
$IPTABLES -F FORWARD
} && echo done

# We want to deny incoming access by default.
# echo -n Denying incoming access... && {
# $IPTABLES -P FORWARD drop
# } && echo done

# Drop all datagrams destined for this host received from outside.
echo -n Dropping incoming datagrams... && {
$IPTABLES -A INPUT -i $ANYDEV -j DROP
} && echo done

# SPOOFING
# We should not accept any datagrams with a source address matching ours
# from the outside, so we deny them.
echo -n Preventing spoofing... && {
$IPTABLES -A FORWARD -s $OURNET -i $ANYDEV -j DROP
} && echo done

# SMURF
# Disallow ICMP to our broadcast address to prevent "Smurf" style attack.
echo -n Preventing SMURFs... && {
$IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET -j DROP
} && echo done

# We should accept fragments, in iptables we must do this explicitly.
echo -n Accepting fragments... && {
$IPTABLES -A FORWARD -f -j ACCEPT
} && echo done

# TCP
# We will accept all TCP datagrams belonging to an existing connection
# (i.e. having the ACK bit set) for the TCP ports were allowing through.
# This should catch more than 95 % of all valid TCP packets.
echo -n Accepting valid incoming tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -d $OURNET --dports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done
echo -n Accepting valid outgoing tcp datagrams on existing connections... && {
$IPTABLES -A FORWARD -m multiport -p tcp -s $OURNET --sports $TCPIN ! --tcp-flags SYN,ACK ACK -j ACCEPT
} && echo done

# TCP - INCOMING CONNECTIONS
# We will accept connection requests from the outside only on the
# allowed TCP ports.
echo -n Accepting incoming tcp connections on allowed ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $ANYDEV -d $OURNET --dports $TCPIN --syn -j ACCEPT
} && echo done

# TCP - OUTGOING CONNECTIONS
# We will accept all outgoing tcp connection requests on the allowed TCP ports.
echo -n Accepting outgoing traffic on allowed tcp ports... && {
$IPTABLES -A FORWARD -m multiport -p tcp -i $OURDEV -d $ANYADDR --dports $TCPOUT --syn -j ACCEPT
} && echo done

# UDP - INCOMING
# allow UDP datagrams in on the allowed ports and back.
echo -n Allowing UDP datagrams in on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -d $OURNET --dports $UDPIN -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $ANYDEV -s $OURNET --sports $UDPIN -j ACCEPT
} && echo done

# UDP - OUTGOING
# We will allow UDP datagrams out to the allowed ports and back.
echo -n Allowing UDP datagrams out on the allowed ports and back... && {
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -d $ANYADDR --dports $UDPOUT -j ACCEPT
$IPTABLES -A FORWARD -m multiport -p udp -i $OURDEV -s $ANYADDR --sports $UDPOUT -j ACCEPT
} && echo done

# ICMP - INCOMING
# We will allow ICMP datagrams in of the allowed types.
# echo -n Allowing ICMP datagrams in of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $ANYDEV -d $OURNET --icmp-type $ICMPIN -j ACCEPT
# } && echo done

# ICMP - OUTGOING
# We will allow ICMP datagrams out of the allowed types.
# echo -n Allowing ICMP datagrams out of the allowed types... && {
# $IPTABLES -A FORWARD -p icmp -i $OURDEV -d $ANYADDR --icmp-type $ICMPOUT -j ACCEPT
# } && echo done

# DEFAULT and LOGGING
# All remaining datagrams fall through to the default
# rule and are dropped. They will be logged if youve
# configured the LOGGING variable above.
#

# DoS
# enabling Syn-flood protection
echo -n Enabling Syn-flood protection... && {
iptables -A FORWARD -p tcp --syn -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling Furtive port scanner protection
echo -n Enabling Furtive port scanner protection... && {
iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT
} && echo done
# Enabling ping of death protection
echo -n Enabling ping of death protection... && {
iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT
} && echo done


if [ "$LOGGING" ]
then
# Log barred TCP
$IPTABLES -A FORWARD -m tcp -p tcp -j LOG
# Log barred UDP
$IPTABLES -A FORWARD -m udp -p udp -j LOG
# Log barred ICMP
$IPTABLES -A FORWARD -m udp -p icmp -j LOG
fi
#
# end.