Free software cracking software for linux

Software::Packager::Rpm is a suite of Perl modules providing a common interface for
the creation of platform specific software installation packagers.

add_item()
my %object_data = (
SOURCE => /source/file1,
TYPE => file,
KIND => doc,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

This method overrides the add_item method in Software::Packager. It adds the ability to add extra features used by RPM for each object in the package.

For more details see the documentation in: Software::Packager Software::Packager::Object::Rpm

program_name()
$packager->program_name(SoftwarePackager);
my $program_name = $packager->program_name();

This method is used to set the name of the program that the package is installing. This may in should be the same as the package name but that is not required. It must not contain spaces or a dash "-" and must be all on one line.

version()
$packager->version(1.2.3.4.5.6);
my $version = $packager->version();

This method sets the version for the package to the passed value. The version passed cannot contain a dash "-" or spaces and must be on one line.

release()

This method sets the release version for the package. The release is the number of times the package has been recreated. If the release is not set then a default of 1 is used. It cannot contain spaces, a dash or new lines.

copyright()

This method sets the copyright type for the package. This should be the name of the copyright

source()

This method sets the source location for the package. This should be the URL for the source package used to create this package.

architecture()
$packager->architecture("sparc");
my $arch = $packager->architecture();

This method sets the architecture for the package to the passed value. If no argument is passed then the current architecture is returned. This is the output "from uname -p"

package_name()
my $name = $packager->package_name();

This method returns the name of the package that will be created.

short_description()

$packager->short_description("This is a short description.");
my $description = $packager->short_description();

The short description is just that a short description of the program. It must be all on one line.

description()
$packager->description("This is the description.");
my $description = $packager->description();

The description method sets the package description to the passed value. If no arguments are passed the package description is returned.

The discription can be of any length. It will be formatted by RPM in the following way:
If a line starts with a space it will be printed verbatim.

A blank line signifies a new paragraph.

All other lines will be assumed to be part of a paragraph and will be formatted by RPM.

package()

This method creates the package and returns true if it is successful else it returns undef

Software::Packager::Svr4 is the Software::Packager extension for System VR4 packages.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(svr4);

This module is used to create software packages in a format suitable for installation with pkgadd.

FUNCTIONS

new()

This method creates and returns a new Software::Packager::SVR4 object.

add_item()

$packager->add_item(%object_data);

Adds a new object (file, link, etc) to the package.

package()

$packager->package();

Create the package.

info

This method returns a hash that is filled with the necessary information for a pkginfo file that conforms to the SYSV format.

package_name()

Define the package name.

program_name()

This is used to specify the full package name.

The program name must be less that 256 charaters.

For more details see the pkginfo(4) man page.

architecture()

The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package.

The maximum length of a token is 16 charaters.

A token should be in the format "instruction set"."platform group" where:

instruction set is in the format of `uname -p`

platform group is in the format of `uname -m`

If the architecture is not set then the current instruction set is used.

For more details see the pkginfo(4) man page.

version()

This method is used to check the format of the version and return it in the format required for SVR4.

The version must be 256 charaters or less.

The first charater cannot be a left parenthesis.

The recommended format is an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.

install_dir()

$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir;

This method sets the base directory for the software to be installed. The installation directory must start with a "/".

compatible_version()

$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);

my $compatible_version = $packager->compatible_version();

This method sets the compatible versions file for the software to be installed.

space()

$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);

my $space = $packager->space();

This method sets the space file for the software to be installed.
request_script()

$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();

This method sets the space file for the software to be installed.

