Free message board signatures software for linux

Acquire is a computer version of the classic board game.
The goal of the game is to make the most profit by buying stocks in companies that form, merge and grow as tiles are placed on the game board.
This program is a text-based version of the game and should be playable on any system with a C++ compiler.
Enhancements:
- The main improvement of this release is that the bug causing the game to crash at the end was fixed, so you can now see who won.
- There were some other small bugfixes and changes.

Mail::DKIM::Signature module encapsulates a DKIM signature header.

CONSTRUCTORS

new() - create a new signature from parameters

my $signature = new Mail::DKIM::Signature(
[ Algorithm => "rsa-sha1", ]
[ Signature => $base64, ]
[ Method => "relaxed", ]
[ Domain => "example.org", ]
[ Headers => "from:subject:date:message-id", ]
[ Query => "dns", ]
[ Selector => "alpha", ]
);
parse() - create a new signature from a DKIM-Signature header
my $sig = parse Mail::DKIM::Signature(
"DKIM-Signature: a=rsa-sha1; b=yluiJ7+0=; c=relaxed"
);

Constructs a signature by parsing the provided DKIM-Signature header content. You do not have to include the header name (i.e. "DKIM-Signature:") but it is recommended, so the header name can be preserved and returned the same way in as_string().

Note: The input to this constructor is in the same format as the output of the as_string method.

METHODS

algorithm() - get or set the algorithm (a=) field

The algorithm used to generate the signature. Should be either "rsa-sha1", an RSA-signed SHA-1 digest, or "rsa-sha256", an RSA-signed SHA-256 digest.
See also hash_algorithm().

as_string() - the signature header as a string
print $signature->as_string . "n";

outputs

DKIM-Signature: a=rsa-sha1; b=yluiJ7+0=; c=relaxed

As shown in the example, the as_string method can be used to generate the DKIM-Signature that gets prepended to a signed message.
as_string_without_data() - signature without the signature data

print $signature->as_string_without_data . "n";

outputs

DKIM-Signature: a=rsa-sha1; b=; c=relaxed

This is similar to the as_string() method, but it always excludes the "data" part. This is used by the DKIM canonicalization methods, which require incorporating this part of the signature into the signed message.

body_count() - get or set the body count (l=) field

my $i = $signature->body_count;

Informs the verifier of the number of bytes in the body of the email included in the cryptographic hash, starting from 0 immediately following the CRLF preceding the body. Also known as the l= tag.

When creating a signature, this tag may be either omitted, or set after the selected canonicalization system has received the entire message body (but before it canonicalizes the DKIM-Signature).

body_hash() - get or set the body hash (bh=) field

my $bh = $signature->body_hash;

The hash of the body part of the message. Whitespace is ignored in this value. This tag is required.

When accessing this value, whitespace is stripped from the tag for you.

canonicalization() - get or set the canonicalization (c=) field

$signature->canonicalization("relaxed", "simple");

($header, $body) = $signature->canonicalization;

