Free response to software for linux

Spamresponder provides a simple and radical spam filter using DNS validation and challenge/response.

Spamresponder is a very simple and radical spam filter, combining DNS validation with the challenge/response approach. It will go through all mail messages in /var/mail/$USER, looking for specific "trusted" strings in the header and body parts of the mail.

It will delete and send an automatic reply to messages which have no "trusted" strings inside them. Those replies will include one of the "trusted" strings, so the recipient just needs to reply to this confirmation message.

The MailFrom-address of an email containing a trusted string becomes a trusted string itself.

Net::Google::Response is a simple OOP-ish interface to the Google SOAP API search responses.

SYNOPSIS

my $service = Net::Google->new(key=>LOCAL_GOOGLE_KEY);
my $session = $service->search();

$session->query(qw(Perl modules));

# You are probably better off calling
# $session->results() but if you want
# the raw response object(s) here ya go :

my $responses = $session->response();
my $count = scalar(@$responses);

# $r is a Net::Google::Response object

foreach my $r (@$responses) {
print sprintf("%s : %sn",$r->searchQuery(),$r->estimatedTotalResults());
}

Provides a simple OOP-ish interface to the Google SOAP API for searching. This package is used by Net::Google.

The Net::Google::Response object is used to contain response information provided by the Google search service in response to a search query. The Response object allows the client program to easily access the data returned from a search.

Response data is accessed using methods with identical names to the elements of a search response (as documented in the Google Web APIs Reference, section 3). For instance, the first example in the SYNOPSIS section, above, would return the estimated number of total results for the query.

Response objects may contain other response objects, where an element would return an array of other elements. For instance, calling $response->resultElements() will return a reference to an array of Net::Google::Response objects, each one representing one result from the search.

The Response module will automatically provide methods for the search response, as described by the service WSDL file. The results format is described by the Google APIs documentation, to which you should refer for the most up-to-date information. As of the April 8th, 2002 release of the Google APIs, the methods below are provided for each search result.

Reliable Response Notification provides guaranteed delivery of critical messages to a wide range of devices. The project guarantees that every emergency will have one, and only one, person responding and taking charge of the recovery.
For integrated services, like some network monitors, help-desk packages, and security suites, Reliable Response Notification allows the user to update records via their mobile devices. It is available as either a standalone server or as a hosted service.
Enhancements:
- The product supports three types of groups: broadcast, escalation and on-call.
- Many devices are supported, including email, SMS, text-to-speech, Jabber, GTalk, SameTime IM, and alphanumeric pagers.
- Integrations for a number of packages are available.
- There is an easy system to add new integrations as needed.

Regular Expression, Arbitrary Protocol, Opensource Filtering Firewall (Reapoff) is an arbitrary protocol proxy. A proxy server is a program which accepts connections on behalf of another program and forwards these connections to the original program. There are a many different commonly used proxies involved, such as web proxies, ftp proxies, and mail proxies.

Proxy based firewalls offer superior protection to packet filtering firewalls. This is because the proxies are interpreting each protocol. This is unlike more conventional packet filtering firewalls which make the assumption that protocol interactions are somehow related to TCP port numbers. Proxy based firewalls offer the following advantages:

Information passed between client and server is guaranteed to conform to the specified protocol
It is possible to specify a security policy on the different operations offered by those protocols.

For example suppose that we have an FTP proxy protecting an FTP server. This proxy ensures that the clients to the FTP server are actually using the FTP protocol. In addition the administrator may also specify a small subset of FTP commands that are allowed, for example no uploads are allowed etc. The best feature about this is that the administrator can deploy the proxy on the perimeter and have the security policy apply to any machines that may be installed inside.

Such a fine level of control is great, but in practice most proxies do not really offer that level of contol, and if they do its difficult to configure.

REAPOFF is an arbitrary protocol proxy. That is to say, the same proxy may be used to control any TCP/IP based protocol - the behavior of the proxy is fully specified by its configuration files. This fact allows REAPOFF to be easily modified to work with any new protocol simply by writing a new configuration file. In addition new features are easily added simply by adding new rules. Removing rules which may not be applicable for a particular scenario can be achieved very easily by commenting these out in the configuration file. The aim of this project is to produce the most intelligent proxy. This is very important for system administrators who need to add a new filtering rule to protect their network against a newly announced vulnerability for example.

The REAPOFF site will have a library of rules, each adding new functionality to the proxy or protecting against a newly announced vulnerability exploitation, in much the same way as IDS or anti-virus vendors include new signatures in response to new vulnerabilities.

SvnReporter generates various reports in response to commits happening in a Subversion repository.

SvnReporter is intended to be called from the post-commit hook. Two types of reports are supported: single-event and event list reports.

The former generate reports relative to the current commit only, and are typically used to generate post-commit mails.

The latter generate reports relative to a list of commits, e.g. an RSS feed or a Web page showing the latest commits.

Reports can be restricted to certain criteria, specified by a list of regular expressions. The format of the reports can be defined with a template.

MEPIS has released MEPIS SoHoServer Test02 for public testing. This release is available for download at public mirrors and the MEPIS subscription ftp server. Look in the “testing” subdirectory.

SoHoServer is a general purpose server based on the recent release of Debian “sarge.”. The preinstalled and configured server software includes Apache2, PHP4, Perl, Mysql, Proftpd, Bind, DHCPd, Postfix, Dovecot, Shorewall, Squid, DansGuardian, Webmin, and Usermin.

Like other MEPIS products, SoHoServer is easy to try, easy to install, and easy to use. It comes preconfigured with defaults that “just work” in most situations. Early testers report that even someone with limited server experience can have a MEPIS SoHoServer up and running in as little as fifteen minutes.

Test 02 has updated preconfigs, in response to user feedback. The latest security updates have been added and the MEPIS tools have been updated to the latest versions.

MaraDNS is a package that implements the Domain Name Service (DNS), an essential internet service.
MaraDNS is intended for environments where a DNS server must be secure and where the server must use the absolute minimum number of resources possible.
MaraDNS was created in response to issues people had with the DNS servers available in early 2001; and has the following design goals:
- Security-aware programming. A DNS server needs to be secure. I have a number of security features in the code, including:
1. The code uses a special string library which is resistant to buffer overflows.
2. The code, if started as root, mandates running as an unprivledged user in a chroot() jail.
- Open-Source. The 1.0 release of the DNS server is public-domain code; the next release will be released under a very liberal BSD-style license.
- Simplicity. This DNS server has the minimum number of features needed to correctly act as an authoritative and/or recursive name server.
Enhancements:
- The AES variant that MaraDNS uses has been hardened against some cache timing attacks that cryptographers have recently published.