twins
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 19
KDM-Twins 0.2
KDM-Twins is a very nice KDM login screen featurinf the Twins KDM wallpaper. more>>
KDM-Twins is a very nice KDM login screen featurinf the Twins KDM wallpaper.
<<less Download (MB)
Added: 2007-03-08 License: GPL (GNU General Public License) Price:
962 downloads
Twin Distress 1.1.0
Twin Distress project is a puzzle game where you remove all blocks of the same color from the screen. more>>
Twin Distress project is a puzzle game where you remove all blocks of the same color from the screen.
Two blocks are removed at a time, and must be of the same color. After completing a level, you will be rewarded with a bonus point for every tick left on the clock.
For each level thereafter, the time to complete the the level will be shorter.
Enhancements:
- updated the help screen with all of the new features in the game
- forgot to add gravity for when blocks are put back on the screen
- created add_gravity_effect_for_blocks_put_back() & modified wrong_move_penalty()
- added gravity to the game
- added another bonus scoring option to the game when a player doesnt make a wrong move in the level
- completed the ability for the blocks to randomize in Very Hard & Insane skill modes
- more..
<<lessTwo blocks are removed at a time, and must be of the same color. After completing a level, you will be rewarded with a bonus point for every tick left on the clock.
For each level thereafter, the time to complete the the level will be shorter.
Enhancements:
- updated the help screen with all of the new features in the game
- forgot to add gravity for when blocks are put back on the screen
- created add_gravity_effect_for_blocks_put_back() & modified wrong_move_penalty()
- added gravity to the game
- added another bonus scoring option to the game when a player doesnt make a wrong move in the level
- completed the ability for the blocks to randomize in Very Hard & Insane skill modes
- more..
Download (MB)
Added: 2006-11-22 License: GPL (GNU General Public License) Price:
1068 downloads
MTASC 1.11
MTASC (Motion-Twin ActionScript2 Compiler) is an ActionScript2 cross-platform compiler. more>>
MTASC is the first ActionScript 2 Open Source free compiler.
MTASC project can compile large number of .as class files in a very short time and generate directly the corresponding SWF bytecode without relying on Macromedia Flash or other tools.
You can download it now and please read the comparison between MTASC and Macromedia compiler that is sold with Flash. If its your first time using MTASC, please read how to install and use MTASC.
INSTALL
Theses install notes are for windows user unfamiliar with commandline tools usage.
First download the MTASC package corresponding to your system and install/unzip somewhere on your computer. Then add the path of the installed executable to your PATH environment variable (see http://www.chem.gla.ac.uk/~louis/software/faq/q1.html if you dont kwnow how to do).
For example if youve installed into c:program filesmtasc you might add c:progra~1mtasc to your PATH. Now the executable is accessible everywhere. You can then write a compile.bat file containing the following text :
mtasc.exe YourFiles.as... -swf YourProject.swf
pause
Put the compile.bat file with your source files and run it when you want to compile.
USAGE
MTASC is a commandline compiler, it can then be better integrated into [Your favorite editor] by configuring it to compile .as files with MTASC. The general usage of mtasc tool is : mtasc (your .as class files) -swf (you project swf). Please note that if you have two classes Point and Line with Line.as using Point for its code, you dont need to ask MTASC to compile Point.as when compiling Line.as since it will do it automatically for you. Then if you want to include the minimal set of classes needed by your program to run, you can simply compile using mtasc Main.as where Main.as is your "main" class, the entry point of your program (if you have any).
Now that you know how to call MTASC, lets have a look at how it works : MTASC takes the SWF file specified with the -swf flag, compile all .as specified files, and update the SWF file by replacing all classes that are present inside it by the newly compiled classes. To use MTASC instead of Macromedia Flash Compiler, its simple. Open your project and publish it normally (for example project.swf). Now run MTASC using the published SWF as input : mtasc (your as files) -swf project.swf. This will compile your classes and update the SWF that you can use for your website. Please note that MTASC add the compiled classes to the SWF in replacement of ALL classes compiled by Flash.
If you have an error such as class not found, file not found, or class name mistake, you should use the -cp flag in order to add a ClassPath to MTASC (that means a directory where it will look for .as files). For example if your classes are in the /code directory, do not call mtasc code/Hello.as because it will look for the class code.Hello (with package code), but call instead mtasc -cp code Hello.as.
Additional arguments are the following :
-swf file : specify input SWF which contains assets.
-cp path : add a directory path to the ClassPath : this is the list of directories that MTASC will use to look for .as files. You can use several times -cp to add several directories.
-main : will automaticaly call static function main once all classes are registered.
-header width:height:fps:bgcolor : does not load a SWF, instead create a new one containing only compiled code and using provided header informations. bgcolor is optional and should be 6 digits hexadecimal value.
-mx : use precompiled MX classes (see section on V2 components below).
Some other arguments, for advanced users :
-version n : specify SWF version : 6 to generate Player 6r89 compatible SWF or 8 to access Flash8 features.
-v : activate verbose mode, printing some additional informations about compiling process.
-out file : change output swf file.
-msvc : use Microsoft Visual Studio errors style formating install of Java style (for file names and lines number).
-strict : will use strict compilation mode which require that all variables are explicitely typed.
-exclude file : exclude code generation of classes listed in specified file (format is one full class path per line).
-trace function : specify a custom trace function. (see Trace Facilities), or no disable all the traces.
-keep : keep AS2 classes compiled by MCC into the SWF (this could cause some classes to be present two times if also compiled with MTASC).
-frame f : will export AS2 classes into target frame of swf.
-pack path : compile all the files contained in specified package - not recursively (eg to compile files in c:flashcodemyapp do mtasc -cp c:flashcode -pack my/app).
-group : will merge classes into one single clip (this will reduce SWF size but might cause some problems if youre using -keep or -mx).
Enhancements:
- Several small fixes.
- Strongly typed arrays have been added.
<<lessMTASC project can compile large number of .as class files in a very short time and generate directly the corresponding SWF bytecode without relying on Macromedia Flash or other tools.
You can download it now and please read the comparison between MTASC and Macromedia compiler that is sold with Flash. If its your first time using MTASC, please read how to install and use MTASC.
INSTALL
Theses install notes are for windows user unfamiliar with commandline tools usage.
First download the MTASC package corresponding to your system and install/unzip somewhere on your computer. Then add the path of the installed executable to your PATH environment variable (see http://www.chem.gla.ac.uk/~louis/software/faq/q1.html if you dont kwnow how to do).
For example if youve installed into c:program filesmtasc you might add c:progra~1mtasc to your PATH. Now the executable is accessible everywhere. You can then write a compile.bat file containing the following text :
mtasc.exe YourFiles.as... -swf YourProject.swf
pause
Put the compile.bat file with your source files and run it when you want to compile.
USAGE
MTASC is a commandline compiler, it can then be better integrated into [Your favorite editor] by configuring it to compile .as files with MTASC. The general usage of mtasc tool is : mtasc (your .as class files) -swf (you project swf). Please note that if you have two classes Point and Line with Line.as using Point for its code, you dont need to ask MTASC to compile Point.as when compiling Line.as since it will do it automatically for you. Then if you want to include the minimal set of classes needed by your program to run, you can simply compile using mtasc Main.as where Main.as is your "main" class, the entry point of your program (if you have any).
Now that you know how to call MTASC, lets have a look at how it works : MTASC takes the SWF file specified with the -swf flag, compile all .as specified files, and update the SWF file by replacing all classes that are present inside it by the newly compiled classes. To use MTASC instead of Macromedia Flash Compiler, its simple. Open your project and publish it normally (for example project.swf). Now run MTASC using the published SWF as input : mtasc (your as files) -swf project.swf. This will compile your classes and update the SWF that you can use for your website. Please note that MTASC add the compiled classes to the SWF in replacement of ALL classes compiled by Flash.
If you have an error such as class not found, file not found, or class name mistake, you should use the -cp flag in order to add a ClassPath to MTASC (that means a directory where it will look for .as files). For example if your classes are in the /code directory, do not call mtasc code/Hello.as because it will look for the class code.Hello (with package code), but call instead mtasc -cp code Hello.as.
Additional arguments are the following :
-swf file : specify input SWF which contains assets.
-cp path : add a directory path to the ClassPath : this is the list of directories that MTASC will use to look for .as files. You can use several times -cp to add several directories.
-main : will automaticaly call static function main once all classes are registered.
-header width:height:fps:bgcolor : does not load a SWF, instead create a new one containing only compiled code and using provided header informations. bgcolor is optional and should be 6 digits hexadecimal value.
-mx : use precompiled MX classes (see section on V2 components below).
Some other arguments, for advanced users :
-version n : specify SWF version : 6 to generate Player 6r89 compatible SWF or 8 to access Flash8 features.
-v : activate verbose mode, printing some additional informations about compiling process.
-out file : change output swf file.
-msvc : use Microsoft Visual Studio errors style formating install of Java style (for file names and lines number).
-strict : will use strict compilation mode which require that all variables are explicitely typed.
-exclude file : exclude code generation of classes listed in specified file (format is one full class path per line).
-trace function : specify a custom trace function. (see Trace Facilities), or no disable all the traces.
-keep : keep AS2 classes compiled by MCC into the SWF (this could cause some classes to be present two times if also compiled with MTASC).
-frame f : will export AS2 classes into target frame of swf.
-pack path : compile all the files contained in specified package - not recursively (eg to compile files in c:flashcodemyapp do mtasc -cp c:flashcode -pack my/app).
-group : will merge classes into one single clip (this will reduce SWF size but might cause some problems if youre using -keep or -mx).
Enhancements:
- Several small fixes.
- Strongly typed arrays have been added.
Download (0.29MB)
Added: 2005-12-23 License: GPL (GNU General Public License) Price:
1403 downloads
The Revisionist 0.02b
The Revisionist is a tool for extracting and indexing hidden metadata. more>>
The Revisionist is a tool for extracting and indexing hidden metadata (such as deleted or modified text) from large collections of MS Word files.
It can operate whole Web sites or SMB or NFS directories. The Revisionist project is handy for pen-testing, or it can be used just to spot embarrassing secrets.
My primary goal is to provide pen-testers and content administrators with a handy tool to detect hidden data in all documents available at a specific location (be it a locally mounted network share, a HTTP site, or whatnot), and easily review it all.
Right now, the tool only detects and indexes deleted text in documents with "change tracking" enabled, and can also index usernames and hardware addresses embedded in documents (to facilitate external assessment of company structure); future versions should be able to recover other goodies, too.
Usage:
To run the tool against a local directory, a mounted SMB or NFS directory, or such, simply issue the following command (after doing make, that is):
./therev @/path/to/directory
After the tool completes, you should be able to view master.html in current directory using your favourite browser (Lynx, Netscape, etc). Cached copies of documents would be placed in subdirectories named document.XXXXXX, where X is a random digit; hence, it is recommended to run the tool in a separate directory.
Note that you may also instruct the tool to look for specific substring and only choose those documents that contain it (strict checking, no regexp available):
./therev linux @/path/to/directory
To run the program against a specific site or top-level domain, do the following:
./therev site.com
Note that com, gov, gov.pl, www.microsoft.com are all a valid site name. The first parameter works similar to the previous case:
./therev homeland security gov
As a special bonus, when running the script against multilinguinal sites, you might want to specify a third parameter - desired language (using a two-letter code: en, pl, etc). NOTE: DO NOT USE LANGUAGE QUALIFIER UNLESS NECESSARY:
./therev linux microsoft.com en
The HTTP search mode uses Google.com to locate all matching Word documents on a specific site. For a document to be found, it must be indexable (that is, not excluded in robots.txt) and be in the first 1000 of results for a specific site. If there are more than 1000 documents at some website, consider sub-searches with keywords.
Enhancements:
- This release was fixed to work with the new Google page layout.
- Some other minor fixes were made.
<<lessIt can operate whole Web sites or SMB or NFS directories. The Revisionist project is handy for pen-testing, or it can be used just to spot embarrassing secrets.
My primary goal is to provide pen-testers and content administrators with a handy tool to detect hidden data in all documents available at a specific location (be it a locally mounted network share, a HTTP site, or whatnot), and easily review it all.
Right now, the tool only detects and indexes deleted text in documents with "change tracking" enabled, and can also index usernames and hardware addresses embedded in documents (to facilitate external assessment of company structure); future versions should be able to recover other goodies, too.
Usage:
To run the tool against a local directory, a mounted SMB or NFS directory, or such, simply issue the following command (after doing make, that is):
./therev @/path/to/directory
After the tool completes, you should be able to view master.html in current directory using your favourite browser (Lynx, Netscape, etc). Cached copies of documents would be placed in subdirectories named document.XXXXXX, where X is a random digit; hence, it is recommended to run the tool in a separate directory.
Note that you may also instruct the tool to look for specific substring and only choose those documents that contain it (strict checking, no regexp available):
./therev linux @/path/to/directory
To run the program against a specific site or top-level domain, do the following:
./therev site.com
Note that com, gov, gov.pl, www.microsoft.com are all a valid site name. The first parameter works similar to the previous case:
./therev homeland security gov
As a special bonus, when running the script against multilinguinal sites, you might want to specify a third parameter - desired language (using a two-letter code: en, pl, etc). NOTE: DO NOT USE LANGUAGE QUALIFIER UNLESS NECESSARY:
./therev linux microsoft.com en
The HTTP search mode uses Google.com to locate all matching Word documents on a specific site. For a document to be found, it must be indexable (that is, not excluded in robots.txt) and be in the first 1000 of results for a specific site. If there are more than 1000 documents at some website, consider sub-searches with keywords.
Enhancements:
- This release was fixed to work with the new Google page layout.
- Some other minor fixes were made.
Download (0.016MB)
Added: 2006-01-30 License: LGPL (GNU Lesser General Public License) Price:
1363 downloads
MinDia 0.97.3
MinDia is an application for creating, modifying, and presenting multimedia slide shows. more>>
MinDia is an application for creating, modifying, and presenting multimedia slide shows. Slide shows can contain multimedia elements like images, sounds, and text.
In addition to displaying on screen, it can control Rollei slide projectors (Rolleivision 35 twin digital P and Rolleivision twin msc 3x0 P) via a serial port.
Enhancements:
New features:
- button for switching to fullscreen modus
- automatic language detection
- help dialog improved (find text implemented)
Bugfixes and improvements:
- new directory structure for project
- small bugfixes (QString casts)
- bugfixes in playinfo dialog
- linux version only
- improved configure script (better tmake/qmake and python detection)
- bugfix in installation script (--prefix handling now correct)
- uninstall implemented
- compile problems resolved for newer Qt versions
- source and binary rpm package for SuSE 8.2 available
<<lessIn addition to displaying on screen, it can control Rollei slide projectors (Rolleivision 35 twin digital P and Rolleivision twin msc 3x0 P) via a serial port.
Enhancements:
New features:
- button for switching to fullscreen modus
- automatic language detection
- help dialog improved (find text implemented)
Bugfixes and improvements:
- new directory structure for project
- small bugfixes (QString casts)
- bugfixes in playinfo dialog
- linux version only
- improved configure script (better tmake/qmake and python detection)
- bugfix in installation script (--prefix handling now correct)
- uninstall implemented
- compile problems resolved for newer Qt versions
- source and binary rpm package for SuSE 8.2 available
Download (1.0MB)
Added: 2005-05-30 License: GPL (GNU General Public License) Price:
1608 downloads
SIPp 2.0
SIPp is a free Open Source test tool / traffic generator for the SIP protocol. more>>
SIPp is a free Open Source test tool / traffic generator for the SIP protocol. It includes a few basic SipStone user agent scenarios (UAC and UAS) and establishes and releases multiple calls with the INVITE and BYE methods.
SIPp project can also reads custom XML scenario files describing from very simple to complex call flows. It features the dynamic display of statistics about running tests (call rate, round trip delay, and message statistics), periodic CSV statistics dumps, TCP and UDP over multiple sockets or multiplexed with retransmission management and dynamically adjustable call rates.
Other advanced features include support of IPv6, TLS, SIP authentication, conditional scenarios, UDP retransmissions, error robustness (call timeout, protocol defense), call specific variable, Posix regular expression to extract and re-inject any protocol fields, custom actions (log, system command exec, call stop) on message receive, field injection from external CSV file to emulate live users.
While optimized for traffic, stress and performance testing, SIPp can be used to run one single call and exit, providing a passed/failed verdict.
Last, but not least, SIPp has a comprehensive documentation available both in HTML and PDF format.
SIPp can be used to test many real SIP equipements like SIP proxies, B2BUAs, SIP media servers, SIP/x gateways, SIP PBX, ... It is also very useful to emulate thousands of user agents calling your SIP system.
Enhancements:
- New: Statistical (conditional) branching feature. See
- http://sipp.sf.net/doc/reference.html#Randomness+in+conditional+branching.
- New: 3PCC extended mode - see
- http://sipp.sourceforge.net/doc/reference.html#3PCC+Extended
- Tool: monitor remote SIP servers through SNMP - see
- http://sipp.sourceforge.net/wiki/index.php/Getting_feedback_from_the_server
- Enh: extends the -aa option to UPDATE messages
- Enh: changes in the compilation with external libs - useful for the package
- generation system
- Enh: Allow sampling from a Weibull distribution for pause duration
- Enh: use stat_delimiter for the trace_rtt option and include number that is
- being reported.
- Enh: Add repeat_rtd keyword for repeated RTD calculations
- Enh: Handle stripping Control-M characters from multi-valued headers in
- get_header
- Enh: Update the clock_tick more frequently so that we have a higher timer and
- statistics resolution
- Enh: for option that take a time as argument - allow them to be specified using
- seconds or milliseconds
- Enh: fail when parsing a scenario that has pcap if pcap is not enabled
- Enh: print the actual location of the error log file and the error condition
- (if any) on creation
- Enh: fail when parsing a scenario that enables authentication if SSL is not
- enabled
- Enh: Makefile - include EXTRAENDLIBS keyword so that libraries can be appended
- to the list after SSL Enh: Add regexp_match argument to the receive command for
- universal catching
- Enh: remote control: increase the allowed number of control sockets.
- Enh: 3pcc extended: clean the reach of the allowed number of local twin sockets
- Enh: amelioration of statistic computing
- Enh regexp: add case_indep, occurence and start_line options for the hdr
- matching case
- Enh: Stats: Use RTDs that are precise to the microsecond in -trace_rtt, and
- improve the consistency between trace_rtt and the averages
- Enh: Only include RTDs that are actually used in the CSV output
- Enh: Allow loss percentages less than 1 and also a global command line option to
- specify that packets should be lost at a given percentage
- Fix: fix for -t un error for non-IPv6 platform like win32 - Unable to bind UDP
- socket, errno = 106 (Address family not supported by protocol)
- Fix: Do not initialize the screen library in background mode
- Fix: allow having an optional recv before a recvCmd
- Fix: Authentication: allow [fieldn] values for the [authentication] field
- Fix: updated support of short header forms
- Fix: small bug fix to the micrortt.diff which is required for the initial call
- rate to work properly
- Fix:Allow the code to compile with -Wall -Werror on Linux
- Fix: empty line was generated when [routes] keyword was used and proxy did not
- record-route
- Fix: pcap on HPUX; Fix: Simple fixes identified with valgrind
- Fix: 3pcc extended: problem when quitting
- Fix: regexp: add a warning when the specified header is not present in the
- received message
- Fix: pcap: destroy the send packets thread properly even if the sendto failed
- Fix: bug in regexp due to an incomplete commit (rev 172) - remove some debugging
- traces in message log file
- Fix: bugs on retransmission counters and on cookies for optional messages
- Fix: Incorrect branch in automatic ACK answering to unexpected >= 400 responses,
- as well as automatic CANCEL - in such cases, branch must be identical to the
- branch of the initial INVITE request
- Fix: 3pcc extended: clean up when screen exit. Fix: stop logging when the
- maximum allowed file size is reached (avoid core dump)
- Fix: incomplete Via header in automatic responses when aborting calls
- Fix: -h: -key parameter
- Fix: 3pcc/3pcc extended modes: closes twin sockets properly when twin instance
- exits, to break the poll() loop and avoid the print of empty messages
- Fix: in 3pcc/3pcc extended modes: send BYE/CANCEL before exit due to other twin
- instance exit
- Fix: force exit when pressing q twice (Q press can still be used)
- Fix: Aka authentication for synchro case, also added password len as password
- for authentication might contain char Fix: possible core dump in SDP parser
- Fix: accept up to the 5 defined RTDs (previously would only accept one less)
- Fix: Fail if there is an invalid repartition table specification - previous
- behavior was a core dump
- Fix: added -users option to the parameter table
- Fix: change option description to match timed options
- Fix: trace_err did not work in background mode
- Fix: bug when testing the presence of the 3PCC compilation flag
- Fix: bug in -r -rp option
<<lessSIPp project can also reads custom XML scenario files describing from very simple to complex call flows. It features the dynamic display of statistics about running tests (call rate, round trip delay, and message statistics), periodic CSV statistics dumps, TCP and UDP over multiple sockets or multiplexed with retransmission management and dynamically adjustable call rates.
Other advanced features include support of IPv6, TLS, SIP authentication, conditional scenarios, UDP retransmissions, error robustness (call timeout, protocol defense), call specific variable, Posix regular expression to extract and re-inject any protocol fields, custom actions (log, system command exec, call stop) on message receive, field injection from external CSV file to emulate live users.
While optimized for traffic, stress and performance testing, SIPp can be used to run one single call and exit, providing a passed/failed verdict.
Last, but not least, SIPp has a comprehensive documentation available both in HTML and PDF format.
SIPp can be used to test many real SIP equipements like SIP proxies, B2BUAs, SIP media servers, SIP/x gateways, SIP PBX, ... It is also very useful to emulate thousands of user agents calling your SIP system.
Enhancements:
- New: Statistical (conditional) branching feature. See
- http://sipp.sf.net/doc/reference.html#Randomness+in+conditional+branching.
- New: 3PCC extended mode - see
- http://sipp.sourceforge.net/doc/reference.html#3PCC+Extended
- Tool: monitor remote SIP servers through SNMP - see
- http://sipp.sourceforge.net/wiki/index.php/Getting_feedback_from_the_server
- Enh: extends the -aa option to UPDATE messages
- Enh: changes in the compilation with external libs - useful for the package
- generation system
- Enh: Allow sampling from a Weibull distribution for pause duration
- Enh: use stat_delimiter for the trace_rtt option and include number that is
- being reported.
- Enh: Add repeat_rtd keyword for repeated RTD calculations
- Enh: Handle stripping Control-M characters from multi-valued headers in
- get_header
- Enh: Update the clock_tick more frequently so that we have a higher timer and
- statistics resolution
- Enh: for option that take a time as argument - allow them to be specified using
- seconds or milliseconds
- Enh: fail when parsing a scenario that has pcap if pcap is not enabled
- Enh: print the actual location of the error log file and the error condition
- (if any) on creation
- Enh: fail when parsing a scenario that enables authentication if SSL is not
- enabled
- Enh: Makefile - include EXTRAENDLIBS keyword so that libraries can be appended
- to the list after SSL Enh: Add regexp_match argument to the receive command for
- universal catching
- Enh: remote control: increase the allowed number of control sockets.
- Enh: 3pcc extended: clean the reach of the allowed number of local twin sockets
- Enh: amelioration of statistic computing
- Enh regexp: add case_indep, occurence and start_line options for the hdr
- matching case
- Enh: Stats: Use RTDs that are precise to the microsecond in -trace_rtt, and
- improve the consistency between trace_rtt and the averages
- Enh: Only include RTDs that are actually used in the CSV output
- Enh: Allow loss percentages less than 1 and also a global command line option to
- specify that packets should be lost at a given percentage
- Fix: fix for -t un error for non-IPv6 platform like win32 - Unable to bind UDP
- socket, errno = 106 (Address family not supported by protocol)
- Fix: Do not initialize the screen library in background mode
- Fix: allow having an optional recv before a recvCmd
- Fix: Authentication: allow [fieldn] values for the [authentication] field
- Fix: updated support of short header forms
- Fix: small bug fix to the micrortt.diff which is required for the initial call
- rate to work properly
- Fix:Allow the code to compile with -Wall -Werror on Linux
- Fix: empty line was generated when [routes] keyword was used and proxy did not
- record-route
- Fix: pcap on HPUX; Fix: Simple fixes identified with valgrind
- Fix: 3pcc extended: problem when quitting
- Fix: regexp: add a warning when the specified header is not present in the
- received message
- Fix: pcap: destroy the send packets thread properly even if the sendto failed
- Fix: bug in regexp due to an incomplete commit (rev 172) - remove some debugging
- traces in message log file
- Fix: bugs on retransmission counters and on cookies for optional messages
- Fix: Incorrect branch in automatic ACK answering to unexpected >= 400 responses,
- as well as automatic CANCEL - in such cases, branch must be identical to the
- branch of the initial INVITE request
- Fix: 3pcc extended: clean up when screen exit. Fix: stop logging when the
- maximum allowed file size is reached (avoid core dump)
- Fix: incomplete Via header in automatic responses when aborting calls
- Fix: -h: -key parameter
- Fix: 3pcc/3pcc extended modes: closes twin sockets properly when twin instance
- exits, to break the poll() loop and avoid the print of empty messages
- Fix: in 3pcc/3pcc extended modes: send BYE/CANCEL before exit due to other twin
- instance exit
- Fix: force exit when pressing q twice (Q press can still be used)
- Fix: Aka authentication for synchro case, also added password len as password
- for authentication might contain char Fix: possible core dump in SDP parser
- Fix: accept up to the 5 defined RTDs (previously would only accept one less)
- Fix: Fail if there is an invalid repartition table specification - previous
- behavior was a core dump
- Fix: added -users option to the parameter table
- Fix: change option description to match timed options
- Fix: trace_err did not work in background mode
- Fix: bug when testing the presence of the 3PCC compilation flag
- Fix: bug in -r -rp option
Download (0.18MB)
Added: 2007-04-27 License: GPL (GNU General Public License) Price:
926 downloads
otto 2.0
otto is a web based mp3 database and jukebox which can gracefully organize a very large number of albums. more>>
otto is a web based mp3 database and jukebox which can gracefully organize a very large number of albums. it is suitable for home or office workgroup use, or as an interface to a streaming internet radio station.
otto is written in perl. it requires perl5, mysql, the DBI and DBD::mysql perl modules (and a few others), and apache. mod_perl is optional. otto runs under linux and could easily be ported to other versions of unix. mpg123 or icecast are used to play or stream your music.
otto was designed with two purposes in mind:
1) to act as an easy interface to all my cds which ive encoded into mp3s. i use otto at home to act as a jukebox which is always playing music from my collection. i rarely put a cd into my cd player anymore, i simply use otto instead.
2) to be a multi-user network streaming jukebox for a group of people to upload and share their music. you could, for example, use this at work with everyone having separate accounts for accessing otto, and everyone having separate upload/download areas for music which they own. people all over the office can share and listen to the same music and everyone can have the pleasure of acting as dj for everyone else.
otto is always playing music. otto keeps a queue of songs to be played. you can add requests to the queue, change the order of requests, delete songs from the queue, or even kill the currently playing song. when there are no songs left to play, otto will add 20 random songs to the queue. requests always play ahead of the random songs otto has picked.
otto is geared toward people who have ripped+encoded entire albums. the otto database groups together tracks from an album and keeps them in album order. whole albums can easily be played, or shuffled together with tracks from other albums.
otto does search
otto tries to pack a lot of information on to a single page. at first this means otto is not always the simplest thing to use. however, once you get the hang of it, otto makes browsing and using your mp3 collection a straightforward task and it tries to stay out of your way as much as possible.
an example of this is the otto search function. if you type a search term into the search form, otto will show search results in three separate areas indicating search matches against artist names, album names, and song titles.
otto does lists
otto lets you create lists of songs that interest you. you can create as many lists as you like. once you have picked a list to work with, icons appear next to all song titles while browsing the database allowing you to easily add or delete songs to the list.
a special trash list allows you to select songs which otto should avoid when it is randomly picking songs. if you dont like the currently playing song, there is a trash icon for quickly adding the current song to the trash list so you never have to hear it again.
otto is multi-user
you can issue a separate username and password to each of your otto users. this is useful in a office workgroup environment. if you organize your mp3s such that each users mp3s are in a separate directory, then otto can keep track of whos albums are whos. otto displays the albums owner next to the album title while you are browsing the database. the currently playing track also has the owner displayed so you know who to blame.
when a user is browsing a song which is tagged as being owned by them, a download link appears next to that song allowing it to be saved locally on the users machine. if desired, this feature can be disabled so any user can download any song.
otto keeps a list of the 30 most recently loaded albums so you can easily see what has been recently loaded by your fellow users.
you can also choose to configure otto not to prompt for a username + password at all. this can be handy when using otto at home where multi-user features dont make as much sense.
otto as radio station
otto makes a fine front end for an internet radio station. instead of using mpg123 to play the music out of your soundcard, otto can use icecast to stream your mp3s over the network. you can even combine mpg123 and icecast to play music and stream to the network at the same time.
the front page for otto is a public page which does not require a username or password. it shows whats playing and whats coming up. otto also parses the icecast stats file and shows how many people are currently listening. on the request interface, you can also see a list of the last 30 icecast listeners and how long they were connected.
if your users log into the web interface from the same machine they use to listening to the stream, otto automatically associates that username with the icecast listener address. this way you can tell who is behind a given icecast connection.
otto as database
one of the design goals for otto was to be able to gracefully browse and search a very large database of mp3 files. otto is a pleasure to use even if you load 20,000 tracks into it. as part of dealing with so many songs, otto has a few options for controlling the organization of your database.
you can arrange for artists with multiple pseudonyms to be filed together under one name. AFX and Caustic Window can be filed under Aphex Twin, for example. or maybe you would like to file a related artist somewhere other than under their own name, Morrissey under The Smiths perhaps.
if you identify specific artists names as proper names, you can have otto file them under their last name instead of their first. like Charlie Parker under P instead of C.
otto also has a separate various artists section and a separate soundtracks section. if you tell otto how to parse the song and artist names from each of your various artists collections, you can have all your Banco de Gaia tracks appear under Banco de Gaia including all his appearances on numerous various artists collections.
other stuff
otto has support for running multiple icecast channels at once. each channel is configured with a different database of songs and has a separate icecast stream associated with it. all from a single otto installation.
otto has some international language support. it can be configured to use an arbitrary character set encoding. it also has an alternate navagation bar containing the greek alphabet in the iso-8859-7 character set. if you want to support another language this will provide a great starting point.
it is easy to write small scripts that fetch the currently playing song and the upcoming song queue. as long as you have mysql installed and the mysql perl module available, the script can run either on the same machine that runs otto, or on a remote machine. this is great for driving non-web based displays (like lcd displays attached to the serial port). a rough example script is included.
otto was originally inspired by the globecom jukebox. if otto doesnt quite do it for you, then perhaps the globcom one will. please see http://www.globecom.net/jukebox/
otto thanks
otto would like to send props out to its peeps. a special thank you to willg (otto logo and general look), jas (suggested the name), mbletsas, rmadams, bfitz, jfinks, mikeg, kasco, tschroed, dbrandon, nfields, spero, and sgunn. thank you all for your help, feedback and encouragement. i hope i didnt forget anyone, im bad that way.
<<lessotto is written in perl. it requires perl5, mysql, the DBI and DBD::mysql perl modules (and a few others), and apache. mod_perl is optional. otto runs under linux and could easily be ported to other versions of unix. mpg123 or icecast are used to play or stream your music.
otto was designed with two purposes in mind:
1) to act as an easy interface to all my cds which ive encoded into mp3s. i use otto at home to act as a jukebox which is always playing music from my collection. i rarely put a cd into my cd player anymore, i simply use otto instead.
2) to be a multi-user network streaming jukebox for a group of people to upload and share their music. you could, for example, use this at work with everyone having separate accounts for accessing otto, and everyone having separate upload/download areas for music which they own. people all over the office can share and listen to the same music and everyone can have the pleasure of acting as dj for everyone else.
otto is always playing music. otto keeps a queue of songs to be played. you can add requests to the queue, change the order of requests, delete songs from the queue, or even kill the currently playing song. when there are no songs left to play, otto will add 20 random songs to the queue. requests always play ahead of the random songs otto has picked.
otto is geared toward people who have ripped+encoded entire albums. the otto database groups together tracks from an album and keeps them in album order. whole albums can easily be played, or shuffled together with tracks from other albums.
otto does search
otto tries to pack a lot of information on to a single page. at first this means otto is not always the simplest thing to use. however, once you get the hang of it, otto makes browsing and using your mp3 collection a straightforward task and it tries to stay out of your way as much as possible.
an example of this is the otto search function. if you type a search term into the search form, otto will show search results in three separate areas indicating search matches against artist names, album names, and song titles.
otto does lists
otto lets you create lists of songs that interest you. you can create as many lists as you like. once you have picked a list to work with, icons appear next to all song titles while browsing the database allowing you to easily add or delete songs to the list.
a special trash list allows you to select songs which otto should avoid when it is randomly picking songs. if you dont like the currently playing song, there is a trash icon for quickly adding the current song to the trash list so you never have to hear it again.
otto is multi-user
you can issue a separate username and password to each of your otto users. this is useful in a office workgroup environment. if you organize your mp3s such that each users mp3s are in a separate directory, then otto can keep track of whos albums are whos. otto displays the albums owner next to the album title while you are browsing the database. the currently playing track also has the owner displayed so you know who to blame.
when a user is browsing a song which is tagged as being owned by them, a download link appears next to that song allowing it to be saved locally on the users machine. if desired, this feature can be disabled so any user can download any song.
otto keeps a list of the 30 most recently loaded albums so you can easily see what has been recently loaded by your fellow users.
you can also choose to configure otto not to prompt for a username + password at all. this can be handy when using otto at home where multi-user features dont make as much sense.
otto as radio station
otto makes a fine front end for an internet radio station. instead of using mpg123 to play the music out of your soundcard, otto can use icecast to stream your mp3s over the network. you can even combine mpg123 and icecast to play music and stream to the network at the same time.
the front page for otto is a public page which does not require a username or password. it shows whats playing and whats coming up. otto also parses the icecast stats file and shows how many people are currently listening. on the request interface, you can also see a list of the last 30 icecast listeners and how long they were connected.
if your users log into the web interface from the same machine they use to listening to the stream, otto automatically associates that username with the icecast listener address. this way you can tell who is behind a given icecast connection.
otto as database
one of the design goals for otto was to be able to gracefully browse and search a very large database of mp3 files. otto is a pleasure to use even if you load 20,000 tracks into it. as part of dealing with so many songs, otto has a few options for controlling the organization of your database.
you can arrange for artists with multiple pseudonyms to be filed together under one name. AFX and Caustic Window can be filed under Aphex Twin, for example. or maybe you would like to file a related artist somewhere other than under their own name, Morrissey under The Smiths perhaps.
if you identify specific artists names as proper names, you can have otto file them under their last name instead of their first. like Charlie Parker under P instead of C.
otto also has a separate various artists section and a separate soundtracks section. if you tell otto how to parse the song and artist names from each of your various artists collections, you can have all your Banco de Gaia tracks appear under Banco de Gaia including all his appearances on numerous various artists collections.
other stuff
otto has support for running multiple icecast channels at once. each channel is configured with a different database of songs and has a separate icecast stream associated with it. all from a single otto installation.
otto has some international language support. it can be configured to use an arbitrary character set encoding. it also has an alternate navagation bar containing the greek alphabet in the iso-8859-7 character set. if you want to support another language this will provide a great starting point.
it is easy to write small scripts that fetch the currently playing song and the upcoming song queue. as long as you have mysql installed and the mysql perl module available, the script can run either on the same machine that runs otto, or on a remote machine. this is great for driving non-web based displays (like lcd displays attached to the serial port). a rough example script is included.
otto was originally inspired by the globecom jukebox. if otto doesnt quite do it for you, then perhaps the globcom one will. please see http://www.globecom.net/jukebox/
otto thanks
otto would like to send props out to its peeps. a special thank you to willg (otto logo and general look), jas (suggested the name), mbletsas, rmadams, bfitz, jfinks, mikeg, kasco, tschroed, dbrandon, nfields, spero, and sgunn. thank you all for your help, feedback and encouragement. i hope i didnt forget anyone, im bad that way.
Download (0.082MB)
Added: 2006-07-18 License: GPL (GNU General Public License) Price:
1196 downloads
Fenris 0.07-m2 build 3245
Fenris is a multipurpose tracer, debugger, and code analysis tool. more>>
Fenris is a suite of tools suitable for code analysis, debugging, protocol analysis, reverse engineering, forensics, diagnostics, security audits, vulnerability research and many other purposes.
The main logical components are:
- Fenris: high-level tracer, a tool that detects the logic used in C programs to find and classify functions, logic program structure, calls, buffers, interaction with system and libraries, I/O and many other structures. Fenris is mostly a "whats inside" tracer, as opposed to ltrace or strace, tracers intended to inspect external "symptoms" of the internal program structure. Fenris does not depend on libbfd for accessing ELF structures, and thus is much more robust when dealing with "anti-debugging" code.
- libfnprints and dress: fingerprinting code that can be used to detect library functions embedded inside a static application, even without symbols, to make code analysis simplier; this functionality is both embedded in other components and available as a standalone tool that adds symtab to ELF binaries and can be used with any debugger or disassembler.
- Aegir: an interactive gdb-alike debugger with modular capabilities, instruction by instruction and breakpoint to breakpoint execution, and real-time access to all the goods offered by Fenris, such as high-level information about memory objects or logical code structure.
- nc-aegir: a SoftICE-alike GUI for Aegir, with automatic register, memory and code views, integrated Fenris output, and automatic Fenris control (now under development).
- Ragnarok: a visualisation tool for Fenris that delivers browsable information about many different aspects of program execution - code flow, function calls, memory object life, I/O, etc (to be redesigned using OpenDX or a similar data exploration interface).
- ...and some other companion utilities.
Code analysis is not limited to debugging, quality assurance or security audits. Understanding and handling file formats or communication protocols used by proprietary solutions, a problem that many corporations face when they decide to change their base software platform from one, obsolete or insufficient solution to another, perhaps more suitable, is a task that can consume long months and millions of dollars, especially when any misjudgment or misinterpretation is made.
Because of that, accurate and complete information about existing solutions has to be obtained and evaluated in a timely manner. This project is an attempt to fill the gap between currently used tools by providing a freely available program analysis utility, suitable for black-box code audits, algorithm analysis,
rapid reconnaissance in open-source projects, tracking down bugs, evaluating security subsystems, performing computer forensics, etc.
This program does not automate the process of auditing, and does not favor any particular use. Instead of that, it is intended to be a flexible and universal application that will be a valuable solution for many advanced users. While functional, it is probably not tested sufficiently, there are many issues to fix, several known bugs, some portability problems.
It is being released primarily to get user feedback, comments, and, most important, to request development support, as my resources are very limited, both in terms of available time and development platforms. This project is and will be distributed as a free software, regardless of projected use, accompanied by complete sources, under the terms and
conditions of GPL. Why do you might need this code? Well, there are few reasons...
Human beings are, so far, the best code analysts. Unlike computer programs, they have imagination, ability to build synthetic abstract models, and yet to observe and analyze smallest details at the same time. Functionality is often being described as "doing what the program is supposed to do", security as "doing what the program is supposed to do and
nothing more". While it might sound funny, that is the most general and complete definition we have. In most real-life scenarios only humans really know what are their expectations. Building strict formal models of our expectations does not necessarily mean that models themselves are flawless, and is very time-consuming. Then, even with such models,
validating the code is not always possible, due to its computational complexity. That is why real, live programs (not including some critical developments) do not have such models, do not follow any particular coding guidelines, and cannot be formally examined without human judgment.
Unfortunately, humans are also highly inaccurate and very expensive. They work slowly, and better results can be achieved by hiring better specialists and performing more careful audit. And after all, even the best expert can overlook something in complex, hard to read code. It is almost impossible for human to perform an accurate audit of a large, complex, heterogeneous project written e.g. in C - like Sendmail, BIND, Apache - and provide results in reasonable time.
Things get even worse when humans try to understand algorithms and protocols used by complex closed-source black box solutions. They are simply too slow, and not always able to make accurate guesses about dozens of complicated, conditional parameter passes and function calls before final action is taken.
While it might sound surprising, human-driven code audit is very similar to playing chess - it is a general analysis of possible states, way too many to be implicitly projected by our conscience, a result of experience, knowledge, some unparalleled capabilities of human brain, and luck. It is also a subject to false moves and misjudgment. And there are maybe just a few hundred excellent players.
As for today, freely and commercially available audit tools both use two opposite approaches. First approach tends to minimize human role by automating the review of source code. Source code analysis methods are good in spotting known, repeatable static errors in the code - such as format string vulnerabilities. On the other hand, static tools are not able to trace and analyze all possible execution paths of complex application by
simply looking at its source.
The reason for inability to follow all execution paths lies deeply in the foundations of modern computation theory, and one of its aspects is known as "the halting problem". Speaking in more general terms, in many cases (such as complex software, or even underlying operating system), the amount of medium needed to store all possible states of a complex program exceeds significantly the number of particles in the
universe; and the amount of time needed to generate and process them sequentially is greater than the lifetime of our universe, even having a machine that works with the speed of light.
This might be changed by the development of new computation models, such as quantum computing, or by creating mathematical models that allow us to make such problems non-polynomial - but for now, we are far from this point, and static analysis is restrained in many very serious ways, even though many software suppliers tend to market their products as the ultimate, 100% solutions. Subtle, complex, conditional dynamic errors, such as privilege dropping problems, input-dependent table overflows in C and many other issues usually cannot be detected without generating a completely unacceptable number of false positives.
This kind of software is highly dependent on coding style, and specific notation or development practices might render them less efficient - for example, automated audit utilities can usually detect problems like insecure call to strcpy() function, but will very likely not notice insecure manual copy in do-while
loop. The truth is, for programs that do not have previously built formal models, static auditing utilities look for known, common problems in known, common types of code in a very limited scope.
Another issue is the applicability of this approach to algorithm analysis tasks. In the domain of automated audit tools, this problem is "reduced" to building a formal model of program behavior, or, more appropriately, generating certain predictive statements about the code. While there are very interesting developments in this direction, such as the work of professor Patrick Cousot, it is very difficult to make any detailed, accurate and abstract enough run-time predictions for complex source code that has any immediate value in the analysis of unknown algorithm.
Last but not least, static analysis of sources can be deployed only when the source code is available, which does not have to be the case. This approach is a subject to many shortcomings, tricky assertions, and is a technique of strictly limited capabilities. This is, of course, not to dismiss this method - but to demonstrate that this much favored approach is not flawless and how much it needs to be accompanied with auxiliary methods.
The second approach to be discussed here is based on a dynamic run-time program analysis. This method is usually used to provide the user with information about actual program execution path, letting him make decisions on which path to follow and giving him free will to draw any conclusions and perform all the synthetic reasoning.
This method is
applied to a live binary executed in real-time and is based on monitoring syscalls (strace), libcalls (ltrace) or functions (xtrace); in certain cases, breakpoint debuggers, such as gdb, can be used, however it is usually not feasible to use them to perform anything more than in-depth analysis of a very small portion of program functionality. Usually, such analysis provides a very useful information on what is happening, and this information is provided in uniform, reduced-output form.
A careful auditor can analyze program behavior and find interesting or potentially dangerous run-time conditions. By monitoring how a given application interacts with external world, he (or she) can determine whether some other
conditions can be triggered and eventually explore them by examining sources or re-running the program. Advantages are enormous, as such software enables the auditor to spot very subtle errors in code that "looked good", to observe actual execution, not to try to figure it out, and to find or trace down not obvious or non-schematic vulnerabilities. Run-time trace tools are primarily used for fast reconnaissance tasks and for tracing down notorious errors that are not clearly visible in the source, significantly reducing the time of such operations.
There are, however, serious drawbacks related to this method. First of all, known tracing tools do not provide the complete information. They will detect strcpy() call, but wont report if exactly the same functionality has been implemented from scratch by the author of given program. And, in some cases, the amount of produced data
can be enormous, and because of its completely unstructured character, it makes the observation of overall execution vector almost impossible. Two most important problems are: correlating trace data with actual code, and determining what occurred in the "dark matter" between two lines of trace output.
There are some attempts to combine both approaches - run-time evaluation and source code analysis - such as Purify or many other commercial development support products. Unfortunately, they all feature a limited set of capabilities that need development-side or compilation-time support and are not really suitable for comprehending black box solutions or performing a general analysis. Most of them are targeted for dynamic memory debugging and code / memory profiling.
While not mentioned above, there is also another approach to black-box code - high-level decompiler. However, the complexity of modern compilers makes it very difficult to develop an effective C decompiler or similar utility, and there are only a few (two?) projects available to accomplish it, all of them not able to deal with too complex or optimized code. Finally, there is no guarantee that generated output code will be any help in comprehending the program. For now, this approach remains almost purely theoretical,
and I am not aware of any auditors using it extensively. Why? Well, heres an example of decompiled, mildly optimized code *with* some symbolic information: http://www.backerstreet.com/rec/ex386/hdgO.rec . One may argue it is less readable than cross-referenced disassembly.
This project, Fenris, is named after the monstrous wolf, son of the Norse god Loki. It is not the ultimate answer to all questions, not a solution for all problems, and under no circumstances is intended to replace other tools and techniques. On the other hand, it makes one step forward compared to other tools, trying to support the auditor and to make his work much more effective. This is accomplished by combining a number of techniques, including partial run-time decompiler, stateful analysis, code fingerprinting, I/O analysis, high-level visualization layer, traditional interactive debugger features and run-time code modification capabilities. The goal is to provide a very detailed trace information, and, at the same time, to provide data suitable to build a model of program behavior more quickly and in more convenient way.
Fenris is not supposed to find vulnerabilities or bugs, or to guess algorithms or describe protocols. It is supposed to report and analyze the execution path - detect and describe functional blocks, monitor data flow in the program, marking its lifetime, source, migration and destination, analyze how functions work and what conditions are evaluated.
At the end, it can deliver you an execution model of traced program (or arbitrarily chosen portion of it, if complete trace results in too much noise or irrelevant information), and hint you how this model can change in different conditions. Fenris does not need source codes of analyzed application, but obviously does not keep the auditor from using them.
For many users, Fenris might be a new tool or tools, for others - just a command-line replacement or addition to strace, ltrace, gdb or similar applications (theres a brief list of other nice tools in doc/other.txt). And thats the idea - to build a tool that is simple, reusable, but also precise and smart. It is supposed to have advantages over other tools, but not to be an ultimate replacement or the final solution. Some users can just use very specific features, such as automated function fingerprinting, and use companion tools instead of the main program.
<<lessThe main logical components are:
- Fenris: high-level tracer, a tool that detects the logic used in C programs to find and classify functions, logic program structure, calls, buffers, interaction with system and libraries, I/O and many other structures. Fenris is mostly a "whats inside" tracer, as opposed to ltrace or strace, tracers intended to inspect external "symptoms" of the internal program structure. Fenris does not depend on libbfd for accessing ELF structures, and thus is much more robust when dealing with "anti-debugging" code.
- libfnprints and dress: fingerprinting code that can be used to detect library functions embedded inside a static application, even without symbols, to make code analysis simplier; this functionality is both embedded in other components and available as a standalone tool that adds symtab to ELF binaries and can be used with any debugger or disassembler.
- Aegir: an interactive gdb-alike debugger with modular capabilities, instruction by instruction and breakpoint to breakpoint execution, and real-time access to all the goods offered by Fenris, such as high-level information about memory objects or logical code structure.
- nc-aegir: a SoftICE-alike GUI for Aegir, with automatic register, memory and code views, integrated Fenris output, and automatic Fenris control (now under development).
- Ragnarok: a visualisation tool for Fenris that delivers browsable information about many different aspects of program execution - code flow, function calls, memory object life, I/O, etc (to be redesigned using OpenDX or a similar data exploration interface).
- ...and some other companion utilities.
Code analysis is not limited to debugging, quality assurance or security audits. Understanding and handling file formats or communication protocols used by proprietary solutions, a problem that many corporations face when they decide to change their base software platform from one, obsolete or insufficient solution to another, perhaps more suitable, is a task that can consume long months and millions of dollars, especially when any misjudgment or misinterpretation is made.
Because of that, accurate and complete information about existing solutions has to be obtained and evaluated in a timely manner. This project is an attempt to fill the gap between currently used tools by providing a freely available program analysis utility, suitable for black-box code audits, algorithm analysis,
rapid reconnaissance in open-source projects, tracking down bugs, evaluating security subsystems, performing computer forensics, etc.
This program does not automate the process of auditing, and does not favor any particular use. Instead of that, it is intended to be a flexible and universal application that will be a valuable solution for many advanced users. While functional, it is probably not tested sufficiently, there are many issues to fix, several known bugs, some portability problems.
It is being released primarily to get user feedback, comments, and, most important, to request development support, as my resources are very limited, both in terms of available time and development platforms. This project is and will be distributed as a free software, regardless of projected use, accompanied by complete sources, under the terms and
conditions of GPL. Why do you might need this code? Well, there are few reasons...
Human beings are, so far, the best code analysts. Unlike computer programs, they have imagination, ability to build synthetic abstract models, and yet to observe and analyze smallest details at the same time. Functionality is often being described as "doing what the program is supposed to do", security as "doing what the program is supposed to do and
nothing more". While it might sound funny, that is the most general and complete definition we have. In most real-life scenarios only humans really know what are their expectations. Building strict formal models of our expectations does not necessarily mean that models themselves are flawless, and is very time-consuming. Then, even with such models,
validating the code is not always possible, due to its computational complexity. That is why real, live programs (not including some critical developments) do not have such models, do not follow any particular coding guidelines, and cannot be formally examined without human judgment.
Unfortunately, humans are also highly inaccurate and very expensive. They work slowly, and better results can be achieved by hiring better specialists and performing more careful audit. And after all, even the best expert can overlook something in complex, hard to read code. It is almost impossible for human to perform an accurate audit of a large, complex, heterogeneous project written e.g. in C - like Sendmail, BIND, Apache - and provide results in reasonable time.
Things get even worse when humans try to understand algorithms and protocols used by complex closed-source black box solutions. They are simply too slow, and not always able to make accurate guesses about dozens of complicated, conditional parameter passes and function calls before final action is taken.
While it might sound surprising, human-driven code audit is very similar to playing chess - it is a general analysis of possible states, way too many to be implicitly projected by our conscience, a result of experience, knowledge, some unparalleled capabilities of human brain, and luck. It is also a subject to false moves and misjudgment. And there are maybe just a few hundred excellent players.
As for today, freely and commercially available audit tools both use two opposite approaches. First approach tends to minimize human role by automating the review of source code. Source code analysis methods are good in spotting known, repeatable static errors in the code - such as format string vulnerabilities. On the other hand, static tools are not able to trace and analyze all possible execution paths of complex application by
simply looking at its source.
The reason for inability to follow all execution paths lies deeply in the foundations of modern computation theory, and one of its aspects is known as "the halting problem". Speaking in more general terms, in many cases (such as complex software, or even underlying operating system), the amount of medium needed to store all possible states of a complex program exceeds significantly the number of particles in the
universe; and the amount of time needed to generate and process them sequentially is greater than the lifetime of our universe, even having a machine that works with the speed of light.
This might be changed by the development of new computation models, such as quantum computing, or by creating mathematical models that allow us to make such problems non-polynomial - but for now, we are far from this point, and static analysis is restrained in many very serious ways, even though many software suppliers tend to market their products as the ultimate, 100% solutions. Subtle, complex, conditional dynamic errors, such as privilege dropping problems, input-dependent table overflows in C and many other issues usually cannot be detected without generating a completely unacceptable number of false positives.
This kind of software is highly dependent on coding style, and specific notation or development practices might render them less efficient - for example, automated audit utilities can usually detect problems like insecure call to strcpy() function, but will very likely not notice insecure manual copy in do-while
loop. The truth is, for programs that do not have previously built formal models, static auditing utilities look for known, common problems in known, common types of code in a very limited scope.
Another issue is the applicability of this approach to algorithm analysis tasks. In the domain of automated audit tools, this problem is "reduced" to building a formal model of program behavior, or, more appropriately, generating certain predictive statements about the code. While there are very interesting developments in this direction, such as the work of professor Patrick Cousot, it is very difficult to make any detailed, accurate and abstract enough run-time predictions for complex source code that has any immediate value in the analysis of unknown algorithm.
Last but not least, static analysis of sources can be deployed only when the source code is available, which does not have to be the case. This approach is a subject to many shortcomings, tricky assertions, and is a technique of strictly limited capabilities. This is, of course, not to dismiss this method - but to demonstrate that this much favored approach is not flawless and how much it needs to be accompanied with auxiliary methods.
The second approach to be discussed here is based on a dynamic run-time program analysis. This method is usually used to provide the user with information about actual program execution path, letting him make decisions on which path to follow and giving him free will to draw any conclusions and perform all the synthetic reasoning.
This method is
applied to a live binary executed in real-time and is based on monitoring syscalls (strace), libcalls (ltrace) or functions (xtrace); in certain cases, breakpoint debuggers, such as gdb, can be used, however it is usually not feasible to use them to perform anything more than in-depth analysis of a very small portion of program functionality. Usually, such analysis provides a very useful information on what is happening, and this information is provided in uniform, reduced-output form.
A careful auditor can analyze program behavior and find interesting or potentially dangerous run-time conditions. By monitoring how a given application interacts with external world, he (or she) can determine whether some other
conditions can be triggered and eventually explore them by examining sources or re-running the program. Advantages are enormous, as such software enables the auditor to spot very subtle errors in code that "looked good", to observe actual execution, not to try to figure it out, and to find or trace down not obvious or non-schematic vulnerabilities. Run-time trace tools are primarily used for fast reconnaissance tasks and for tracing down notorious errors that are not clearly visible in the source, significantly reducing the time of such operations.
There are, however, serious drawbacks related to this method. First of all, known tracing tools do not provide the complete information. They will detect strcpy() call, but wont report if exactly the same functionality has been implemented from scratch by the author of given program. And, in some cases, the amount of produced data
can be enormous, and because of its completely unstructured character, it makes the observation of overall execution vector almost impossible. Two most important problems are: correlating trace data with actual code, and determining what occurred in the "dark matter" between two lines of trace output.
There are some attempts to combine both approaches - run-time evaluation and source code analysis - such as Purify or many other commercial development support products. Unfortunately, they all feature a limited set of capabilities that need development-side or compilation-time support and are not really suitable for comprehending black box solutions or performing a general analysis. Most of them are targeted for dynamic memory debugging and code / memory profiling.
While not mentioned above, there is also another approach to black-box code - high-level decompiler. However, the complexity of modern compilers makes it very difficult to develop an effective C decompiler or similar utility, and there are only a few (two?) projects available to accomplish it, all of them not able to deal with too complex or optimized code. Finally, there is no guarantee that generated output code will be any help in comprehending the program. For now, this approach remains almost purely theoretical,
and I am not aware of any auditors using it extensively. Why? Well, heres an example of decompiled, mildly optimized code *with* some symbolic information: http://www.backerstreet.com/rec/ex386/hdgO.rec . One may argue it is less readable than cross-referenced disassembly.
This project, Fenris, is named after the monstrous wolf, son of the Norse god Loki. It is not the ultimate answer to all questions, not a solution for all problems, and under no circumstances is intended to replace other tools and techniques. On the other hand, it makes one step forward compared to other tools, trying to support the auditor and to make his work much more effective. This is accomplished by combining a number of techniques, including partial run-time decompiler, stateful analysis, code fingerprinting, I/O analysis, high-level visualization layer, traditional interactive debugger features and run-time code modification capabilities. The goal is to provide a very detailed trace information, and, at the same time, to provide data suitable to build a model of program behavior more quickly and in more convenient way.
Fenris is not supposed to find vulnerabilities or bugs, or to guess algorithms or describe protocols. It is supposed to report and analyze the execution path - detect and describe functional blocks, monitor data flow in the program, marking its lifetime, source, migration and destination, analyze how functions work and what conditions are evaluated.
At the end, it can deliver you an execution model of traced program (or arbitrarily chosen portion of it, if complete trace results in too much noise or irrelevant information), and hint you how this model can change in different conditions. Fenris does not need source codes of analyzed application, but obviously does not keep the auditor from using them.
For many users, Fenris might be a new tool or tools, for others - just a command-line replacement or addition to strace, ltrace, gdb or similar applications (theres a brief list of other nice tools in doc/other.txt). And thats the idea - to build a tool that is simple, reusable, but also precise and smart. It is supposed to have advantages over other tools, but not to be an ultimate replacement or the final solution. Some users can just use very specific features, such as automated function fingerprinting, and use companion tools instead of the main program.
Download (1.1MB)
Added: 2005-04-18 License: GPL (GNU General Public License) Price:
1657 downloads
Laughing Man Factorial 0.1
Laughing Man Factorial is the paranormal evil twin of Laughing Man. more>>
Laughing Man Factorial is the paranormal evil twin of Laughing Man. Factorial also has an unexplained superiority complex, almost exponential you might say, over the original Laughing Man which we will hence forth refer to as Junior for appeasement of currently unwarranted hoity-toity.
Like Junior it is an application for monitoring webpage changes, however it does so using the Objective-C/Cocoa framework as opposed to Java, and leverages Core Data, bindings, and value transformers to produce a smaller code footprint. Less fluff and more meat I say, more meat and less fluff.
Factorial is in a experimental state, it is not recommended that current users of Junior switch completely to this version. You can safely import your data and tinker with Factorial, but it is recommended that any data that you want to remain consistent, be done through old stable Junior.
Factorial may not be forgiving on data when upgrading from one version to the next for the next several releases, hence the adjectives paranormal and evil in the preface.
Junior Equivalent functionality
Splitbar position saved on shutdown
Categories display like junior
New Features
Drag and drop funtionality greatly enhanced
supports dragging to and from Safari and OmniWeb
Change log embedded into application and available through menu.
Enhancements:
- This release fixes several bugs, and provides several feature enhancements, bringing the Factorial branch almost up to par with the original Laughing Man.
- Most notably, a nasty Java to Objective-C, Date to NSDate porting bug in the beta was fixed.
- The beta was usable, but users had to wait a little under 3 years for each site refresh.
- This issue has been fixed in 0.1, but you must reset your data if you used the beta.
<<lessLike Junior it is an application for monitoring webpage changes, however it does so using the Objective-C/Cocoa framework as opposed to Java, and leverages Core Data, bindings, and value transformers to produce a smaller code footprint. Less fluff and more meat I say, more meat and less fluff.
Factorial is in a experimental state, it is not recommended that current users of Junior switch completely to this version. You can safely import your data and tinker with Factorial, but it is recommended that any data that you want to remain consistent, be done through old stable Junior.
Factorial may not be forgiving on data when upgrading from one version to the next for the next several releases, hence the adjectives paranormal and evil in the preface.
Junior Equivalent functionality
Splitbar position saved on shutdown
Categories display like junior
New Features
Drag and drop funtionality greatly enhanced
supports dragging to and from Safari and OmniWeb
Change log embedded into application and available through menu.
Enhancements:
- This release fixes several bugs, and provides several feature enhancements, bringing the Factorial branch almost up to par with the original Laughing Man.
- Most notably, a nasty Java to Objective-C, Date to NSDate porting bug in the beta was fixed.
- The beta was usable, but users had to wait a little under 3 years for each site refresh.
- This issue has been fixed in 0.1, but you must reset your data if you used the beta.
Download (0.044MB)
Added: 2005-11-26 License: GPL (GNU General Public License) Price:
1430 downloads
College Linux 2.5 (Obi Wan)
College Linux is CollegeLinux a new, stand-alone operating system based on Slackware. more>>
The aim of this experimental Linux distribution is to provide to RKC students andto the student population at large an operating system which is easy to install and use and which provides an alternative to the traditional commercial operating systems ;) Why Slackware as a base?
As they themselves put it, "The Official Release of Slackware Linux by Patrick Volkerding is an advanced Linux operating system, designed with the twin goals of ease of use and stability as top priorities.
Including the latest popular software while retaining a sense of tradition, providing simplicity and ease of use alongside flexibility and power, Slackware brings the best of all worlds to the table. "CollegeLinux can benefit from the stability of slackware now made easy with our user friendly installer and interface.
The basic concept of CollegeLinux is to provide you with an alternative, user-friendly operating system and a way to learn more using linux. Whilst maintaining simplicity and a user friendly system, we want to introduce our users to more advanced features and why not, to maintain the "geek" side of linux by providing an excellent development environment.
Thanks to the great environment and suite of free software provided by KDE.Once you have installed CollegeLinux you can do the normal tasks you used to accomplish under your "old" OS namely:
- Using an office suite which containts an advanced text editor,spreadsheet, presentation tool, chart, scientific calculator and much more (thanks to OpenOffice, you can modify your windows documents or save your new documents in a windows compatible format like .doc, .xls etc);
- Organizing your work/study task with calendar, task manager and everything you might need to cope with your busy life;-Having available an email suite, browsers, html editor, graphic software,music and multimedia tools and much more.
-Development & Server environment: The new CollegeLinux 2.5. comes with a "robot" to auto install and configure on the fly PHP,Apache, Webmin and MySQL on the fly: your complete development environment. If you always wanted to learn some programming this is your chance. With our tools and the full manual at dotgeek you can start learning PHP with collegelinux and test your first scripts locally.
- Installing and upgrading any of the available packages via a slapt get based, easy to use interface. The expandibility of CollegeLinux is therefore limited only by your own imagination!
Enhancements:
- Full compatibility with Slackware 9.1 ;
- CollegeLinux server robot: install & configure automatically (almost no question asked) Apache, PHP, MySQL, SQLite, Webmin and Phpmyadmin (mysql front end) and SQLiteManager (sqlite frontend) your complete server & development environment;
- CL auto-update engine: slapt-get based(special thanks to Jason Woodward ) integrated with a Konqueror front end. You can now update on the fly every package or the entire distribution.
- Our own Installer substantiall upgraded, more hardware supported.
- Direct connect file sharing, latest kde, openoffice and much more.
<<lessAs they themselves put it, "The Official Release of Slackware Linux by Patrick Volkerding is an advanced Linux operating system, designed with the twin goals of ease of use and stability as top priorities.
Including the latest popular software while retaining a sense of tradition, providing simplicity and ease of use alongside flexibility and power, Slackware brings the best of all worlds to the table. "CollegeLinux can benefit from the stability of slackware now made easy with our user friendly installer and interface.
The basic concept of CollegeLinux is to provide you with an alternative, user-friendly operating system and a way to learn more using linux. Whilst maintaining simplicity and a user friendly system, we want to introduce our users to more advanced features and why not, to maintain the "geek" side of linux by providing an excellent development environment.
Thanks to the great environment and suite of free software provided by KDE.Once you have installed CollegeLinux you can do the normal tasks you used to accomplish under your "old" OS namely:
- Using an office suite which containts an advanced text editor,spreadsheet, presentation tool, chart, scientific calculator and much more (thanks to OpenOffice, you can modify your windows documents or save your new documents in a windows compatible format like .doc, .xls etc);
- Organizing your work/study task with calendar, task manager and everything you might need to cope with your busy life;-Having available an email suite, browsers, html editor, graphic software,music and multimedia tools and much more.
-Development & Server environment: The new CollegeLinux 2.5. comes with a "robot" to auto install and configure on the fly PHP,Apache, Webmin and MySQL on the fly: your complete development environment. If you always wanted to learn some programming this is your chance. With our tools and the full manual at dotgeek you can start learning PHP with collegelinux and test your first scripts locally.
- Installing and upgrading any of the available packages via a slapt get based, easy to use interface. The expandibility of CollegeLinux is therefore limited only by your own imagination!
Enhancements:
- Full compatibility with Slackware 9.1 ;
- CollegeLinux server robot: install & configure automatically (almost no question asked) Apache, PHP, MySQL, SQLite, Webmin and Phpmyadmin (mysql front end) and SQLiteManager (sqlite frontend) your complete server & development environment;
- CL auto-update engine: slapt-get based(special thanks to Jason Woodward ) integrated with a Konqueror front end. You can now update on the fly every package or the entire distribution.
- Our own Installer substantiall upgraded, more hardware supported.
- Direct connect file sharing, latest kde, openoffice and much more.
Download (601MB)
Added: 2005-04-06 License: GPL (GNU General Public License) Price:
1670 downloads
Sflack 12.0
Sflack Linux is based on Slackware(R) Linux disrtibuition. more>>
Sflack Linux is based on Slackware Linux disrtibuition. Sflack Linux is a UNOFFICIAL port of Slackware to the x86_64 architecture. This means is:
- It runs nicer on an amd64;
- It is *not* called Slackware, or any direct derivative;
Do not bug Patrick Volkerding with bug reports. Sflack is not his responsibility.
Sflack isnt a multi-lib distribution, which means that you cannot run 32-bit applications easily.
The Official Release of Sflack Linux by Vincenzo Ingrosso would want to be an advanced Linux operating system, designed with the twin goals of ease of use and stability as top priorities. Including the latest popular software while retaining a sense of tradition, providing simplicity and ease of use alongside flexibility and power, Sflack brings the best of all worlds to the table.
Originally developed by Linus Torvalds in 1991, the UNIX-like Linux operating system now benefits from the contributions of millions of users and developers around the world. Sflack Linux provides new and experienced users alike with a fully-featured system, equipped to serve in any capacity from desktop workstation to machine-room server. Web, ftp, and email servers are ready to go out of the box, as are a wide selection of popular desktop environments. A full range of development tools, editors, and current libraries is included for users who wish to develop or compile additional software.
Sflack Overview
Sflack Linux is a complete and pure 64-bit multitasking "UNIX-like" system.i Its currently based around the 2.6 Linux kernel series and the GNU C Library version 2.4 (libc6). It contains an easy to use installation program, extensive online documentation, and a menu-driven package system. A full installation gives you the X Window System, C/C++ development environments, Perl, networking utilities, a mail server, a news server, a web server, an ftp server, the GNU Image Manipulation Program, Firefox Web Browser, plus many more programs. Sflack Linux can run on amd64 systems all the way up to the latest x86_64 machines (uses -m64 optimization for best performance on amd64-class machines).
Enhancements:
- This release uses the latest kernel, KDE 3.5.7, XFce 4.4.1, HAL automounting for desktop users, an updated toolchain, and many other enhancements.
<<less- It runs nicer on an amd64;
- It is *not* called Slackware, or any direct derivative;
Do not bug Patrick Volkerding with bug reports. Sflack is not his responsibility.
Sflack isnt a multi-lib distribution, which means that you cannot run 32-bit applications easily.
The Official Release of Sflack Linux by Vincenzo Ingrosso would want to be an advanced Linux operating system, designed with the twin goals of ease of use and stability as top priorities. Including the latest popular software while retaining a sense of tradition, providing simplicity and ease of use alongside flexibility and power, Sflack brings the best of all worlds to the table.
Originally developed by Linus Torvalds in 1991, the UNIX-like Linux operating system now benefits from the contributions of millions of users and developers around the world. Sflack Linux provides new and experienced users alike with a fully-featured system, equipped to serve in any capacity from desktop workstation to machine-room server. Web, ftp, and email servers are ready to go out of the box, as are a wide selection of popular desktop environments. A full range of development tools, editors, and current libraries is included for users who wish to develop or compile additional software.
Sflack Overview
Sflack Linux is a complete and pure 64-bit multitasking "UNIX-like" system.i Its currently based around the 2.6 Linux kernel series and the GNU C Library version 2.4 (libc6). It contains an easy to use installation program, extensive online documentation, and a menu-driven package system. A full installation gives you the X Window System, C/C++ development environments, Perl, networking utilities, a mail server, a news server, a web server, an ftp server, the GNU Image Manipulation Program, Firefox Web Browser, plus many more programs. Sflack Linux can run on amd64 systems all the way up to the latest x86_64 machines (uses -m64 optimization for best performance on amd64-class machines).
Enhancements:
- This release uses the latest kernel, KDE 3.5.7, XFce 4.4.1, HAL automounting for desktop users, an updated toolchain, and many other enhancements.
Download (MB)
Added: 2007-07-05 License: GPL (GNU General Public License) Price:
842 downloads
Krusader 1.80.0
Krusader is an advanced twin-panel (commander-style) file-manager for KDE 3.x more>>
It provides all the file-management features you could possibly want.
Plus: extensive archive handling, mounted filesystem support, FTP, advanced search module, viewer/editor, directory synchronisation, file content comparisons, powerful batch renaming and much much more.
It supports the following archive formats: tar, zip, bzip2, gzip, rar, ace, arj and rpm and can handle other KIOSlaves such as smb or fish. It is (almost) completely customizable, very user friendly, fast and looks great on your desktop!
You should give it a try.
Main features:
- extensive archive handling
- mounted filesystem support
- FTP, an advanced search module
- a text viewer/editor
- directory synchronization
- support for file content comparisons
- powerful batch renaming
- It supports the following archive formats: tar, zip, bzip2, gzip, rar, ace, arj, and rpm. It can also handle other KIOSlaves such as smb:// or fish://.
- and much more...
Version restrictions:
- In order to successfully use the most recent Krusader, you need KDElibs >= 3.2.x.
- Krusader uses about 3-4 MByte of memory to run (and about 15 Mbyte shared memory which is also used by more processes), but this may vary depending on your platform and configuration.
<<lessPlus: extensive archive handling, mounted filesystem support, FTP, advanced search module, viewer/editor, directory synchronisation, file content comparisons, powerful batch renaming and much much more.
It supports the following archive formats: tar, zip, bzip2, gzip, rar, ace, arj and rpm and can handle other KIOSlaves such as smb or fish. It is (almost) completely customizable, very user friendly, fast and looks great on your desktop!
You should give it a try.
Main features:
- extensive archive handling
- mounted filesystem support
- FTP, an advanced search module
- a text viewer/editor
- directory synchronization
- support for file content comparisons
- powerful batch renaming
- It supports the following archive formats: tar, zip, bzip2, gzip, rar, ace, arj, and rpm. It can also handle other KIOSlaves such as smb:// or fish://.
- and much more...
Version restrictions:
- In order to successfully use the most recent Krusader, you need KDElibs >= 3.2.x.
- Krusader uses about 3-4 MByte of memory to run (and about 15 Mbyte shared memory which is also used by more processes), but this may vary depending on your platform and configuration.
Download (4.1MB)
Added: 2007-07-23 License: GPL (GNU General Public License) Price:
506 downloads
Unreal Tournament 2004 BONUS MEGAPACK
Unreal Tournament 2004 BONUS MEGAPACK contains many missions for Unreal Turnament 2004. more>>
Unreal Tournament 2004 BONUS MEGAPACK contains many missions for Unreal Turnament 2004.
This pack is our way of saying "Thanks" for purchasing UT2004. We hope you enjoy it!
This bonus pack includes everything you need to update UT2004 to the most current version, including the latest patch, and the content from the first (Editors Choice Edition) bonus pack for UT2004. You can install this bonus pack on any version of UT2004.
The MegaPack includes the following maps:
Assault:
AS-BP2-Acatana
Intense space fighting and on-foot combat combine in this recreation of the historic Skaarj invasion of the Acatana asteroid belt.
AS-BP2-Jumpship
Be part of the elite team that infiltrated and hijacked the first warp capable Jumpship.
AS-BP2-Outback
City slickers just took over the outback’s top brewery – get over there pronto and stop the production of their tasteless Zero Beer before it takes over Oz!
AS-BP2-SubRosa
Fight your way into a Liandri research facility and steal the original plans for the Redeemer.
AS-BP2-Thrust
A recreation of the infamous destruction of the Saturn IX rocket where a team of rebel fighters launched it unguided and half fueled into hostile waters.
CTF:
CTF-BP2-Concentrate
Tall spires tower over this Capture the Flag battle set on a derelict outpost deep in the Elorean Seas.
CTF-BP2-Pistola
This twin complex of concrete and metal combines the beauty of nature with the harsh lines of industrial architecture to create a fierce battle arena.
Deathmatch:
DM-BP2-Calandras
The courtyards of Calandras were once beautiful and welcoming. While the Temple’s interiors have been preserved, a new less-inviting use has been found for the exteriors.
DM-BP2-GoopGod
For centuries the Nali monks managed to keep this sacred burial ground hidden until Liandri satellites discovered the location during a routine satellite sweep. The area was mined, and what remained was converted into a tournament arena, corpses and all.
The content from the first bonuspack, also included, is:
Onslaught:
ONS-Adara
ONS-IslandHop
ONS-Tricky
ONS-Urban
Three new vehicles:
SPMA (Self Propelled Mobile Artillery)
The SPMA is a two person vehicle, with the driver controlling a long range artillery piece. Alt-fire deploys the spotter camera. Enemies will want to shoot down the spotter camera as soon as they see it, to keep the SPMA from raining destruction from afar. An AVRiL at the spotter camera will automatically re-direct toward the SPMA if it ever becomes visible to the AVRiL.
Paladin
The Paladin is a defense focused vehicle, with a powerful energy projectile cannon and a defensive shield alt-fire. Firing the cannon while the shield is deployed will heavily damage nearby players.
Cicada
The two-man Cicada ground attack bomber is a powerful weapon against ground targets, but is easy prey for Raptors. The pilot can fire missiles, or use the alt-fire to specify a target. While holding alt-fire, multiple missiles are loaded up, and released when alt-fire is released. These missiles will all track toward the specified target location, so the alt-fire can be used to avoid enemy fire while loading up missiles. The second seat in the Cicada is an energy beam turret located on the belly of the Cicada. Its alt-fire is chaff that can be used to confuse incoming AVRiLs.
Six new characters:
Mekkor (Skaarj)
Mekkor is from the Black Fist Clan, sworn enemies of the Iron Skull Clan. Severely injured in battle, he is testing his new cybernetic armor in the Tournament.
Skrilax (Skaarj)
Skrilax is from the Black Fist Clan, sworn enemies of the Iron Skull Clan. Alongside his brother Mekkor, he was severely injured while fighting the Iron Skull Clan."
Barktooth (Iron Guard)
Barktooth would rather rip an opponent to shreds with his bare hands than fight from afar. He also finds close range Flak shots very satisfying."
Karag (Iron Guard)
Before joining the Iron Guard, Karag honed his weapon handling skills during a long stint as a Marshall for the Terran Colonial Authority. His style and panache already have the the Tournament audience abuzz."
Kragoth (Necris)
After an absence of several years, the Necris are preparing a return to the Tournament. Known as the Star Slayer, Kragoth is a dread Necris Phayder assassin. He is rumored to have single handedly killed the entire crew of an ICV Star Cruiser."
Thannis (Necris)
After an absence of several years, the Necris are preparing a return to the Tournament. Thannis is participating to scout the competition."
<<lessThis pack is our way of saying "Thanks" for purchasing UT2004. We hope you enjoy it!
This bonus pack includes everything you need to update UT2004 to the most current version, including the latest patch, and the content from the first (Editors Choice Edition) bonus pack for UT2004. You can install this bonus pack on any version of UT2004.
The MegaPack includes the following maps:
Assault:
AS-BP2-Acatana
Intense space fighting and on-foot combat combine in this recreation of the historic Skaarj invasion of the Acatana asteroid belt.
AS-BP2-Jumpship
Be part of the elite team that infiltrated and hijacked the first warp capable Jumpship.
AS-BP2-Outback
City slickers just took over the outback’s top brewery – get over there pronto and stop the production of their tasteless Zero Beer before it takes over Oz!
AS-BP2-SubRosa
Fight your way into a Liandri research facility and steal the original plans for the Redeemer.
AS-BP2-Thrust
A recreation of the infamous destruction of the Saturn IX rocket where a team of rebel fighters launched it unguided and half fueled into hostile waters.
CTF:
CTF-BP2-Concentrate
Tall spires tower over this Capture the Flag battle set on a derelict outpost deep in the Elorean Seas.
CTF-BP2-Pistola
This twin complex of concrete and metal combines the beauty of nature with the harsh lines of industrial architecture to create a fierce battle arena.
Deathmatch:
DM-BP2-Calandras
The courtyards of Calandras were once beautiful and welcoming. While the Temple’s interiors have been preserved, a new less-inviting use has been found for the exteriors.
DM-BP2-GoopGod
For centuries the Nali monks managed to keep this sacred burial ground hidden until Liandri satellites discovered the location during a routine satellite sweep. The area was mined, and what remained was converted into a tournament arena, corpses and all.
The content from the first bonuspack, also included, is:
Onslaught:
ONS-Adara
ONS-IslandHop
ONS-Tricky
ONS-Urban
Three new vehicles:
SPMA (Self Propelled Mobile Artillery)
The SPMA is a two person vehicle, with the driver controlling a long range artillery piece. Alt-fire deploys the spotter camera. Enemies will want to shoot down the spotter camera as soon as they see it, to keep the SPMA from raining destruction from afar. An AVRiL at the spotter camera will automatically re-direct toward the SPMA if it ever becomes visible to the AVRiL.
Paladin
The Paladin is a defense focused vehicle, with a powerful energy projectile cannon and a defensive shield alt-fire. Firing the cannon while the shield is deployed will heavily damage nearby players.
Cicada
The two-man Cicada ground attack bomber is a powerful weapon against ground targets, but is easy prey for Raptors. The pilot can fire missiles, or use the alt-fire to specify a target. While holding alt-fire, multiple missiles are loaded up, and released when alt-fire is released. These missiles will all track toward the specified target location, so the alt-fire can be used to avoid enemy fire while loading up missiles. The second seat in the Cicada is an energy beam turret located on the belly of the Cicada. Its alt-fire is chaff that can be used to confuse incoming AVRiLs.
Six new characters:
Mekkor (Skaarj)
Mekkor is from the Black Fist Clan, sworn enemies of the Iron Skull Clan. Severely injured in battle, he is testing his new cybernetic armor in the Tournament.
Skrilax (Skaarj)
Skrilax is from the Black Fist Clan, sworn enemies of the Iron Skull Clan. Alongside his brother Mekkor, he was severely injured while fighting the Iron Skull Clan."
Barktooth (Iron Guard)
Barktooth would rather rip an opponent to shreds with his bare hands than fight from afar. He also finds close range Flak shots very satisfying."
Karag (Iron Guard)
Before joining the Iron Guard, Karag honed his weapon handling skills during a long stint as a Marshall for the Terran Colonial Authority. His style and panache already have the the Tournament audience abuzz."
Kragoth (Necris)
After an absence of several years, the Necris are preparing a return to the Tournament. Known as the Star Slayer, Kragoth is a dread Necris Phayder assassin. He is rumored to have single handedly killed the entire crew of an ICV Star Cruiser."
Thannis (Necris)
After an absence of several years, the Necris are preparing a return to the Tournament. Thannis is participating to scout the competition."
Download (194MB)
Added: 2005-12-19 License: Freeware Price:
1404 downloads
Pygoscelis Alpha 1
Pygoscelis provides many powerful features and abilities for easy and effective file managment. more>>
Pygoscelis is modern advanced twinpanel filemanager for GNOME Desktop environment that continues in tradition of dualpanel filemanagers started by Norton Commander.
Pygoscelis project is written purely in Python language using PyGTK and Gnome Python bindings. Pygoscelis provides many powerful features and abilities for easy and effective file managment.
User interface is clean, perfectly fit into the GNOME, tries to by HIG compliant but also keep traditional dualpanel interface.
Word Pygocelis was taken from latin and stands for common genus of penguins
Project was originaly started as part of my bachelors thesis about orthordox filemanager and its development continues as free software released under the GNU General Public License (GPL).
Main features:
- Twin panels
- Tabbed inteface
- Gnome theme MIME awares
- Searching abilities
- Mounted filesystem support
- Archive support
- FTP support (planned)
- Plugin interface (planned)
<<lessPygoscelis project is written purely in Python language using PyGTK and Gnome Python bindings. Pygoscelis provides many powerful features and abilities for easy and effective file managment.
User interface is clean, perfectly fit into the GNOME, tries to by HIG compliant but also keep traditional dualpanel interface.
Word Pygocelis was taken from latin and stands for common genus of penguins
Project was originaly started as part of my bachelors thesis about orthordox filemanager and its development continues as free software released under the GNU General Public License (GPL).
Main features:
- Twin panels
- Tabbed inteface
- Gnome theme MIME awares
- Searching abilities
- Mounted filesystem support
- Archive support
- FTP support (planned)
- Plugin interface (planned)
Download (MB)
Added: 2006-09-07 License: GPL (GNU General Public License) Price:
1146 downloads
mksite.sh 2006-0428
mksite.sh is a static Web site / project HTML documentation formatter that only requires the Bourne shell and sed. more>>
mksite.sh is a static Web site / project HTML documentation formatter that only requires the Bourne shell and sed.
mksite.sh gives a common look and full navigation to an HTML Web site along with all the needed metadata detection, site map generation, and variable expansion.
It has a tabbed layout suitable for hundreds of Web pages, and is small enough to be added to any project tarball.
Pro
- It requires only sh/sed posix shell tools to build doc pages.
- It can build a common navigation bar and a sitemap for all webpages.
- The program is a single short script file freely copyable & modifiable.
Con
- All embedded meta-information must fit on a single line each.
- There is only little more functionality than variable substititions.
- The doc processing is slow - and even slower without gnu sed.
Neutral
- A sitefile must be written - the sitemap is not truly autodetected.
- The speedier twin perl script provides the exact same functionality.
- Best for small webpages but gets too slow for hundreds of webpages.
- The fancy results stem from the sitefile logic - see our examples .
Plus
- Automatic "printerstyle" page generation helping text-mode browsers.
- That style helps also for web accessibility of challenged people.
- Ships with fancy tabbed style navigation as shown on these webpages.
- Shortpage special style to print source code on full screen width.
- It can adapt hrefs to navigate web content pages in subdirectories.
Enhancements:
- A workaround was made for bugs in GNU sed.
- Pagelist detection was enhanced.
- The unit tests were corrected.
<<lessmksite.sh gives a common look and full navigation to an HTML Web site along with all the needed metadata detection, site map generation, and variable expansion.
It has a tabbed layout suitable for hundreds of Web pages, and is small enough to be added to any project tarball.
Pro
- It requires only sh/sed posix shell tools to build doc pages.
- It can build a common navigation bar and a sitemap for all webpages.
- The program is a single short script file freely copyable & modifiable.
Con
- All embedded meta-information must fit on a single line each.
- There is only little more functionality than variable substititions.
- The doc processing is slow - and even slower without gnu sed.
Neutral
- A sitefile must be written - the sitemap is not truly autodetected.
- The speedier twin perl script provides the exact same functionality.
- Best for small webpages but gets too slow for hundreds of webpages.
- The fancy results stem from the sitefile logic - see our examples .
Plus
- Automatic "printerstyle" page generation helping text-mode browsers.
- That style helps also for web accessibility of challenged people.
- Ships with fancy tabbed style navigation as shown on these webpages.
- Shortpage special style to print source code on full screen width.
- It can adapt hrefs to navigate web content pages in subdirectories.
Enhancements:
- A workaround was made for bugs in GNU sed.
- Pagelist detection was enhanced.
- The unit tests were corrected.
Download (0.18MB)
Added: 2006-04-28 License: zlib/libpng License Price:
1278 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above twins 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
