Ports Search

TinyCA is a simple graphical userinterface written in Perl/Tk to manage a small CA (Certification Authority). Currently TinyCA supports the following features: * unlimited number of CAs * support for creating and managing SubCAs * Creation and Revocation of x509 - S/MIME certificates * PKCS#10 Requests can be imported and signed * RSA and DSA keys can be generated and used * Servercertificates o Certificates can be exported as: PEM, DER, TXT and PKCS#12 o Certificates may be used with e.g. Apache, Postfix, OpenLDAP, Cyrus and FreeS/WAN * Clientcertificates o Certificates can be exported as: PEM, DER, TXT and PKCS#12 o Certificates may be used with e.g. Netscape, Konqueror, Opera, Internet Explorer, Outlook (Express) and FreeS/WAN * Certificate Revocation List o CRLs can be exported as: PEM, DER and TXT

Tox is a decentralized, secure messenger with audio and video chat capabilities. You can see it as an alternative to Skype. This is only the core library. To use it, you have to install a client, like e.g. net-im/toxic, net-im/qTox or net-im/uTox. Tox isn't complete yet, but we encourage you to contribute to help make us awesome!

Suck and blow are simple companion utilities for sending data over a TCP socket. They are easy to use and appropriate when FTP is unavailable, or too much of a hassle, e.g., in single-user mode, from within shell scripts, etc. Blow reads the data from standard input, while suck writes it to standard output. Either program may originate the TCP connection, and the TCP port may be specified if desired.

Wapiti allows you to audit the security of your web applications. It performs "black-box" scans, i.e. it does not study the source code of the application but will scans the webpages of the deployed webapp, looking for scripts and forms where it can inject data. Once it gets this list, Wapiti acts like a fuzzer, injecting payloads to see if a script is vulnerable.

This package provides an in-memory B-Tree implementation for Go, useful as a an ordered, mutable data structure.

Array::LineReader gives you the possibility to access lines of some file by the elements of an array. This modul inherites methods from Tie::Array (see Tie::Array). You save a lot of memory, because the file's content is read only on demand, i.e. in the case you access an element of the array. The offset and length of all the lines is hold in memory as long as you tie your array.

This module is a filter for SVN::Notify that translates user account names (e.g. "user1") into email addresses. It does this based on a colon-separated file, like a UNIX passwd file (or more usefully) the AuthUserFile used by Apache. The file path is specified via the --account_file option to the svnnotify script, and the index (zero-based) of the email field is specified via the --account_field option.

SubWeb is a proxy/reverse proxy for HTTP flows. It is possible with SubWeb to handle and visualize HTTP request, headers, body on the fly. It has three operating modes : proxy, reverse proxy, and midproxy (a proxy which requires the pages from another proxy). It can also act as a virtual web server, i.e. answer certain request based on keyword match. SubWeb can also allow filtering, and is highly customizable.

Convert::UUlib is a versatile and powerful decoder/encoder library for a variety of encodings used in Usenet and Mail (uuencode, xxencode, b64, binhex...).

Dbmail is the name of a group of programs that enable the possibility of storing and retrieving mail messages from a database (currently MySQL, PostgreSQL or SQLite). * Scalability. Dbmail is as scalable as the database system that is used for the mail storage. In theory millions of accounts can be managed using dbmail. One could, for example, run 4 different servers with the pop3 daemon each connecting to the same database (cluster) server. * Manageability. Dbmail is based upon a database. Dbmail can be managed by changing settings in the database (f.e. using PHP/Perl/SQL), without needing shell access. * Speed. Dbmail uses very efficient, database specific queries for retrieving mail information. This is much faster then parsing a filesystem. * Security. Dbmail has got nothing to do with the filesystem or interaction with other programs in the Unix environment which need special permissions. Dbmail is as secure as the database it's based upon. * Flexibility. Changes on a Dbmail system (adding of users, changing passwords etc.) are effective immediately.