Aircrack-ng is a set of tools for auditing wireless networks.
- airodump: 802.11 packet capture program
- aireplay: 802.11 packet injection program
- aircrack: static WEP and WPA-PSK key cracker
- airdecap: decrypts WEP/WPA capture files
Aircrack-ng is the next generation of aircrack with lots of new features.
How do I crack a static WEP key ?
The basic idea is to capture as much encrypted traffic as possible using airodump. Each WEP data packet has an associated 3-byte Initialization Vector (IV): after a sufficient number of data packets have been collected, run aircrack on the resulting capture file. aircrack will then perform a set of statistical attacks developped by a talented hacker named KoreK.
How do I know my WEP key is correct ?
There are two authentication modes for WEP:
Open-System Authentication: this is the default mode. All clients are accepted by the AP, and the key is never checked: association is always granted. However if your key is incorrect you wont be able to receive or send packets (because decryption will fail), so DHCP, ping etc. will timeout.
Shared-Key Authentication: the client has to encrypt a challenge before association is granted by the AP. This mode is flawed and leads to keystream recovery, so its never enabled by default.
In summary, just because you seem to have successfully connected to the access point doesnt mean your WEP key is correct ! To check your WEP key, try to decrypt a capture file with the airdecap program.
How many IVs are required to crack WEP ?
WEP cracking is not an exact science. The number of required IVs depends on the WEP key length, and it also depends on your luck. Usually, 40-bit WEP can be cracked with 300.000 IVs, and 104-bit WEP can be cracked with 1.000.000 IVs; if youre out of luck you may need two million IVs, or more.
Theres no way to know the WEP key length: this information is kept hidden and never announced, either in management or data packets; as a consequence, airodump can not report the WEP key length. Thus, it is recommended to run aircrack twice: when you have 250.000 IVs, start aircrack with "-n 64" to crack 40-bit WEP. Then if the key isnt found, restart aircrack (without the -n option) to crack 104-bit WEP.
Enhancements:
- This release adds an ACX injection patch, and updates the rtl8187 patch for 2.6.21.
- It fixes madwifi-ng detection with airmon-ng.
- It fixes 2 bugs in aircrack-ng related to WPA cracking.
- It fixes an old Debian bug (#417388).
- It fixes the use of wlanng, and fixes IP address writing in the CSV file with airodump-ng.
- It fixes a bug in the GUI for Windows and adds a PTW option.

Software::Packager::Solaris is the Software::Packager extension for Solaris 2.5.1 and above.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(solaris);

This module is used to create software packages in a format suitable for installation with pkgadd. The process of creating packages is baised upon the document Application Packaging Developers Guide. Which can be found at http://docs.sun.com/ab2/@LegacyPageView?toc=SUNWab_42_2:/safedir/space3/coll1/SUNWasup/toc/PACKINSTALL:Contents;bt=Application+Packaging+Developer%27s+Guide;ps=ps/SUNWab_42_2/PACKINSTALL/Contents

FUNCTIONS

new()

This method creates and returns a new Software::Packager::Solaris object.

add_item()
$packager->add_item(%object_data);

This method overrides the add_item function in the Software::Packager module.

This method adds a new object to the package.

package()

$packager->packager(); This method overrides the base API in Software::Packager, it controls the process if package creation.

package_name()

This method is used to specify the abbreviated package name.

Sun say: (Application Packaging Developers Guide. Page 32) A valid package abbreviation must the criteria defined below:

It must start with a letter. Additional charaters may be alphanumeric and can be the two special charaters + and -.

It must be nine or fewer charaters.

Reserved names are install, new, and all.

For more details see the pkginfo(4) man page.

program_name()

This is used to specify the full package name.

The program name must be less that 256 charaters.

For more details see the pkginfo(4) man page.

architecture()

The architecture must be a comma seperated list of alphanumeric tokens that indicate the architecture associated with the package. The maximum length of a token is 16 charaters. A token should be in the format "instruction set"."platform group" where: instruction set is the output of `uname -p` platform group is the output of `uname -m`
If the architecture is not set then the current instruction set is used.

For more details see the pkginfo(4) man page.

version()

This method is used to check the format of the version and return it in the format required for Solaris.

The version must be 256 charaters or less.

The first charater cannot be a left parenthesis.

The recommended format isi an arbitrary string of numbers in Dewey-decimal format. For more datails see the pkginfo(4) man page.

install_dir()
$packager->install_dir(/usr/local);
my $base_dir = $packager->install_dir();

This method sets the base directory for the software to be installed. The installation directory must start with a "/".

compatible_version()

$packager->compatible_version(/some/path/file);
or
$packager->compatible_version($compver_stored_in_string);

my $compatible_version = $packager->compatible_version();

This method sets the compatible versions file for the software to be installed.

space()

$packager->space(/some/path/file);
or
$packager->space($space_data_stored_in_string);
my $space = $packager->space();

This method sets the space file for the software to be installed.

request_script()

$packager->request_script(/some/path/file);
or
$packager->request_script($request_script_stored_in_string);
my $request_script = $packager->request_script();

This method sets the space file for the software to be installed.

Software Engineering Environment (SEE) is frame for manufacturing information. It is implemented in sevlet and xml, and is used by the web-browser.
Software Engineering Environment (SEE) attempts to provide the information manufacturing platform for software development.
SEE is a free project, that is the author will provide all of its source code at the same time.
It runs in any servlet environment (The author merely verified in the Win and Linux environment), not using any special technique and needs no auxiliary program.
All of its data are saved in XML files, and need not database. (The future release will support the option of saving data, so that the user can select some free database, such as mysql, or commercial database to improve SEE speed.)
This means that the user can run SEE without any money. (Tomcat is a free servlet environment.)
User uses all SEE functions with the web-browser. So information sharing is very convenient.
SEE supports Simplified Chinese, Traditional Chinese, and English now.( It will support any language if someone will translate.) User can switch to interfaces in different language at any time when SEE is running. And user can add language translations which will work at once.
The main body of SEE is a frame for information manufacturing. All information included in it can be costumed dynamically and all changes will get into effect immediately. This means that the user can modify or add her/his own information structure as will at any time.
SEE provides various predefined selections for information attributes, which correspond various predefined information manufacturing patterns. The user can focus on the information description when costuming information definition, and the system will implement the functions automatically. This is the core of SEE. Most functions of SEE are in this model.
The default information definition of SEE is the result that the author understands what is the Software Engineering.
Although the target of SEE is helping for software development, actually, user can use it to design any type information, such as book registering, personnel lists, and financial reports etc.
The speed of SEE is not bad. Reading and writing 20000 records needs no more than 1 second. At present, the sorting speed is 9 seconds for 5000 records. (The testing platform is 1.8G CPU and 256M memory)
Enhancements:
- The data interface to prepare supporting databases.
- The databases are not supported in this release.
- A new interface style "Beautiful Flowers".
- These flowers are photoed in parks in this year by the author.
- The author likes the honeybee who holds a flower in its mouth very much. It is the first cartoon figure by the author. It will appear when you save wrong data. :)
- The function of "Personal Message".
- User can only query the messages sent by and sent to herself/himself. And user can only remove the messages sent to herself/himself.
- After a user read a message sent to her/him, SEE will mark it as "have_read" automatically.
- The number of new arrived messages will be shown in the interface.
- The data privileges management
- When user "Remove All" or "Modify All", the "base conditions" will be checked at first. That is user can only do what she/he can do.
- The Password fields values can not be visited, except when the user, who owns the "Import" privilege to current data, exports the data.
- All the data structures of ACL tables are changed! Their keywords become the "Title". This will permit user define better ACL.
- And the "condition" in the ACL tables are implemented completely. Now any "SEE conditions" is valid.
- Snapshot for image file
- When list the data, a snapshot will be shown for the image files type, which may end with jpg/jpeg/gif/png.
- Data sorting concerned with langauges.
- Thus when sorting data in Chinese, the result is Chinese result.
- General users can not visit the "User" table! Then they can not fill in many data!
- This is a fatal bug! This means all former releases can not be used actually!
- Now all ACL tables are redesigned.
- When a new user is added without password, SEE will add some password itself! Then this new user can never login!
- This is another fatal bug!
- In the last English release, which is 0.06, the ACL data are in Chinese!
- So the English users can not use SEE at all~~
- This is still a fatal bug!
- The "Risk Items" in the table "Deviation Handling" is wrong defined.
- This will cause an error information when user clicks the "Select" button.
- The values of Password fields can be visited when query or export.
- Although the values are meaningless encoded codes, they are still security thread.
- When some quota marks in the key values, pages will report errors and the function buttons, such as Modify and Remove, can not act!
- This is because quota is also an element of web page.
- When the interface language changes, the language in audit records changes too!
- This is not permitted. Language of all data is determined when SEE is installed and can not change with interface!

