Ports Search

UPnP media server MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices. MediaTomb implements the UPnP MediaServer V 1.0 specification that can be found on http://www.upnp.org/. The current implementation focuses on parts that are required by the specification, however we look into extending the functionality to cover the optional parts of the spec as well.

OpenH323 is a multi-platform H323 Video Conferencing library. This is used to make H323 Video Conferencing applications like GnomeMeeting and ohphone. (both in the FreeBSD ports tree) The library includes a sample program called simph323. The OpenH323 library makes use of PWLib. http://www.equival.com PWLib is a multi-platform code library that can be used to write applications that will compile and run on the BSD Unixes, Windows, Linux and a few other Unix variants. It was developed by Equivalence Ltd Pty.

The Flow module provides the decoding function for NetFlow version 5,9 and IPFIX, and the encoding function for NetFlow version 9 and IPFIX. It supports NetFlow version 9 (RFC3945) and NetFlow version 5 (http://www.cisco.com/) and IPFIX(draft-ietf-ipfix-protocol-26.txt). Regretfully, it doesn't provide the full specification of IPFIX, yet. It is future work. You can easily make the Flow Proxy, Protocol Converter and Flow Concentrator by using the combination of both function. And also, you can make the flexible Collector which can receive any Templates by using the Storable perl module.

libnet is a collection of Perl modules which provides a simple and consistent programming interface (API) to the client side of various protocols used in the internet community. For details of each protocol please refer to the RFC. RFC's can be found a various places on the WEB, for a starting point look at: http://www.yahoo.com/Computers_and_Internet/Standards/RFCs/ The RFC implemented in this distribution are Net::FTP RFC959 File Transfer Protocol Net::SMTP RFC821 Simple Mail Transfer Protocol Net::Time RFC867 Daytime Protocol Net::Time RFC868 Time Protocol Net::NNTP RFC977 Network News Transfer Protocol Net::POP3 RFC1939 Post Office Protocol 3

Net::SSH2 is a perl interface to the libssh2 (http://www.libssh2.org) library. It supports the SSH2 protocol (there is no support for SSH1) with all of the key exchanges, ciphers, and compression of libssh2. Unless otherwise indicated, methods return a true value on success and false on failure; use the error method to get extended error information. The typical order is to create the SSH2 object, set up the connection methods you want to use, call connect, authenticate with one of the auth methods, then create channels on the connection to perform commands.

This is a server daemon, port scanner and (optionally) clients for FSP, the File Service Protocol. FSP is lightweight and connectionless. It is typically used for offering files to "anonymous" visitors over a congested link. It uses UDP rather than TCP sockets. A service contact port (well-known port) for FSP has not been assigned by IANA (per RFC 1700). See <URL:http://www.faqs.org/faqs/fsp-faq/> for an overview. To use fspd, you must copy the fspd.conf.sample file, normally installed in /usr/local/etc/, to fspd.conf and edit it. You can run fspd from inetd or stand-alone.

POE::Component::Server::NNTP is a POE component that implements an RFC 977 http://www.faqs.org/rfcs/rfc977.html NNTP server. It is the companion component to POE::Component::Client::NNTP which implements NNTP client functionality. You spawn an NNTP server component, create your POE sessions then register your session to receive events. Whenever clients connect, disconnect or send valid NNTP protocol commands you will receive an event and an unique client ID. You then parse and process the commands given and send back applicable NNTP responses. This component doesn't implement the news database and as such is not by itself a complete NNTP daemon implementation.

This code appears to have only cursory resemblance to Bruce Schneier's blowfish and twofish algorithms in that it too has a table-based decoder. Derivation from FairKeys code by Jon Lech Johanson at nanocrew.net. If you don't know what that is, don't bother looking here further. This is a Pure Perl implementation. I doubt there is any need for xs coding for what would mainly be processing 16 bytes at a time. This code is part of an ongoing effort to clone portions of the Apple iTMS in Perl for portability. See www.hymn-project.org for prior efforts by others.

SKS OpenPGP Key Server SKS is a new OpenPGP keyserver whose goal is to provide easy to deploy, decentralized, and highly reliable synchronization. That means that a key submitted to one SKS server will quickly be distributed to all key servers; and even wildly out-of-date servers, or servers that experience spotty connectivity, can fully synchronize with rest of the system. Refer to the online references for pointers on downloading a full copy of the public PGP databse (about 2Gb) and on tweaking the your configuration. http://www.keysigning.org/sks/ may help you getting started.

Steghide is a steganography tool which is able to hide data in "container files" and to extract this data again. If you do not know what steganography is take a look at Neil F. Johnson's paper about steganography at http://www.jjtc.com/Steganography/ Steghide is designed to be portable and configurable and features hiding data in bmp, wav and au files, blowfish encryption, MD5 hashing of passphrases to blowfish keys and pseudo-random distribution of hidden bits ("stego bits") in the container data.