signature files
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 10112
Test::Signature 1.06
Test::Signature is a Perl module to automate SIGNATURE testing. more>>
Test::Signature is a Perl module to automate SIGNATURE testing.
SYNOPSIS
# This is actually the t/00signature.t
# file from this distribution.
use Test::More tests => 1;
use Test::Signature;
signature_ok();
ABSTRACT
Test::Signature verifies that the Module::Signature generated signature of a module is correct.
Module::Signature allows you to verify that a distribution has not been tampered with. Test::Signature lets that be tested as part of the distributions test suite.
By default, if Module::Signature is not installed then it will just say so and not fail the test. That can be overridden though.
IMPORTANT: This is not a substitute for the users verifying the distribution themselves. By the time this module is run, the users will have already run your Makefile.PL or Build.PL scripts which could have been compromised.
This module is more for ensuring youve updated your signature appropriately before distributing, and for preventing accidental errors during transmission or packaging.
<<lessSYNOPSIS
# This is actually the t/00signature.t
# file from this distribution.
use Test::More tests => 1;
use Test::Signature;
signature_ok();
ABSTRACT
Test::Signature verifies that the Module::Signature generated signature of a module is correct.
Module::Signature allows you to verify that a distribution has not been tampered with. Test::Signature lets that be tested as part of the distributions test suite.
By default, if Module::Signature is not installed then it will just say so and not fail the test. That can be overridden though.
IMPORTANT: This is not a substitute for the users verifying the distribution themselves. By the time this module is run, the users will have already run your Makefile.PL or Build.PL scripts which could have been compromised.
This module is more for ensuring youve updated your signature appropriately before distributing, and for preventing accidental errors during transmission or packaging.
Download (0.016MB)
Added: 2007-05-04 License: Perl Artistic License Price:
903 downloads
IANA /etc Files 2.20
IANA /etc Files is a tool that generates /etc/services and /etc/protocols from IANA data. more>>
IANA /etc Files installs /etc/services and /etc/protocols using data from the Internet Assigned Numbers Authority. Included are snapshots of the data from the IANA, scripts to transform that data into the needed formats, and scripts to fetch the latest data.
Installation
The installation process is flexible and friendly to unattended installation even though, due to its simplicity, it does not use Autoconf.
For basic installation run:
make
su
make install
This creates /etc/services and /etc/protocols without using internet access.
To install in a different location, use something like:
make PREFIX=/mnt/tmp install
This would create /mnt/tmp/etc/services and /mnt/tmp/etc/protocols.
For unusual installations, "make PREFIX=/foo ETC_DIR=bar install" will create /foo/bar/services and /foo/bar/protocols.
Enhancements:
- This release contains updated data from the IANA, improvements to the test function, and support for generating stripped files.
- It is the second of a series of planned changes intended to meet the needs of distributions.
<<lessInstallation
The installation process is flexible and friendly to unattended installation even though, due to its simplicity, it does not use Autoconf.
For basic installation run:
make
su
make install
This creates /etc/services and /etc/protocols without using internet access.
To install in a different location, use something like:
make PREFIX=/mnt/tmp install
This would create /mnt/tmp/etc/services and /mnt/tmp/etc/protocols.
For unusual installations, "make PREFIX=/foo ETC_DIR=bar install" will create /foo/bar/services and /foo/bar/protocols.
Enhancements:
- This release contains updated data from the IANA, improvements to the test function, and support for generating stripped files.
- It is the second of a series of planned changes intended to meet the needs of distributions.
Download (0.16MB)
Added: 2006-11-15 License: Open Software License Price:
1075 downloads
File::Signature 1.009
File::Signature is a Perl module to detect changes to a files content or attributes. more>>
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.
<<lessSYNOPSIS
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.
Download (0.008MB)
Added: 2007-04-30 License: Perl Artistic License Price:
909 downloads
Module::Signature 0.55
Module::Signature is a Perl module signature file manipulation. more>>
Module::Signature is a Perl module signature file manipulation.
SYNOPSIS
As a shell command:
% cpansign # verify an existing SIGNATURE, or
# make a new one if none exists
% cpansign sign # make signature; overwrites existing one
% cpansign -s # same thing
% cpansign verify # verify a signature
% cpansign -v # same thing
% cpansign -v --skip # ignore files in MANIFEST.SKIP
% cpansign help # display this documentation
% cpansign -h # same thing
In programs:
use Module::Signature qw(sign verify SIGNATURE_OK);
sign();
sign(overwrite => 1); # overwrites without asking
# see the CONSTANTS section below
(verify() == SIGNATURE_OK) or die "failed!";
<<lessSYNOPSIS
As a shell command:
% cpansign # verify an existing SIGNATURE, or
# make a new one if none exists
% cpansign sign # make signature; overwrites existing one
% cpansign -s # same thing
% cpansign verify # verify a signature
% cpansign -v # same thing
% cpansign -v --skip # ignore files in MANIFEST.SKIP
% cpansign help # display this documentation
% cpansign -h # same thing
In programs:
use Module::Signature qw(sign verify SIGNATURE_OK);
sign();
sign(overwrite => 1); # overwrites without asking
# see the CONSTANTS section below
(verify() == SIGNATURE_OK) or die "failed!";
Download (0.067MB)
Added: 2007-02-16 License: Perl Artistic License Price:
980 downloads
list files 0.2
list files package prints to file list of files in a given directory. more>>
list files package prints to file list of files in a given directory.
Handy if youd like to, say, tell a friend of yours what ebooks you have, and wouldnt feel like typing them all by hand.
Hope you can find it useful.
INSTALLATION
i assume youve got everything in its standard places; otherwise you probably know what to do anyway.
to install for one user
copy listFiles.desktop to ~/.kde/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
to install for all users
copy listFiles.desktop to /usr/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
Enhancements:
- added counting the number of items
- added the possibility to change the place where the listing is written to
- some minor changes to the code
<<lessHandy if youd like to, say, tell a friend of yours what ebooks you have, and wouldnt feel like typing them all by hand.
Hope you can find it useful.
INSTALLATION
i assume youve got everything in its standard places; otherwise you probably know what to do anyway.
to install for one user
copy listFiles.desktop to ~/.kde/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
to install for all users
copy listFiles.desktop to /usr/share/apps/konqueror/servicemenus
copy listFiles.sh to /usr/local/bin or elsewhere in the path
Enhancements:
- added counting the number of items
- added the possibility to change the place where the listing is written to
- some minor changes to the code
Download (0.002MB)
Added: 2007-02-13 License: GPL (GNU General Public License) Price:
581 downloads
Mail::DKIM::Signature 0.26
Mail::DKIM::Signature module encapsulates a DKIM signature header. more>>
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.
<<lessCONSTRUCTORS
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.
Download (0.046MB)
Added: 2007-07-18 License: Perl Artistic License Price:
828 downloads
Mail::DKIM::DkSignature 0.28
Mail::DKIM::DkSignature is a DomainKeys signature header. more>>
Mail::DKIM::DkSignature is a DomainKeys signature header.
CONSTRUCTORS
parse() - create a new signature from a DomainKey-Signature header
my $sig = parse Mail::DKIM::DkSignature(
"DomainKey-Signature: a=rsa-sha1; b=yluiJ7+0=; c=nofws"
);
Constructs a signature by parsing the provided DomainKey-Signature header content. You do not have to include the header name (i.e. "DomainKey-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
as_string() - the signature header as a string
print $signature->as_string . "n";
outputs
DomainKey-Signature: a=rsa-sha1; b=yluiJ7+0=; c=nofws
As shown in the example, the as_string method can be used to generate the DomainKey-Signature that gets prepended to a signed message.
algorithm() - get or set the algorithm (a=) field
The algorithm used to generate the signature. Defaults to "rsa-sha1", an RSA-signed SHA-1 digest.
canonicalization() - get or set the canonicalization (c=) field
$signature->canonicalization("nofws");
$signature->canonicalization("simple");
$method = $signature->canonicalization;
Message canonicalization (default is "simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.
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.
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.
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").
selector() - get or set the selector (s=) field
The selector subdivides the namespace for the "d=" (domain) tag.
signature() - get or set the signature data (b=) field
The signature data. Whitespace is automatically stripped from the returned value.
<<lessCONSTRUCTORS
parse() - create a new signature from a DomainKey-Signature header
my $sig = parse Mail::DKIM::DkSignature(
"DomainKey-Signature: a=rsa-sha1; b=yluiJ7+0=; c=nofws"
);
Constructs a signature by parsing the provided DomainKey-Signature header content. You do not have to include the header name (i.e. "DomainKey-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
as_string() - the signature header as a string
print $signature->as_string . "n";
outputs
DomainKey-Signature: a=rsa-sha1; b=yluiJ7+0=; c=nofws
As shown in the example, the as_string method can be used to generate the DomainKey-Signature that gets prepended to a signed message.
algorithm() - get or set the algorithm (a=) field
The algorithm used to generate the signature. Defaults to "rsa-sha1", an RSA-signed SHA-1 digest.
canonicalization() - get or set the canonicalization (c=) field
$signature->canonicalization("nofws");
$signature->canonicalization("simple");
$method = $signature->canonicalization;
Message canonicalization (default is "simple"). This informs the verifier of the type of canonicalization used to prepare the message for signing.
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.
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.
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").
selector() - get or set the selector (s=) field
The selector subdivides the namespace for the "d=" (domain) tag.
signature() - get or set the signature data (b=) field
The signature data. Whitespace is automatically stripped from the returned value.
Download (0.050MB)
Added: 2007-08-14 License: Perl Artistic License Price:
802 downloads
SigTranslator 20060205
SigTranslator is a project able to translate IDS signatures e.g. from Snort rules to Dragon rules and vice versa. more>>
SigTranslator is a project able to translate IDS signatures e.g. from Snort rules to Dragon rules and vice versa. SigTranslator can translate as well the common signatures standard (CIDSS - Common Intrusion Detection Signatures Standard).
Signature Translator is simple to use Java application which will help you to use signatures in your favourite IDS translated from other IDS .
Enhancements:
- Major code enhancements and bugfixes.
<<lessSignature Translator is simple to use Java application which will help you to use signatures in your favourite IDS translated from other IDS .
Enhancements:
- Major code enhancements and bugfixes.
Download (1.1MB)
Added: 2006-02-06 License: The Apache License Price:
1355 downloads
sign 1.0.7
sign is a file signing and signature verification utility. more>>
sign is a file signing and signature verification utility. Its main purpose is to be a simple and convenient extension to a tar/gz/bzip2 line of tools to check file integrity and authenticity. Its small and simple, it does just one thing and hopefully does it well.
I needed a tool to digitally sign a bunch of .tar.gz and to allow recepients of the files to easily check, unzip, untar and start enjoying the content as quickly and painlessly as possible.
There are OpenSSL, GnuPG, PGP and others and they are of course perfectly capable of file signing. OpenSSL is probably the most widely spread one and best suited for the role of being a universal signing utility. However the state of affairs is such that OpenSSL as an application is not really used for anything more than generating tarball MD5 hashes. The other packages are plain big and complex for a simple task of file integrity checking. Its like getting a professional sound editing suite instead of a dead-simple .mp3 player. The larger crypto-packages also tend to lack modularity in a sense that to get file signing working I would need to configure a handful of core, but otherwise unrelated settings first. Besides if I am not going to use anything but a signing code, the rest will be sitting there collecting dust, creating untrivial shared libraries dependencies and a general feeling of a wasted disk space.
First of all, sign is a file processing tool, it reads from the files (including stdin) and writes to the files (including stdout). It can be used to attach signatures to the files or to verify and/or strip them.
Between signing and verifying latter will account for a bulk of usage. When checking the signature, sign will check for both integrity and authenticity of the file. An integrity check is done by validating SHA-1 hash embedded into the signature, and an authenticity is ensured by checking signers credentials against a trusted list.
sign adopts OpenSSH-style authentication model, where the trust hierarchy is flat (no certificates), an authentication is done with public keys and the list of trusted keys is grown gradually on as-needed basis.
Every trusted key is associated with a file name prefix called the title. The key can be trusted for signing files, whose name start with keys title. The same key may be associated with more than one title, but not vice versa.
The signature is appended at the end of the file and it carries three bits of information - the title, the public key of the signer and the hash of all preceeding data encrypted with signers private key. The verification is performed as follows:
The filename is checked to start with a title
The hash is decrypted using the public key
The hash is compared to the locally computed value (this ensures integrity)
The title is looked up locally; if its known and associated public key is the same as in the signature, the file is deemed authentic.
Otherwise if the title is known, but the key is different, the file is considered to be signed by untrusted, impersonating party and the check fails.
And lastly, if the title is unknown, the authenticity of the file cannot be established. The user is provided with public key fingerprint, which should be manually authenticated. Then the title and the key are added to the trusted list; and subsequent signatures from the this signer for this particular title will be cleared automatically.
In order to sign files, the signing keypair must first be generated. The keypair is maintained on per-user basis and can be created by running sign with a special command-line flag. The signing process itself is as follows (give or take insignificant details):
Run the filename through a list of owned titles and find the best match. Alternately accept explicit title from the user using one of the command-line flags.
Attach the title, attach public signing key
Compute the hash, encrypt it with private signing key
Attach encrypted hash.
For details on command-line syntax and other operating parameters, please refer to a man page; an online version is here.
<<lessI needed a tool to digitally sign a bunch of .tar.gz and to allow recepients of the files to easily check, unzip, untar and start enjoying the content as quickly and painlessly as possible.
There are OpenSSL, GnuPG, PGP and others and they are of course perfectly capable of file signing. OpenSSL is probably the most widely spread one and best suited for the role of being a universal signing utility. However the state of affairs is such that OpenSSL as an application is not really used for anything more than generating tarball MD5 hashes. The other packages are plain big and complex for a simple task of file integrity checking. Its like getting a professional sound editing suite instead of a dead-simple .mp3 player. The larger crypto-packages also tend to lack modularity in a sense that to get file signing working I would need to configure a handful of core, but otherwise unrelated settings first. Besides if I am not going to use anything but a signing code, the rest will be sitting there collecting dust, creating untrivial shared libraries dependencies and a general feeling of a wasted disk space.
First of all, sign is a file processing tool, it reads from the files (including stdin) and writes to the files (including stdout). It can be used to attach signatures to the files or to verify and/or strip them.
Between signing and verifying latter will account for a bulk of usage. When checking the signature, sign will check for both integrity and authenticity of the file. An integrity check is done by validating SHA-1 hash embedded into the signature, and an authenticity is ensured by checking signers credentials against a trusted list.
sign adopts OpenSSH-style authentication model, where the trust hierarchy is flat (no certificates), an authentication is done with public keys and the list of trusted keys is grown gradually on as-needed basis.
Every trusted key is associated with a file name prefix called the title. The key can be trusted for signing files, whose name start with keys title. The same key may be associated with more than one title, but not vice versa.
The signature is appended at the end of the file and it carries three bits of information - the title, the public key of the signer and the hash of all preceeding data encrypted with signers private key. The verification is performed as follows:
The filename is checked to start with a title
The hash is decrypted using the public key
The hash is compared to the locally computed value (this ensures integrity)
The title is looked up locally; if its known and associated public key is the same as in the signature, the file is deemed authentic.
Otherwise if the title is known, but the key is different, the file is considered to be signed by untrusted, impersonating party and the check fails.
And lastly, if the title is unknown, the authenticity of the file cannot be established. The user is provided with public key fingerprint, which should be manually authenticated. Then the title and the key are added to the trusted list; and subsequent signatures from the this signer for this particular title will be cleared automatically.
In order to sign files, the signing keypair must first be generated. The keypair is maintained on per-user basis and can be created by running sign with a special command-line flag. The signing process itself is as follows (give or take insignificant details):
Run the filename through a list of owned titles and find the best match. Alternately accept explicit title from the user using one of the command-line flags.
Attach the title, attach public signing key
Compute the hash, encrypt it with private signing key
Attach encrypted hash.
For details on command-line syntax and other operating parameters, please refer to a man page; an online version is here.
Download (0.027MB)
Added: 2006-07-07 License: BSD License Price:
1208 downloads
XML Digital Signature Tool 0.0.2.20070320
XML Digital Signature Tool is a Firefox extension that can process Digital Signature in XML documents. more>>
XML Digital Signature Tool is a Firefox extension that can process Digital Signature in XML documents (as per W3C standard for XML signature: http://www.w3.org/Signature/).
The XML digital signature tool is built on top of Apache XML security C library (version 1.3), called XSEC (http://xml.apache.org/security/c/index.html). We made no changes to XSEC source code. We just compiled the source with NSS option to provide cryptographic functionality using browsers CERT DB. The recompiled XSEC library is packaged with the XPI file for this extension.
In addition, this tool provides an XPCOM based API for wrapping C++ based Apache XML security library. Our XPCOM IDL based API allows any Firefox based extension to access XSEC library using JavaScript and C++. This tool also provides XUL based GUI for specifying various parameters for signing XML files and verifying signed XML files.
The Apache XSEC c-library uses the Apache XML projects (http://xml.apache.org/) Xerces-C XML Parser and Xalan-C XSLT processor. The latter is used for processing XPath and XSLT transforms. This tool does not include the DLL or shared library for Xercrs-C or Xalan-C. You have to download and install Apache XERCES for C (v1.3.0) and XALAN tools for C (v.1.10) before you can run this extension. The path for shared libraries or DLL of XERCES and XALAN must be in the LD_LIBRARY_PATH (for Unix) or PATH (for windows).
In addition, the tool provides following features:
- ability to generate Self-Issued SAML Token (both v1.1 and v2.0) using the RSA/DSA keys in the certificate DB. (http://docs.oasis-open.org/security/saml/v2.0/) The SAML Token generation is implemented using a XPCOM based componenet.
- XPCOM based API for UUID generation. The XPCOM implementation resues the UUID generation source code in the RFC4122 (http://www.ietf.org/rfc/rfc4122.txt). We have adpated the source code for Mozilla NSS based digest and added string based UUID API.
Note: This tool only works on Windows and Linux OSes.
<<lessThe XML digital signature tool is built on top of Apache XML security C library (version 1.3), called XSEC (http://xml.apache.org/security/c/index.html). We made no changes to XSEC source code. We just compiled the source with NSS option to provide cryptographic functionality using browsers CERT DB. The recompiled XSEC library is packaged with the XPI file for this extension.
In addition, this tool provides an XPCOM based API for wrapping C++ based Apache XML security library. Our XPCOM IDL based API allows any Firefox based extension to access XSEC library using JavaScript and C++. This tool also provides XUL based GUI for specifying various parameters for signing XML files and verifying signed XML files.
The Apache XSEC c-library uses the Apache XML projects (http://xml.apache.org/) Xerces-C XML Parser and Xalan-C XSLT processor. The latter is used for processing XPath and XSLT transforms. This tool does not include the DLL or shared library for Xercrs-C or Xalan-C. You have to download and install Apache XERCES for C (v1.3.0) and XALAN tools for C (v.1.10) before you can run this extension. The path for shared libraries or DLL of XERCES and XALAN must be in the LD_LIBRARY_PATH (for Unix) or PATH (for windows).
In addition, the tool provides following features:
- ability to generate Self-Issued SAML Token (both v1.1 and v2.0) using the RSA/DSA keys in the certificate DB. (http://docs.oasis-open.org/security/saml/v2.0/) The SAML Token generation is implemented using a XPCOM based componenet.
- XPCOM based API for UUID generation. The XPCOM implementation resues the UUID generation source code in the RFC4122 (http://www.ietf.org/rfc/rfc4122.txt). We have adpated the source code for Mozilla NSS based digest and added string based UUID API.
Note: This tool only works on Windows and Linux OSes.
Download (0.85MB)
Added: 2007-07-26 License: MPL (Mozilla Public License) Price:
826 downloads
seccure 0.3
seccure toolset implements a selection of asymmetric algorithms based on elliptic curve cryptography (ECC). more>>
seccure toolset implements a selection of asymmetric algorithms based on elliptic curve cryptography (ECC). In particular it offers public key encryption / decryption and signature generation / verification.
ECC schemes offer a much better key size to security ratio than classical systems (RSA, DSA). Keys are short enough to make direct specification of keys on the command line possible (sometimes this is more convenient than the management of PGP-like key rings).
seccure builds on this feature and therefore is the tool of choice whenever lightweight asymmetric cryptography -- independent of key servers, revocation certificates, the Web of Trust or even configuration files -- is required.
Where can I download seccure?
seccure is GPL software. First download seccure from the following link. Then, after having made sure that libgcrypt is properly installed, run make and make install as usual.
How is seccure used?
First we give an example for key generation:
$ seccure-key
Assuming curve p160.
Enter private key: my private key
The public key is: 8W;>i^H0qi|J&$coR5MFpR*Vn
Then we do some public key encryption / decryption:
$ seccure-encrypt -o private.msg 8W;>i^H0qi|J&$coR5MFpR*Vn
Assuming MAC length of 80 bits.
Go ahead and type your message ...
This is a very very secret message!
^D
$ seccure-decrypt -i private.msg
Assuming MAC length of 80 bits.
Assuming curve p160.
Enter private key: my private key
This is a very very secret message!
Integrity check successful, message unforged!
At last we try out the signature generation / verification:
$ seccure-sign
Assuming curve p160.
Enter private key: my private key
Go ahead and type your message ...
This message will be signed
^D
Signature: !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
$ seccure-verify 8W;>i^H0qi|J&$coR5MFpR*Vn !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
Go ahead and type your message ...
This message will be signed
^D
Signature successfully verified!
Enhancements:
- This release adds signcryption and inline signatures.
<<lessECC schemes offer a much better key size to security ratio than classical systems (RSA, DSA). Keys are short enough to make direct specification of keys on the command line possible (sometimes this is more convenient than the management of PGP-like key rings).
seccure builds on this feature and therefore is the tool of choice whenever lightweight asymmetric cryptography -- independent of key servers, revocation certificates, the Web of Trust or even configuration files -- is required.
Where can I download seccure?
seccure is GPL software. First download seccure from the following link. Then, after having made sure that libgcrypt is properly installed, run make and make install as usual.
How is seccure used?
First we give an example for key generation:
$ seccure-key
Assuming curve p160.
Enter private key: my private key
The public key is: 8W;>i^H0qi|J&$coR5MFpR*Vn
Then we do some public key encryption / decryption:
$ seccure-encrypt -o private.msg 8W;>i^H0qi|J&$coR5MFpR*Vn
Assuming MAC length of 80 bits.
Go ahead and type your message ...
This is a very very secret message!
^D
$ seccure-decrypt -i private.msg
Assuming MAC length of 80 bits.
Assuming curve p160.
Enter private key: my private key
This is a very very secret message!
Integrity check successful, message unforged!
At last we try out the signature generation / verification:
$ seccure-sign
Assuming curve p160.
Enter private key: my private key
Go ahead and type your message ...
This message will be signed
^D
Signature: !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
$ seccure-verify 8W;>i^H0qi|J&$coR5MFpR*Vn !JI1%Luh6mu:@)S3wS.go(u1z,b.NhXIUI)/p@$*ONA+)+G}}_
Go ahead and type your message ...
This message will be signed
^D
Signature successfully verified!
Enhancements:
- This release adds signcryption and inline signatures.
Download (0.025MB)
Added: 2006-08-17 License: GPL (GNU General Public License) Price:
1164 downloads
Java EDF files viewer 2.0.1
Java EDF files viewer is a multi-platform EDF file viewer. more>>
Java EDF files viewer is a multiplatform (Linux and Windows) EDF (European Data Format) files viewer written in Java and developped with Borland JbuilderX Foundation.
Usage
1. You need the Java software installed.
2. To execute the viewer
- type in command line: java -jar jEDF.jar
Enhancements:
- This release has hypnogram scoring, montage creation, spectral analysis, EEG event scoring, and a bilingual interface (English/French).
<<lessUsage
1. You need the Java software installed.
2. To execute the viewer
- type in command line: java -jar jEDF.jar
Enhancements:
- This release has hypnogram scoring, montage creation, spectral analysis, EEG event scoring, and a bilingual interface (English/French).
Download (0.22MB)
Added: 2006-11-05 License: GPL (GNU General Public License) Price:
1128 downloads
X-files 1.43
X-Files is a graphical file management program. more>>
X-Files is a graphical file management program for Unix/X-Window environment. It was inspired by the Amiga program DirWork.
This application differs slightly from the main stream file managers in that it has always only one window. On top (or bottom) of the window you have ActionbuttonsTM -area. Other main areas are the two directory listings for file related actions. You can use quick pop-up menu for basic operations. File extensions can be configured to launch any program you desire for that file.
The appearance and functionality can be fully configured according to your taste using the built-in editors.
Tested on: Intel Linux, DEC Alpha, SGI, HP-UX, Solaris
(Should work on any Unix-machine running Tcl/Tk.)
<<lessThis application differs slightly from the main stream file managers in that it has always only one window. On top (or bottom) of the window you have ActionbuttonsTM -area. Other main areas are the two directory listings for file related actions. You can use quick pop-up menu for basic operations. File extensions can be configured to launch any program you desire for that file.
The appearance and functionality can be fully configured according to your taste using the built-in editors.
Tested on: Intel Linux, DEC Alpha, SGI, HP-UX, Solaris
(Should work on any Unix-machine running Tcl/Tk.)
Download (0.15MB)
Added: 2005-04-29 License: GPL (GNU General Public License) Price:
1649 downloads
QArchive.org web files checker 1.0
QArchive.org web files checker is an extension which allows people to check web files for any malware. more>>
QArchive.org web files checker is an extension which allows people to check web files for any malware.
The add-on allowing people to check web files for any malware (viruses, trojans, worms, adware, spyware and other unwanted things) inclusions. Install this plug-in to your browser, reload it. Then click the web file link by right mouse button and choose a "Check files with QArchive.org".
Then follow web site instructions. The usual way: your file will be enqueued. Refresh the report page to get completete antivirus report. That will show you all web files part checking and a summary as well. If you are a web master you can you the useful feature.
Taking the code of received report and placed it on your web site you can inform people about a concrete file safety. The web forums code version exists as well.
<<lessThe add-on allowing people to check web files for any malware (viruses, trojans, worms, adware, spyware and other unwanted things) inclusions. Install this plug-in to your browser, reload it. Then click the web file link by right mouse button and choose a "Check files with QArchive.org".
Then follow web site instructions. The usual way: your file will be enqueued. Refresh the report page to get completete antivirus report. That will show you all web files part checking and a summary as well. If you are a web master you can you the useful feature.
Taking the code of received report and placed it on your web site you can inform people about a concrete file safety. The web forums code version exists as well.
Download (0.005MB)
Added: 2007-03-30 License: MPL (Mozilla Public License) Price:
977 downloads
Journaled Files LIBrary 0.3.5-0.0.0
Journaled Files LIBrary allows you to perform atomic transactions on standard system files. more>>
Journaled Files LIBrary allows you to perform atomic transactions on standard files. It supplies functions to commit and rollback (back-out) changes.
Journaled files are normal files that you can browse and parse with standard tools. A journal (log) stores all transactional info.
Enhancements:
- tutorial available (HTML, PDF, SGML/docbook)
- FAQ was converted from TXT file to HTML, PDF, SGML/docbook
- documentation can be produced directly by make command ("make html", "make pdf", "make dist")
- fixed to "UTF-8" the XML output encoding
<<lessJournaled files are normal files that you can browse and parse with standard tools. A journal (log) stores all transactional info.
Enhancements:
- tutorial available (HTML, PDF, SGML/docbook)
- FAQ was converted from TXT file to HTML, PDF, SGML/docbook
- documentation can be produced directly by make command ("make html", "make pdf", "make dist")
- fixed to "UTF-8" the XML output encoding
Download (0.94MB)
Added: 2005-09-19 License: LGPL (GNU Lesser General Public License) Price:
835 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above signature files search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
