Free specifying software for linux

PHP Directory Listing is a simple PHP script that will do just that, list a directory.
To use PHP Directory Listing just unpack into the directory you want listed, or unpack somewhere else and symlink index.php, index.css and the .icons directory.
Version restrictions:
- Im currently using the Tango Projects icon library, but theres quite a few of the MIME icons missing. If youre good at graphics and help them out, youre supporting much more projects than just this little script!
- The gray box around a mime type icon / thumbnail does not always have the same size.
- There is no good way of specifying the number of columns when the script is used through symlinks
- Actually, the columns should adjust their number automatically, which they dont
Enhancements:
- This release merges Andreas Aronssons changes.
- ASP files are now supported, and directories have a slash appended.

KeyNote is a simple and flexible trust-management system designed to work well for applications.

Trust management, introduced in the PolicyMaker system [BFL96], is a unified approach to specifying and interpreting security policies, credentials, and relationships; it allows direct authorization of security-critical actions. A trust-management system provides standard, general-purpose mechanisms for specifying application security policies and credentials. Trust-management credentials describe a specific delegation of trust and subsume the role of public key certificates; unlike traditional certificates, which bind keys to names, credentials can bind keys directly to the authorization to perform specific tasks.

A language for describing `actions, which are operations with security consequences that are to be controlled by the system.
A mechanism for identifying `principals, which are entities that can be authorized to perform actions.
A language for specifying application `policies, which govern the actions that principals are authorized to perform.
A language for specifying `credentials, which allow principals to delegate authorization to other principals.
A `compliance checker, which provides a service to applications for determining how an action requested by principals should be handled, given a policy and a set of credentials.

The trust-management approach has a number of advantages over other mechanisms for specifying and controlling authorization, especially when security policy is distributed over a network or is otherwise decentralized.

Trust management unifies the notions of security policy, credentials, access control, and authorization. An application that uses a trust- management system can simply ask the compliance checker whether a requested action should be allowed. Furthermore, policies and credentials are written in standard languages that are shared by all trust-managed applications; the security configuration mechanism for one application carries exactly the same syntactic and semantic structure as that of another, even when the semantics of the applications themselves are quite different.

Trust-management policies are easy to distribute across networks, helping to avoid the need for application-specific distributed policy configuration mechanisms, access control lists, and certificate parsers and interpreters.

For a general discussion of the use of trust management in distributed system security, see [Bla99].

KeyNote is a simple and flexible trust-management system designed to work well for a variety of large- and small- scale Internet-based applications. It provides a single, unified language for both local policies and credentials. KeyNote policies and credentials, called `assertions, contain predicates that describe the trusted actions permitted by the holders of specific public keys. KeyNote assertions are essentially small, highly-structured programs. A signed assertion, which can be sent over an untrusted network, is also called a `credential assertion. Credential assertions, which also serve the role of certificates, have the same syntax as policy assertions but are also signed by the principal delegating the trust.

In KeyNote:

Actions are specified as a collection of name-value pairs.
Principal names can be any convenient string and can directly represent cryptographic public keys.
The same language is used for both policies and credentials.
The policy and credential language is concise, highly expressive, human readable and writable, and compatible with a variety of storage and transmission media, including electronic mail.
The compliance checker returns an application-configured `policy compliance value that describes how a request should be handled by the application. Policy compliance values are always positively derived from policy and credentials, facilitating analysis of KeyNote-based systems.
Compliance checking is efficient enough for high-performance and real-time applications.

This document describes the KeyNote policy and credential assertion language, the structure of KeyNote action descriptions, and the KeyNote model of computation.

DBIx::Wrapper::Config Perl module allows the use of a configuration file in XML specifying information required to connect to databases using DBIx::Wrapper.

This way, your database connection specifications can be kept in one place.

Each "db" element specifies a key/name for the database connection, which should be passed as the $db_key argument to connect() in order to connect to that database.

The "db" elements children specify the dsn, authentication, and attribute information. dbi:mysql:database=test_db;host=example.com;port=3306 test_user test_pwd test_user test_pwd connect($db_key, $conf_path, %dbix_wrapper_attrs) Return a DBIx::Wrapper object connected to the database specified by $db_key in the file at $conf_path.

