Free verifies software for linux

OpenXAdES provides a legally binding digitally signed documents into life.

OpenXAdES enables people to work with legally-binding digital signatures (primarily giving and verifying them).

Legislation often defines a set of requirements that legal digital signature technologies and infrastructures must be compliant with, and OpenXAdES aims at meeting many, if not all, such requirements from different legislations.

Nift is graphical front-end for footprinting tools and methods already freely avaliable. Its purpose is to aid system administrators in securing their websites by allowing them to quickly check their network.
Main features:
- Option to ignore hosts already found on the network when pingscanning (less garbage to be found in logs)
- Optional Use of wingates whenever possible. (User provided and will also use wingates found withen the network)
- Spoofed Decoys to throw off AIDS, also verifies decoy addys provided are alive to avoid syn flooding the host. Will change ttl of the source I.P. when decoys are used in case the host uses packet source accounting. (keeps your I.P. from being singled out)
- Can either trust banners to determine possible exploits, or test the exploits. The first will be safer, but will likely generate many false positives.
Enhancements:
- Removed Netcat support (no longer needed)
- Added SOCK_STREAM client to do banner grabbing and Enumeration
- Removed Queso OS Detection (nmap is more reliable and upto-date)
- Basic service enumeration code added
- More Data catches and colorized output fixes
- Added Progress bar
- disabled logging feature until 1.0 beta (need to re-design the GUI to fit it in)
- Combined traceroute and ICMP Discovery scan types
- Began work on Firewall ruleset detection code

TiVo File Decoder software converts a .TiVo file (produced by the TiVoToGo functionality on recent TiVo software releases) to a normal MPEG file.
This has the same functionality as using TiVos supplied DirectShow DLL on Windows with a tool such as DirectShowDump, but is portable to different architectures and operating systems, and runs on the command line using files or pipes.
The conversion still requires the valid MAK of the TiVo which recorded the file, so it cannot be used to circumvent their protection, simply to provide the same level of access as is already available on Windows.
Usage: ./objects.dir/tivodecode [--help] [--verbose|-v] [--no-verify|-n] {--mak|-m} mak [{--out|-o} outfile] < tivofile >
--mak, -m media access key (required)
--out, -o output file (default stdout)
--verbose, -v verbose
--no-verify, -n do not verify MAK while decoding
--help print this help and exit
Enhancements:
- Fixes a merge error in tivodecoder.h which included several headers before including tdconfig.h, causing some needed defines not to be defined in those headers

Text::NSP::Measures::3D is a Perl module that provides basic framework for building measure of association for trigrams.

This module can be used as a foundation for building 3-dimensional measures of association that can then be used by statistic.pl. In particular this module provides methods that give convenient access to 3-d (i.e., trigram) frequency counts as created by count.pl, as well as some degree of error handling that verifies the data.

Basic Usage

use Text::NSP::Measures::3D::MI::ll;

$ll_value = calculateStatistic( n111=>10,
n1pp=>40,
np1p=>45,
npp1=>42,
n11p=>20,
n1p1=>23,
np11=>21,
nppp=>100);

if( ($errorCode = getErrorCode()))
{
print STDERR $erroCode." - ".getErrorMessage()."n";
}
else
{
print getStatisticName."value for bigram is ".$ll_value."n";
}

The methods in this module retrieve observed trigram frequency counts and marginal totals, and also compute expected values. They also provide support for error checking of the output produced by count.pl. These methods are used in all the trigram (3d) measure modules provided in NSP. If you are writing your own 3d measure, you can use these methods as well.

Funkee is a cross-platform scripting host built on top of the Java Virtual Machine and the Groovy scripting language. Funkee is geared toward people who want to test code snippets, and toward those who need to write and run scripts quickly.
As of release 0.5, Funkee adds support for BSF -- the Bean Scripting Framework. It has been tested with Jython and Rhino (1.5R3), bringing the number of supported scripting languages to at least three, including Python, JavaScript/ECMAScript, and Groovy.
To add support for your favorite BSF-friendly language, just drop the languages JAR file into your .funkee directory, restart the application, and start writing scripts!
Funkee still favors Groovy, in that Java and Groovy can be used to define classes that can be referenced by any of the supported scripting languages.
Funkee now supports XML-RPC Web Services as both a client and a server. For security reasons, the server component doesnt start without user intervention.
XML-RPC server scripts only need to be dropped into the "xmlrpc" subdirectory off the users funkee home directory in order to be picked up. Example code will be added to this page Real Soon Now.
In order to create a client, scripts currently need to invoke:
funkee.getRPC("http://some.host.name:8080/")
after which they can use the remote service as though it was a local object.
When executed, Funkee displays a smiley face in the upper-right corner of your screen. In the background, it also creates a subdirectory named ".funkee" in your home directory, and unpacks a default set of scripts. (MS Windows users: your home directory is probably under "C:Documents and Settings") You can then invoke Groovy scripts in your .Funkee directory by using the smiley.
To execute Funkee, you need the Java Runtime Environment 1.4 or better. Funkee has been tested against JRE 1.4.2 and JRE 1.5.0 on MS Windows and Linux.
To launch Funkee on MS Windows, double-click the Funkee.jar file. On UNIX, type "java -jar funkee.jar" at the command shell.
Main features:
- Its cooler.
- JAR files dropped into the .Funkee directory are automatically read and made available to scripts at startup.
- Funkee keeps an internal cache of compiled Groovy scripts and classes, which it verifies against the scripts in the .funkee directory. When a Groovy script needs to be recompiled, it gets done transparently at runtime (this includes Groovy objects!).
- Funkee now supports a LOT more scripting languages than just Groovy.
Groovy scripts in Funkee are invoked by events. This means that the behavior of the application is completely configurable by the end user. The names of the scripts, the events that trigger them, and the value of the param variable that gets passed in are as follows:
sys_drop.groovy
param: java.awt.datatransfer.Transferable
Invoked when the user drops something on the smiley.
sys_hyperlink.groovy
param: javax.swing.event.HyperlinkEvent
Invoked when the user clicks a hyperlink in the speech window (after a sayHTML() command.) This is a good script to customize shortly after installing -- usually youll want to shovel the URL from the event to your preferred web browser.
sys_mouseclicked.groovy
sys_mousepressed.groovy
sys_mousereleased.groovy
sys_mouseentered.groovy
sys_mouseexited.groovy
sys_mousepopup.groovy
param: java.awt.event.MouseEvent
Invoked when the user makes the corresponding gesture with the mouse over the smiley.
sys_mousewheelmoved.groovy
param: java.awt.event.MouseWheelEvent
Invoked when the user moves the mouse wheel over the smiley.
Enhancements:
- The UI was completely rewritten and is now based on JRCF.
- Both text and graphical targets are now provided for script outputs.