Free twisted knee software for linux

Twisted Names project is both a domain name server as well as a client resolver library.
Twisted Names comes with an "out of the box" nameserver which can read most BIND-syntax zone files as well as a simple Python-based configuration format.
Twisted Names can act as an authoritative server, perform zone transfers from a master to act as a secondary, act as a caching nameserver, or any combination of these.
Twisted Names client resolver library provides functions to query for all commonly used record types as well as a replacement for the blocking gethostbyname() function provided by the Python stdlib socket module.
Twisted Names is available under the MIT Free Software licence.
Enhancements:
- Errors in the markup used in API documentation have been fixed.
- A bug where the DNS client would sometimes drop a response has been fixed.
- A bug which prevented non-IN lookups from generating malformed queries has been fixed.

Twisted Web includes an HTTP/1.0 protocol implementation for both servers and clients. Twisted Web also includes a resource framework for implementing rich, dynamic web applications. It includes support for authentication either via HTTP AUTH, session URLs, or session cookies.
It supports CGIs and a custom PB-based distribution mechanism for serving content from separate, persistent processes. It includes SOAP and XML-RPC support for both clients and servers. It also makes it particularly easy to deploy new servers with novel or ephemeral use-cases, often with only a single short command.
Enhancements:
- This release adds HTTP Basic auth support for XML-RPC clients, and fixes several date, time, and If-Modified-Since header parsing corner-cases.
- Various performance improvements have been made, and support for CGIs broken in a few specific ways has been improved.

TwistedJava provides an implementation of the Perspective Broker protocol in Java.
TwistedJava is an LGPLed implementation of the Perspective Broker protocol for Java. PB is a remote object protocol, similar to RMI, supporting multiple programming languages.
Included is a policy (Straw) written by Brandon Wiley that lets you use remote Java objects transparently.
You can read the README for the latest version, or read the API javadocs.
Enhancements:
- Adds support for logging in to Twisted 1.1 PB servers.

Twisted Packager II (TP2) is a package manager that aims to make live easy - for end users and also developers. In some respects it is similar to Autopackage - it does not intend to replace the "system packaging tool" but instead will sit alongside it to allow application developers an easy way to package software; and system administrators an easy way to install [or remove!] such software.
TP2 excels at handling generic software - and allows a "source" type package [such as itself!] to be installed across multiple architectures and operating systems using the same package.
TP2 is cross-platform; it is currently in use on Solaris, Linux and HP-UX. Soon the intention is validate it also for BSD and AIX.
TP2 is flexible. It supports dependency management, package verification, preview installation and removal, and audit logs all activity.
TP2 is powerful. It supports "namespaces" which allows the same packages to be installed into different areas on the same machine. Non-root users can be given areas which they can manage independently.
Enhancements:
- Initial public announcement, though the software has been in use in several environments for over 12 months.

Twisted Words library provides implementations of a handful of IM protocols, including IRC, MSNP8, OSCAR, TOC, and Jabber.

Twisted Words provides two separate high-level end-user features:

a multiprotocol instant messaging server
a multiprotocol instant messaging client

These are both still in the early stages of development and are not expected to work flawlessly in all configurations, however each is quite usable for a limited set of functionality. A Twisted Words server can be created with just a couple commands:

$ mktap words --irc-port 6667 --pb-port 8787 --passwd password_file --group somegroup
$ twistd -f words.tap

The Twisted Words client is named im and is usable as an IRC client, and possibly an AIM client (depending on the phase of the moon).

Low Level Functionality:

Twisted Words also includes:

Low-level protocol implementations of OSCAR (AIM and ICQ), IRC, MSN, TOC (AIM).
Jabber libraries.

Prototypes of chat server and client frameworks built on top of the protocols.

Kwotes is a chat quote database system with a twist.

The quotes are publicly moderated, so its up to you to maintain the quality. All quotes are accepted and if their ranking falls too low for too long, they are deleted.

IRC->Telnet project is a IRC to telnet bridge.

IRC->Telnet is a bridge which allows you to use IRC clients to access telnet-based online games like MUSHes, MUDs, and MOOs.

Quick installation guide

- install Twisted
- Add to your PYTHONPATH
- run "mktap irctelnet -p -h -t "
- run "twistd -f irctelnet.tap"
- run your IRC client when the host is the host running twistd, and the port is the "local port" above.

This is a plugin that makes it possible for you to use your favourite IRC client to connect to MUSH/MUD/MOOs.

Well, after its installed and running you connect with an IRC client. Then you join some channel (doesnt matter which). The server will connect to the remote telnet-based site, and relay.

Anything you say (that is, none-CTCP PRIVMSGs) is just relayed to the remote site. Emote PRIVMSGs are sent as : , which is usually the emote command in M[UO]*s

ASK is a spam killer. This program (Active Spam Killer, or ASK for short) takes an "Active" approach in solving the problem: Everytime an email is received, a message is sent back to the sender asking for confirmation. If that sender does not confirm the message, it remains queued for delivery. If the sender confirms, the message is delivered and removed from the queue. The "confirmed" senders will be added to your "whitelist" and will never be sent another confirmation. Messages from these emails will always be delivered immediately . You can also specify an "ignorelist" for emails that should be always ignored and a "blacklist" that will cause a nastygram to be sent back to the sender everytime an email is received.

There are many traditional approaches to avoiding spam. The most common approach is based on "content-filtering": a program that attempts to classify incoming mails based on their content. This works partially, but in reality, its somewhat easy to find ways to avoid it.

ASK takes advantage of the fact that most spammers use invalid or fake "From:" address in their messages. When a new message arrives and the sender is unknown, ASK sends a "confirmation message" back, informing the sender that the original message has been queued, pending confirmation. When the sender confirms (a simple reply), ASK delivers the original message and adds the sender to a "whitelist". Further messages from this sender will be immediately delivered. It is also possible to ignore messages based on specific criteria, like senders email, subject and so on.

The goal of ASK is to block Spam mail before it is delivered to your mailbox. As we know, filtering alone is not effective since many times Spam mail contains no detectable elements.

ASK should be invoked from .forward (or .procmailrc if you are using procmail). The incoming message should be piped to ASK, which will be in charge of doing the actual delivery.

When ASK receives an email, if first checks the email address against your "ignorelist". If the address is listed there, its ignored completely. Then, the message is checked against your "blacklist". If its there, a nastygram is sent back to the sender with something like "Please stop sending me emails" in the Subject line.

The real fun happens when an email comes from an unknown user (i.e, someone not in any of your lists). In this case, ASK calculates the MD5 checksum of the message + a secret MD5 key (configured during installation time). This number is sent as part of a "confirmation message" back to the user. If the user replies to it, the confirmation number (in the subject) is recognized, the message is dequeued and delivered. If the user does not reply, the message remains queued until its removed.

The program has some intelligence to deal with specific cases. For instance, if a mail is sent to a non-existing user, the error message from mailer-daemon is ignored. This avoids seeing lots of "invalid user" messages in your inbox.

Another interesting "twist" is that messages coming from your own email address are never trusted. If the spammer knows your address he could easily fake your own address as the From: line. Messages coming from you will be identified by a "mailkey", a piece of string you always put on your message by default (maybe a piece of your own signature). Note that this has the added side-effect of allowing any messages coming in reply to a message you sent to someone (as long as that person keeps your "mailkey" in its quoted reply, a practice common these days).

The program never deletes any messages. For instance, if you send yourself a message without your mailkey (a possible Spam), it will be saved in a "Junk" mailfolder (you can specify this folder during the configuration).