%dbix_wrapper_attrs is the optional 5th argument to DBIx::Wrappers connect() method, specifying handlers, etc. The file specified by $conf_path should be in the format specified in the DESCRIPTION section of this document.

Installation:

perl Makefile.PL
make
make test
make install

fs-check program checks filesystem sizes to see if they are getting too full. It uses a configuration file that specifies the filesystems to check, email contacts, trigger thresholds (percentage or amount used/unused), and a report program to run.
Also included in the package is such a sample report program, fs-report. It shows things like the largest files, the newest files, and core files. It can be run from cron or as a daemon.
Both programs have a number of command-line options.
Enhancements:
- Various bugs have been fixed.
- This package will now build outside of the source tree.
- An option for specifying the default configuration file was added.
- Perl 5.006 or greater is now required.

CORBA::omniORB::mapping is a CORBA mapping for Perl.

This document describes a mapping of the CORBA system into Perl. It sticks most closely to the mapping in the CORBA::MICO, L:< CORBA:omniORB >, and CORBA::ORBit modules; however, some reference is also made to the mappings implemented in COPE and ILU/Perl.

These systems exhibit a wide diversity in the details of their object adaptors. CORBA::MICO and CORBA::omniORB implement most of the POA specification fashion, including all activation modes. COPE implements a version of the BOA, and ILU has its own object native adaptor different from the BOA, though it implements some of the BOA specificatoin through compatibility classes.

For this reason, this document largely avoids specifying object adaptor details, except for a few specific notes. Details about the manner in which the ORB is initialized and interface definitions are loaded are also not specified here. Conformant implementations may either use conventional stubs or access interface definitions in a dynamic manner. (For instance, by loading them from an Interface Repository.)
The design goal for this mapping was to allow applications to access the complete CORBA specification from Perl in a convenient and concise manner, even when this requires sacrificing some amount of speed or convenience for the ORB implementor.

MAILBOX wmnotify is a "DockApp" application, running under WindowMaker, to periodically check a POP3 or IMAP4 email account for new messages. It also supports SSL encryption.

When new messages are detected, the mailbox image is animated to give a visual indication that new mail has arrived. Additionnally, if desired, a sound can be produced from a WAV or AU audio file, or from the console bell.

For simplicity reasons, wmnotify doesnt support multiple POP3 accounts. But by starting a new instance of wmnotify and specifying an alternate configuration file on the command line, you can effectively check multiple POP3 accounts.

GIMP ASCII Load/Save Plugin package is a set of identical plugins Save 2 ASCII, and ASCII 2 Image, which make saving (loading) images to (from) ASCII text.

GIMP ASCII Load/Save Plugin is very useful if you are using GNU Octave & GIMP together for Image processing. These plugins are distributed under GNU GPL, which you may modify and redistribute.

ASCII 2

Functionally this script tries to create an Image from a text-file that had been processed with the Octave or anything else.

LIMITATIONS: No support for multiple-layers or alpha.

USAGE: Choose a given ASCII file which you want to visualize, and with a knowledge of its column size & row size type those in and select gray/color option, then press ok and wait. You must see your matrix visualized on GIMP.

Save 2 ASCII

Functionally this script tries to save the Image into a text-file for processing with the Octave or anything else.

LIMITATIONS; Cannot save layers.

USAGE: Choose an image, and select if you want it saved as a ASCII file in gray/color mode (1bit-per-pixel(bpp) or 3bpp), and press ok. A new file will be created in your $HOME directory by default, or the directory where you started GIMP from. You can optionally override this by specifying the full path in filename field.

CSVObjects is a free and open sourced Java based framework for transparently parsing and unmarshalling Comma Separated Value (CSV) files and records into Plain Old Java Objects without the need to code the parsing logic manually.

Instead, the parsing library relies on declarative mapping of CSV fields and data types to Java Bean attributes, via a mapping XML file. This is similar to the manner in which Hibernate provides relational table mapping for Java Beans.

The Framework is built upon Stephen Ostermillers excellent CSV reader/parser classes.

Also, the framework provides convenience Xdoclet support for specifying the CSV to Java mapping in the Java source code itself by using Javadoc markup, thereby reducing the burden on the developer to manually maintain separate configuration files.

Installation:

If you have downloaded the binary file release, then you need to include the
CSVObjects- .jar file in your projects library or classpath, ensure that the dependency libraries are also present in the classpath, and thats it!