Free developmental psychology software for linux

DryDock is a Web publishing application that implements a development/production Web site pipeline. It codifies an approval process that forces users to approve all Web site changes before they go into production.

Sometimes, on a web server, system administrators are often ill-equipped to determine who created the document, why its being served, how long its been publicly viewable, and how its changed over time.

To police our own website, we create DryDock. DryDock is a web publishing application that governs the replication of content from a developmental, or staging web tree to a production web tree (ideally placed on a second server). DryDock codifies a formal approval process that forces management to approve all web site changes before those changes are put into production. Users never interact directly with the production web tree; DryDock updates it on their behalf.

Secret::Simple are secure secrets in configurations and code.

SYNOPSIS

# OOP style
my $ss = Secret::Simple->new();
my $ciphertext = $ss->encrypt($plaintext);
my $plaintext = $ss->decrypt($ciphertext);

# procedural style
my $ciphertext = ssencrypt($plaintext);
my $plaintext = ssdecrypt($ciphertext);

This module implements a straightforward interface for encrypting and decrypting secret information such as user IDs and passwords (e.g. database connection or remote account credentials). Secret::Simple can also be used on a limited basis to protect arbitrary data. By default the ciphertext returned is Base 64 encoded so as to be easily embedded within configurations or scripts.

A command-line utility called sstool is included to facilitate easy manipulation of cipher and plaintext snippets. The encryption mechanism utilizes the strong AES algorithm, so any weaknesses in Secret::Simple predominantly lie in how keys are protected. A balance must be struck between key accessibility, key protection, and overall complexity. The calling code can supply a key, series of keys, key files, or a combination. If no key information is explicitly passed, the module will attempt to use the OS users private SSH DSA key file by default if it exists.

The major goal of this module is to be as secure as possible while being simple and convenient enough to encourage its use. Psychology does factor in: simple is a very important consideration. If the security methods are too onerous or complicated to use, many sysadmins or developers may simply use plaintext (no protection other that OS file permissions) or simple ciphers like rot13. The security of the Secret::Simple method is not perfect, but it does represent a significant improvement over commonly-used nonsecure methods of embedding credentials and other secrets in Perl configurations and scripts. If used appropriately, Secret::Simple can greatly improve application and configuration security. Even so, care must always be taken to protect files and file permissions.