Ports 搜索

pkcs11-gateway is a software that allows you to use a Linux 32-bit PKCS#11 module on FreeBSD i386/amd64. It consists of a FreeBSD Cryptoki wrapper library that serializes and forwards PKCS#11 function calls to a Linux server program that dlopen() and use the real module. The communication between the two components is via a UNIX socket. pkcs11-gateway is based on the rpc-layer of Gnome Keyring.

The program Socket implements access to TCP sockets from shell level. First written for the need to open a server socket and read and write to the socket interactively for testing purposes, it quickly evolved into a generic tool providing the socket interface for shell script and interactive use. Please send any comments, suggestions, bug reports etc. to me: Juergen Nickelsen <jn@berlin.snafu.de>

GoTTY is a simple command line tool that turns your CLI tools into web applications. GoTTY starts a new process with the given command when a new client connects to the server. This means users cannot share a single terminal with others by default. However, you can use terminal multiplexers for sharing a single process with multiple clients. For additional security, SSL/TLS client certificate authentication and session encryption should be used.

mod_gzip is an Internet Content Acceleration module for the popular Apache Web Server. mod_gzip uses the well established and publicly available IETF Content-Encoding standards in conjunction with publicy available GZIP compression libraries such as ZLIB to deliver dynamically compressed content 'on the fly' to any browser or user-agent that is capable of receiving it. This is the updated mod_gzip for apache version 2.0 and above. It has better compression and better logging than the builtin module mod_deflate.

CGI::SSI is meant to be used as an easy way to filter shtml through CGI scripts in a loose imitation of Apache's mod_include. If you're using Apache, you may want to use either mod_include or the Apache::SSI module instead of CGI::SSI. Limitations in a CGI script's knowledge of how the server behaves make some SSI directives impossible to imitate from a CGI script.

Jekyll is a simple, blog aware, static site generator. It takes a template directory (representing the raw form of a website), runs it through Textile or Markdown and Liquid converters, and spits out a complete, static website suitable for serving with Apache or your favorite web server. This is also the engine behind GitHub Pages, which you can use to host your project?s page or blog right here from GitHub.

A-Team MySQL LDAP Authenticator (ateam_mysql_ldap_auth) is an authentication plugin for MySQL 5.5.7 and up, and has been tested with 5.6 under FreeBSD. This module allows you to create MySQL users that are then authenticated against an LDAP server. This reduces administrative overhead and eliminates your users having to remember a seperate username and password for MySQL. Just like MySQL Enterprise's PAM module, for client side authentication this plugin uses the clear_text password module as the LDAP server must perform the password hasing and comparison. For command line clients this is done by setting the following environment variable: export LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN=1 In MySQL Workbench this is acheived by going to go to the "Advanced" tab and checking "Enable Cleartext Authentication Plugin" when editing a connction. !!! IMPORTANT: !!! ------------------------------------------------------------------------ !!! ENSURE THE COMMUNICATIONS PATH BETWEEN THE CLIENT AND SERVER IS SECURE! !!! ------------------------------------------------------------------------ !!! By default MySQL does not use SSL so additional steps and network design !!! are needed to ensure you're not exposing your credetials.

XMX is an X protocol multiplexor. It is a standalone utility for displaying an X Windows session on multiple displays. XMX takes advantage of the networked nature of the X Window System by tapping the communication link between an X client and an X server. In this way, XMX works with any X clients and any X servers, without the need to modify either. It's tempting to call this "broadcast software," and that is certainly the effect. In reality, though, XMX is "multicast" software. It must know all the slave machines ahead of time and it connects to each one directly. XMX is more like mail than news. XMX connects to N servers like an X client, then accepts connections from M clients like an X server. One of those servers is designated the "master" from which input is directed to the clients. The other servers are "slaves." Slave servers receive only those protocol requests that are necessary for them to maintain a visual look-alike of the master server's display. This software was developed at Brown University for use in our electronic classroom. Some version of it has been in use here since 1988.

This utility notably decreases the startup time of your X sessions, provided that you start a number of X clients automatically during the X session startup. Most people, for instance, start X clients like xterm, xclock, xconsole and xosview from their .xinitrc, .openwin-init, .xtoolplaces or .xsession file. These X clients are started simultaneously (in the background) which puts a high load on the X server and the OS: * The X server is not multi-threaded, so all X clients are competing to get access to the X server and to use its resources, which causes a lot of overhead (= delay). * The performance of other (non X related) tasks served by the system degrades badly due to the high load. If the system has not enough RAM to hold all the X clients, it is swapping heavily, resulting again in a lot of delay. On the Sun platform there is a utility called 'toolwait' which solves these problems: it starts one X client in the background, waits until it has mapped a window and then exits. Xtoolwait is a free implementation of exactly the same idea.

A user may now build a list of rules that will be used to determine if unsafe images (that are linked to remote sites) will be shown in HTML messages. If a message matches any of the rules and contains images that would normally be initially hidden, then they are now shown by default. The user may choose to always show unsafe images, for all message. This is obviously not recommended by the core SquirrelMail Project Team - or they wouldn't have built this functionality to begin with ( See the following: http://www.squirrelmail.org/wiki/UnsafeImages ). A new section is added to the options page titled, 'Unsafe Image Rules'. Within this page the user may define a number of rules to determine when messages are from a trusted source. These options are very similar to the core message filters plugin. A message field (To, From, CC, Subject) can be matched either against a regular expression, or simply searched to see if the given string is within the field. If a match is found then unsafe images are always shown for this source.