Ports Search

The Cyrus IMAP (Internet Message Access Protocol) server provides access to personal mail and system-wide bulletin boards through the IMAP protocol. The Cyrus IMAP server is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP system. All user access to mail is through software using the IMAP, POP3, or KPOP protocols. The private mailbox database design gives the server large advantages in efficiency, scalability, and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies.

Paraphrasing the website: Mailman is a mailing list manager (MLM); that is, software to help manage email discussion lists, much like Majordomo, LISTSERV, and the like. Unlike most similar products, Mailman gives each mailing list a web page and allows users to subscribe, unsubscribe, and change their preferences via the web. Even a list manager can administer his or her list(s) entirely via the web. Mailman integrates many common MLM features, including web-based archiving (though it also has hooks for external archivers), mail-to-news gateways, bounce handling, spam prevention, Majordomo-style email-based list administration, direct SMTP delivery (with fast bulk mailing), digest delivery, virtual domain support, and more. Mailman is written mostly in Python (with a smattering of C where necessary for security purposes), and includes hooks to make it easily scriptable and extensible. It is compatible with most web servers and browsers, and most mail transfer agents (mail servers). Mailman's documentation may be found on its website.

Frontier::RPC implements UserLand Software's XML RPC (Remote Procedure Calls using Extensible Markup Language). Frontier::RPC includes both a client module for making requests to a server and a daemon module for implementing servers. Frontier::RPC uses RPC2 format messages. RPC client connections are made by creating instances of Frontier::Client objects that record the server name, and then issuing `call' requests that send a method name and parameters to the server. RPC daemons are mini-HTTP servers (using HTTP::Daemon from the `libwww' Perl module). Daemons are created by first defining the procedures you want to make available to RPC and then passing a list of those procedures as you create the Frontier::Daemon object. The Frontier::RPC2 module implements the encoding and decoding of XML RPC requests using the XML::Parser Perl module.

WIDE-DHCPv6 is an open-source implementation of Dynamic Host Configuration Protocol for IPv6 (DHCPv6), originally developed by the KAME project. The implementation mainly conforms to the following standards: - RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) - RFC3319: DHCPv6 Options for Session Initiation Protocol (SIP) Servers - RFC3633: IPv6 Prefix Options for DHCP - RFC3646: DNS Configuration options for DHCPv6 - RFC3898: Network Information Service (NIS) Configuration Options for DHCPv6 - RFC4075: Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6 - RFC4242: Information Refresh Time Option for DHCPv6 - RFC4280: DHCP Options for Broadcast and Multicast Control Servers Note that the current implementation does not support temporary IPv6 address allocation by DHCPv6, and there is no plan to implement that feature at the moment.

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications don't know how to gain access through SOCKS servers. This means that network based applications that don't understand SOCKS are very limited in networks they can reach. An example of this is simple 'telnet'. If you're on a network firewalled from the internet with a SOCKS server for outside access, telnet can't use this server and thus can't telnet out to the Internet. tsocks' role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary.

GNU SASL is an implementation of the Simple Authentication and Security Layer framework and a few common SASL mechanisms. SASL is used by network servers (e.g., IMAP, SMTP) to request authentication from clients, and in clients to authenticate against servers. GNU SASL contains a library (`libgsasl'), a command line utility (`gsasl') to access the library from the shell, and a manual. The library includes support for the SASL framework (with authentication functions and application data privacy and integrity functions) and at least partial support for the CRAM-MD5, EXTERNAL, GSSAPI, ANONYMOUS, PLAIN, SECURID, DIGEST-MD5, LOGIN, NTLM and KERBEROS_V5 mechanisms. The library is portable because it does not do network communication by itself, but rather leaves it up to the calling application. The library is flexible with regards to the authorization infrastructure used, as it utilizes callbacks into the application to decide whether an user is authorized or not.

FastCGI Development Kit. FastCGI is a fast, open, and secure Web server interface that solves the performance problems inherent in CGI, without introducing the overhead and complexity of proprietary APIs (Application Programming Interfaces). FastCGI allows for many nice features such as persistent CGI applications (eliminating process creation time per request) and being able run CGI applications on hosts remote to the web server itself. Most web servers have optional or add-on support for FastCGI. Applications which are developed with FastCGI behave as standard CGIs when invoked by web servers without FastCGI support. In other words, if the server supports FastCGI, then FastCGI applications get all the perks (mainly being *really* fast); if the server does not support FastCGI, then FastCGI applications behave exactly like standard CGIs.

WebStone is free benchmarking tool for web servers available from Mindcraft. The version available here has been SSL enabled, so secure web servers can be benchmarked using our version. In addition to the default configuration parameters, the following can be specified: 1. SSL_VERSION: SSLv2, SSLv23 or SSLv3 (default SSLv3) 2. SSL_CIPHER(SSL preferred cipher): use ssl ciphers specified in ssl[2,3].h, e.g RC4-SHA, IDEA-CBC-SHA, DH-DSS-DES-CBC3-SHA (default EDH-RSA-DES-CBC3-SHA). Specifying an SSLv2 cipher in SSLv3 mode won't work (and vice versa) 3. SSL_CACHE_MODE(client cache mode): ON, OFF (default OFF) 4. SSL_MIX(percentage HTTPS connections, remaining connections are filled in with HTTP connections): 0.0-1.0 (default 1.0) 5. HTTPS_PORT: port (default 8443)

Grip is a front-end to external cd audio rippers (such as dagrab or cdda2wav). It also provides an automated frontend for MP3 encoders, letting you take a disc and transform it easily straight into MP3s. The CDDB protocol is supported for retrieving track information from disc database servers. Grip works with DigitalDJ to provide a unified "computerized" version of your music collection.

Autobench is a simple Perl script for automating the process of benchmarking a web server (or for conducting a comparative test of two different web servers). The script is a wrapper around httperf. Autobench runs httperf a number of times against each host, increasing the number of requested connections per second on each iteration, and extracts the significant data from the httperf output, delivering a CSV or TSV format file which can be imported directly into a spreadsheet for analysis/graphing.