Message canonicalization (default is "simple/simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.
In scalar context, this returns header/body canonicalization as a single string separated by /. In list context, it returns a two element array, containing first the header canonicalization, then the body.

domain() - get or set the domain (d=) field

my $d = $signature->domain; # gets the domain value
$signature->domain("example.org"); # sets the domain value

The domain of the signing entity, as specified in the signature. This is the domain that will be queried for the public key.

expiration() - get or set the signature expiration (x=) field

Signature expiration (default is undef, meaning no expiration). The signature expiration, if defined, is an unsigned integer identifying the standard Unix seconds-since-1970 time when the signature will expire.

get_public_key() - fetches the public key referenced by this signature

my $pubkey = $signature->get_public_key;

Public key to fetch is determined by the protocol, selector, and domain fields.

hash_algorithm() - access the hash algorithm specified in this signature

my $hash = $signature->hash_algorithm;

Determines what hashing algorithm is used as part of the signatures specified algorithm.

For algorithm "rsa-sha1", the hash algorithm is "sha1". Likewise, for algorithm "rsa-sha256", the hash algorithm is "sha256". If the algorithm is not recognized, undef is returned.

headerlist() - get or set the signed header fields (h=) field

$signature->headerlist("a:b:c");

my $headerlist = $signature->headerlist;

my @headers = $signature->headerlist;

Signed header fields. A colon-separated list of header field names that identify the header fields presented to the signing algorithm.

In scalar context, the list of header field names will be returned as a single string, with the names joined together with colons. In list context, the header field names will be returned as a list.

identity() - get or set the signing identity (i=) field

my $i = $signature->identity;

Identity of the user or agent on behalf of which this message is signed. The identity has an optional local part, followed by "@", then a domain name. The domain name should be the same as or a subdomain of the domain returned by the domain method.

Ideally, the identity should match the identity listed in the From: header, or the Sender: header, but this is not required to have a valid signature. Whether the identity used is "authorized" to sign for the given message is not determined here.

method() - get or set the canonicalization (c=) field

Message canonicalization (default is "simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.

protocol() - get or set the query methods (q=) field

A colon-separated list of query methods used to retrieve the public key (default is "dns"). Each query method is of the form "type[/options]", where the syntax and semantics of the options depends on the type.

selector() - get or set the selector (s=) field

The selector subdivides the namespace for the "d=" (domain) tag.

data() - get or set the signature data (b=) field

my $base64 = $signature->data;
$signature->data($base64);

The signature data. Whitespace is automatically stripped from the returned value. The data is Base64-encoded.

prettify() - alters the signature to look "nicer" as an email header

$signature->prettify;

This method may alter the signature in a way that breaks signatures, so it should be done ONLY when the signature is being generated, BEFORE being fed to the canonicalization algorithm.

prettify_safe() - same as prettify() but only touches the b= part

$signature->prettify_safe;

This method will not break the signature, but it only affects the b= part of the signature.

timestamp() - get or set the signature timestamp (t=) field

Signature timestamp (default is undef, meaning unknown creation time). This is the time that the signature was created. The value is an unsigned integer identifying the number of standard Unix seconds-since-1970.

version() - get or set the DKIM specification version (v=) field

This is the version of the DKIM specification that applies to this signature record.

Message::Style is a Perl module to perform stylistic analysis of messages.

SYNOPSIS

use Message::Style;

my $score=Message::Style::score(@article);
# or
my $score=Message::Style::score(@article);

This Perl library does an analysis of a RFC2822 format message (typically email messages or Usenet posts) and produces a score that, in the authors opinion, gives a good indication as to whether the poster is a fsckwit, and therefore whether their message should be ignored.

File::Signature is a Perl module to detect changes to a files content or attributes.

SYNOPSIS

use File::Signature;
my $sig = File::Signature->new(/some/file);

# If you have a stringified signature stored in $string
# you can create a File::Signature object from it.
my $sig = File::Signature->new_from_string($string);

if (my $err = $sig->error) {
warn $err, "n";
}
# You can use a signature object to re-check the same file.
if ( $sig->is_same() ) { print "Ok. The signature is the same.n" }
if ( $sig->changed() ) { print "Uh Oh! The signature has changed.n" }

my @digests = $sig->old_and_new(digest);
my @inodes = $sig->old_and_new(ino);
my @modes = $sig->old_and_new(mode);
my @uid = $sig->old_and_new(uid);
my @gid = $sig->old_and_new(gid);
my @mtime = $sig->old_and_new(mtime);

# A slightly more worthwhile use...
my @fields = $sig->changed();
for my $field (@fields) {
printf "$field was: %s but changed to %s.n",
$sig->old_and_new($field);
}

ABSTRACT

This perl library uses perl5 objects to assist in determining whether a files contents or attributes have changed. It maintains several pieces of information about the file: a digest (currently only MD5 is supported), its inode number, its mode, the uid of its owner, the gid of its group owner, and its last modification time. A File::Signature object is closely associated with a single pathname. It provides a way to compare the state of a file over different points in time; it isnt useful for comparing different files.

This module provides a way to monitor files for changes. It implements an object oriented interface to file "signatures." In the case of this module, a signature includes an MD5 digest (other digests may be added later), the files size, its inode number, its mode, its owners uid, its groups gid, and its mtime. This information is associated with a file by the files "pathname." The pathname is considered to be the files unique identifier. In reality, a file may have more than one pathname, but this module doesnt recognize that.

It will simply treat two differing pathnames as two different files, even if they refer to the same file. As this module checks whether a file changes over time, a minimal use of it would include the time when the signature was created and a different time when the signature is regenerated and compared with the previous one. The amount of time between these checks is arbitrary. This module makes it easy to save a signature object and then load it and check for consistency at a later time, whether seconds or years have passed.

Monkey Boards is a small, fast, and efficient message board systems to enable smaller Web sites to build virtual online communities where users post and reply to messages.

Compared with other projects, this defining purpose Monkey Boards much more clearer and to-the-point.

The project is different from other similar solutions mainly because it uses an SQLite database, whereas the majority currently require a MySQL server to be running somewhere. It will output clean and valid XHTML pages with external CSS stylesheets.

Orion Secure Message Gateway (OrionSMG) is a secure message gateway for transporting ebXML, SOAP, and custom message formats. It complies with the OASIS ebXML 2.0 specification, and can act in both intermediary and processing MHS roles to provide end-to-end reliable messaging.
Orion Secure Message Gateway software runs natively on Linux, OS X, and Windows with ODBC/PostgreSQL database support.
Enhancements:
- OrionSvnInfo.h now in correct directory.
- Old documentation temporarily added.
- Minimal README.txt file added.

eboard is a chess board interface for playing and studying chess.

eboard is a graphical client to internet chess servers, an interface to computer chess engines and a tool for visualization, analysis and study of chess games.

Mail::Message::Convert is a Perl module for conversions between message types.

INHERITANCE

Mail::Message::Convert
is a Mail::Reporter

Mail::Message::Convert is extended by
Mail::Message::Convert::Html
Mail::Message::Convert::HtmlFormatPS
Mail::Message::Convert::HtmlFormatText
Mail::Message::Convert::MailInternet
Mail::Message::Convert::MimeEntity
Mail::Message::Convert::TextAutoformat

SYNOPSIS

Available methods are very converter-specific.

This class is the base for various message (and message parts) converters. When the conversion does not change the contents of the body, most of the converters will return the source object. In any case, an Mail::Message::Body is returned with the conversion applied but as much of the other meta data stored in the source body unchanged.

In most cases, converters are created by Mail::Message when they are needed; have a look at the encode and decoded methods on message objects.