Software Render Library is an Open Source software implementation of a polygon-based renderer (like your graphics card).
Main features:
- Transform vertices (from world to screen coordinates)
- Lighting
- Apply fog
- Rasterization of points, lines and triangles
- Texturation
- Z-Buffers
- Alpha blending
- Output to several pixel formats
Installation:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
If youre using GNU `make or any other `make program that supports the `VPATH variable, you should instead create a new directory, `cd to it and type `../srlib-src/configure.
This way you can keep the source directory clean and have your sources in a directory which is not modifyable by normal users.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Type `make install to install the libraries, headers and documentation. At the moment, only static libraries are built; support for shared libraries will be provided soon.
4. You can remove the library binaries and object files from the build directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Version restrictions:
- Read or write files and file formats, like png or jpeg. Software Render Library expects pixel data in a suitable format in a memory buffer.
- Read and process file formats describing a scene. Software Render Library only takes simple commands like "render this list of triangles" or "apply this certain light".
- Tesselation, i.e. dividing more abstract elements like cubes or spheres into lines and triangles.

aircrack is a 802.11 sniffer and WEP/WPA key cracker.
It consists of: airodump (an 802.11 packet capture program), aireplay (an 802.11 packet injection program), aircrack (static WEP and WPA-PSK cracking), and airdecap (decrypts WEP/WPA capture files).
Enhancements:
- airodump: show probing clients as "not associated"
- airodump: dont substract the noise level unless madwifi
- airodump: fixed channel hopping with old orinoco
- airmon.sh: added detection of the zd1211 driver