Some commonly used Perl modules don't have SSL support at all, even if the
protocol supports it. Others have SSL support, but most of them don't do proper
checking of the server's certificate.
The Net::SSLGlue::* modules try to add SSL support or proper certificate
checking to these modules. Currently support for the following modules is
available:
- Net::SMTP - add SSL from beginning or using STARTTLS
- Net::POP3 - add SSL from beginning or using STLS
- Net::FTP - add SSL and IPv6 support to Net::FTP
- Net::LDAP - add proper certificate checking
- LWP - add proper certificate checking
There is also a Net::SSLGlue::Socket package which combines SSL and non-SSL and
IPv6 capabilities to make it easier to enhance modules based on
IO::Socket::INET.
Unix::Passwd::File can be used to read and manipulate entries in Unix system
password files (/etc/passwd, /etc/group, /etc/group, /etc/gshadow) but can also
be told to search in custom location, for testing purposes).
This module uses a procedural (non-OO) interface. Each function in this module
open and read the passwd files once. Read-only functions like `list_users()` and
`get_max_gid()` open in read-only mode. Functions that might write to the files
like `add_user()` or `delete_group()` first lock `passwd.lock` file, open in
read+write mode and also read the files in the first pass, then seek to the
beginning and write back the files.
No caching is done so you should do your own if you need to.
Pam_p11 is a plugable authentication module (pam) package
for using crpytographic tokens such as smart cards and
usb crypto tokens for authentication.
Pam_p11 uses libp11 to access any PKCS#11 module.
It should be compatible with any implementation, but it
is primarely developed using OpenSC.
Pam_p11 implements two authentication modules:
* pam_p11_openssh authenticates the user using his
openssh ~/.ssh/authorized_keys file.
* pam_p11_opensc authenticates the user using
certificates found in ~/.eid/authorized_certificates.
Pam_p11 is very simple, it has no config file, no options
other than the PKCS#11 module file, does not know about
certificate chains, certificate authorities, revocation
lists or OCSP. Perfect for the small installation with no
frills.
The Suricata Engine is an Open Source Next Generation Intrusion Detection and
Prevention Engine developed by the Open Information Security Foundation (OISF).
This engine is not intended to just replace or emulate the existing tools in
the industry, but will bring new ideas and technologies to the field.
OISF is part of and funded by the Department of Homeland Security's Directorate
for Science and Technology HOST program (Homeland Open Security Technology),
by the Navy's Space and Naval Warfare Systems Command (SPAWAR), as well as
through the very generous support of the members of the OISF Consortium.
More information about the Consortium is available, as well as a list of our
current Consortium Members.
xjobs reads job descriptions line by line and executes them in parallel. It
limits the number of parallel executing jobs and starts new jobs when jobs
finish. Therefore, it combines the arguments from every input line with the
utility and arguments given on the command line. If no utility is given as an
argument to xjobs, then the first argument on every job line will be used as
utility. To execute utility xjobs searches the directories given in the PATH
environment variable and uses the first file found in these directories.
xjobs is most useful on multi-processor/core machines when one needs to execute
several time consuming command several that could possibly be run in parallel.
With xjobs this can be achieved easily, and it is possible to limit the load of
the machine to a useful value. It works similar to xargs, but starts several
processes simultaneously and gives only one line of arguments to each utility
call.
An SNMP based command line network printer management tool.
Modern network printers are quite easily managable across a network.
However, until now, the only tools that make use of these capabilities
are the vendor supplied products such as Web JetAdmin by HP, Marknet by
Lexmark, Centreview by Xerox or PhaserLink by Tektronix. The problem is
that all of these tools are fundamentally GUI based applications and
there is no way to incorporate their functionality into scripts. This
program is designed to be called from scripts to find things out about
printers.
Information you can gather about printers with npadmin:
Model and vendor, Location and contact information,
Network configuration, Memory and disk usage, Max and min papersize,
Engine speed, Duplexer installed, Printer status, Printer languages,
Marker technology, Page count, Minimum margins,
Size, capacity and level of paper trays, Toner levels, Alert conditions,
Resolution, Display information, Cover pages on/off.
CD/DVD mastering tool for the gnome desktop. It has been designed to be
simple and easy to use.
Features:
Data CD/DVD:
- supports edition of discs contents
- can burn data CD/DVD on the fly
- supports multisession
- supports joliet extension
- can write the image to the hard drive
Audio CD:
- write CD-TEXT information (automatically found thanks to gstreamer)
- supports the edition of CD-TEXT information
- can burn audio CD on the fly
- can use all audio files handled by Gstreamer local installation
- can search for audio files inside dropped folders
CD/DVD copy:
- can copy a CD/DVD to the hard drive
- can copy DVD and CD on the fly
- supports single-session data DVD
- supports any kind of CD
LDAP Account Manager (LAM) is a webfrontend for managing entries (e.g. users,
groups, DHCP settings) stored in an LDAP directory. LAM was designed to make
LDAP management as easy as possible for the user. It abstracts from the
technical details of LDAP and allows persons without technical background to
manage LDAP entries. If needed, power users may still directly edit LDAP entries
via the integrated LDAP browser.
Features:
- management of various account types: Unix, Samba 3, Kolab 2, Scalix,
phpGroupWare, Zarafa, DHCP, SSH keys, group of names and much more
- profiles for account creation
- account creation via file upload
- automatic creation/deletion of home directories
- setting file system quotas
- PDF output for all accounts
- editor for organizational units
- schema browser
- LDAP browser
- multiple configuration files
- multi-language support
- support for LDAP+SSL/TLS
A maintainance utility for sgml catalog files.
mkcatalog maintains sgml "catalog" files.
usage: mkcatalog [-pq] install|deinstall dtd-subdirectory [catalog-filename]
options:
-p preserve old catalog file.
-q silent mode
commands(required):
install set DTD configuration to catalog files.
deinstall usset DTD configuration from catalog files.
required arguments:
dtd-subdirectory DTD sub-directory.
(root sgml direcotry is ${PREFIX}/share/sgml.)
optional arguments:
catalog-filename DTD catalog filename.
for example:
# mkcatalog install html/4.0
This commands do the following actions:
1. Add `CATALOG "html/catalog"' to ${PREFIX}/share/sgml/catalog.
2. Add `CATALOG "4.0/catalog"'
to ${PREFIX}/share/sgml/html/catalog.
# mkcatalog install docbook/4.1 docbook41.cat
This commands do the following actions:
1. Add `CATALOG "docbook/catalog"' to ${PREFIX}/share/sgml/catalog.
2. Add `CATALOG "4.1/docbook41.cat"'
to ${PREFIX}/share/sgml/docbook/catalog.
# mkcatalog deinstall docbook/4.1 docbook41.cat
This commands do the following actions:
1. Delete `CATALOG "4.1/docbook41.cat"'
from ${PREFIX}/share/sgml/docbook/catalog.
2. Delete `CATALOG "docbook/catalog"'
from ${PREFIX}/share/sgml/catalog.
CSS::Minifier removes unnecessary whitespace from CSS. The primary requirement
developing this module is to not break working stylesheets: if working CSS is in
input then working CSS is output. The Mac/Internet Explorer comment hack will be
minimized but not stripped and so will continue to function.
This module understands space, horizontal tab, new line, carriage return, and
form feed characters to be whitespace. Any other characters that may be
considered whitespace are not minimized. These other characters include
paragraph separator and vertical tab.
For static CSS files, it is recommended that you minify during the build stage
of web deployment. If you minify on-the-fly then it might be a good idea to
cache the minified file. Minifying static files on-the-fly repeatedly is
wasteful.