pain demolition trophies
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 68
Religion 1.04
Religion is a Perl module that can generate tracebacks and create and install die() and warn() handlers. more>>
Religion is a Perl module that can generate tracebacks and create and install die() and warn() handlers.
This is a second go at a module to simplify installing die() and warn() handlers, and to make such handlers easier to write and control.
For most people, this just means that if use use Religion; then youll get noticably better error reporting from warn() and die(). This is especially useful if you are using eval().
Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and DiePreHandler, that when you construct them return closures that can be stored in variables that in turn get invoked by $SIG{__DIE__} and $SIG{__WARN__}. Note that if Religion is in use, you should not modify $SIG{__DIE__} or $SIG{__WARN__}, unless you are careful about invoking chaining to the old handler.
Religion also provides a TraceBack function, which is used by a DieHandler after you die() to give a better handle on the current scope of your situation, and provide information about where you were, which might influence where you want to go next, either returning back to where you were, or going on to the very last. [Sorry - Ed.]
See below for usage and examples.
USAGE
DieHandler SUB
Invoke like this:
$Die::Handler = new DieHandler sub {
#...
};
where #... contains your handler code. Your handler will receive the following arguments:
$message, $full_message, $level, $eval,
$iline, $ifile, $oline, $ofile, $oscope
$message is the message provided to die(). Note that the default addition of " at FILE line LINE.n" will have been stripped off if it was present. If you want to add such a message back on, feel free to do so with $iline and $ifile.
$full_message) is the message with a scope message added on if there was no newline at the end of $message. Currently, this is not the original message that die() tacked on, but something along the lines of " at line 3 of the eval at line 4 of Foo.pln".
$eval is non-zero if the die() was invoked inside an eval.
The rest of the arguments are explained in the source for Religion::TraceBack. Yes, I need to document these, but not just now, for they are a pain to explain.
Whenever you install a DieHandler, it will automatically store the current value of $Die::Handler so it can chain to it. If you want to install a handler only temporarily, use local().
If your handler returns data using return or by falling off the end, then the items returns will be used to fill back in the argument list, and the next handler in the chain, if any, will be invoked. Dont fall off the end if you dont want to change the error message.
If your handler exits using last, then no further handlers will be invoked, and the program will die immediatly.
If your handler exits using next, then the next handler in the chain will be invoked directly, without giving you a chance to change its arguments as you could if you used return.
If your handler invokes die(), then die() will proceed as if no handlers were installed. If you are inside an eval, then it will exit to the scope enclosing the eval, otherwise it will exit the program.
WarnHandler SUB
Invoke like this:
$Warn::Handler = new WarnHandler sub {
#...
};
For the rest of its explanation, see DieHandler, and subsitute warn() for die(). Note that once the last DieHandler completes (or last is invoked) then execution will return to the code that invoked warn().
DiePreHandler SUB
Invoke like this:
$Die::PreHandler = new DiePreHandler sub {
#...
};
This works identically to $Die::Handler, except that it forms a separate chain that is invoked before the DieHandler chain. Since you can use last to abort all the handlers and die immediately, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages from further handling.
This is even more useful in $Warn::PreHandler, since you can just throw away warnings that you know arent needed.
WarnPreHandler SUB
Invoke like this:
$Warn::PreHandler = new WarnPreHandler sub {
#...
};
This works identically to $Warn::Handler, except that it forms a separate chain that is invoked before the WarnHandler chain. Since you can use last to abort all the handlers and return to the program, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages.
This is very useful, since you can just throw away warnings that you know arent needed.
<<lessThis is a second go at a module to simplify installing die() and warn() handlers, and to make such handlers easier to write and control.
For most people, this just means that if use use Religion; then youll get noticably better error reporting from warn() and die(). This is especially useful if you are using eval().
Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and DiePreHandler, that when you construct them return closures that can be stored in variables that in turn get invoked by $SIG{__DIE__} and $SIG{__WARN__}. Note that if Religion is in use, you should not modify $SIG{__DIE__} or $SIG{__WARN__}, unless you are careful about invoking chaining to the old handler.
Religion also provides a TraceBack function, which is used by a DieHandler after you die() to give a better handle on the current scope of your situation, and provide information about where you were, which might influence where you want to go next, either returning back to where you were, or going on to the very last. [Sorry - Ed.]
See below for usage and examples.
USAGE
DieHandler SUB
Invoke like this:
$Die::Handler = new DieHandler sub {
#...
};
where #... contains your handler code. Your handler will receive the following arguments:
$message, $full_message, $level, $eval,
$iline, $ifile, $oline, $ofile, $oscope
$message is the message provided to die(). Note that the default addition of " at FILE line LINE.n" will have been stripped off if it was present. If you want to add such a message back on, feel free to do so with $iline and $ifile.
$full_message) is the message with a scope message added on if there was no newline at the end of $message. Currently, this is not the original message that die() tacked on, but something along the lines of " at line 3 of the eval at line 4 of Foo.pln".
$eval is non-zero if the die() was invoked inside an eval.
The rest of the arguments are explained in the source for Religion::TraceBack. Yes, I need to document these, but not just now, for they are a pain to explain.
Whenever you install a DieHandler, it will automatically store the current value of $Die::Handler so it can chain to it. If you want to install a handler only temporarily, use local().
If your handler returns data using return or by falling off the end, then the items returns will be used to fill back in the argument list, and the next handler in the chain, if any, will be invoked. Dont fall off the end if you dont want to change the error message.
If your handler exits using last, then no further handlers will be invoked, and the program will die immediatly.
If your handler exits using next, then the next handler in the chain will be invoked directly, without giving you a chance to change its arguments as you could if you used return.
If your handler invokes die(), then die() will proceed as if no handlers were installed. If you are inside an eval, then it will exit to the scope enclosing the eval, otherwise it will exit the program.
WarnHandler SUB
Invoke like this:
$Warn::Handler = new WarnHandler sub {
#...
};
For the rest of its explanation, see DieHandler, and subsitute warn() for die(). Note that once the last DieHandler completes (or last is invoked) then execution will return to the code that invoked warn().
DiePreHandler SUB
Invoke like this:
$Die::PreHandler = new DiePreHandler sub {
#...
};
This works identically to $Die::Handler, except that it forms a separate chain that is invoked before the DieHandler chain. Since you can use last to abort all the handlers and die immediately, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages from further handling.
This is even more useful in $Warn::PreHandler, since you can just throw away warnings that you know arent needed.
WarnPreHandler SUB
Invoke like this:
$Warn::PreHandler = new WarnPreHandler sub {
#...
};
This works identically to $Warn::Handler, except that it forms a separate chain that is invoked before the WarnHandler chain. Since you can use last to abort all the handlers and return to the program, or change the messages or scope details, this can be useful for modifying data that all future handlers will see, or to dispose of some messages.
This is very useful, since you can just throw away warnings that you know arent needed.
Download (0.005MB)
Added: 2007-05-24 License: Perl Artistic License Price:
883 downloads
Module::Install::Philosophy 0.67
Module::Install::Philosophy Perl module contains the concepts behind Module::Install. more>>
Module::Install::Philosophy Perl module contains the concepts behind Module::Install.
SYNOPSIS
This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.
The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.
This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?
As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.
One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.
These are the current problems that I see with CPAN and the core modules:
New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.
I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.
One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.
CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.
<<lessSYNOPSIS
This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.
The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.
This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?
As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.
One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.
These are the current problems that I see with CPAN and the core modules:
New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.
I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.
One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.
CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.
Download (0.080MB)
Added: 2007-06-25 License: Perl Artistic License Price:
851 downloads
Postal 2: Share the Pain DEMO 1407
Postal 2: Share the Pain DEMO is a FPS game for Linux. more>> <<less
Download (167.3MB)
Added: 2006-03-17 License: Freeware Price:
1015 downloads
Americas Army Dedicated Server for Linux 2.5.0 to 2.6.0 Patch
America?s Army is one of the five most popular action games played online. more>>
Americas Army is one of the five most popular action games played online. It provides players with the most authentic military experience available, from exploring the development of Soldiers in individual and collective training to their deployment in simulated missions in the War on Terror.
Americas Army: Special Forces is the follow-up to Americas Army: Operations, which was released on July 4, 2002.
In Americas Army: Special Forces, players attempt to earn Green Beret status by completing individual and collective training missions drawn from the Special Forces Assignment and Selection (SFAS) process.
Players who complete the SFAS process have the opportunity to take on elite Special Forces roles and are qualified to play in multiplayer missions with units ranging from the elite 82d Airborne Division to the 75th Ranger Regiment.
Includes the complete game Americas Army: Operations.
Main features:
- Authentic U.S. Army experience Realistic depiction of the values, units, equipment and career opportunities that make the Army the worlds premier land force continually updated to incorporate new occupations, units, technologies and adventures.
- Realistic roles Including Weapons Specialist (18B), Intelligence (18F), Engineer (18C), Communications (18E) and Combat Medic (18D).
- Challenging Green Beret training Complete training missions drawn from the SFAS process at Fort Bragg. Successfully complete SFAS and advance to Special Forces Qualification Course (Q-Course) missions to explore new Special Forces roles.
- Intense Special Forces action Intense Special Forces action Experience multiplayer missions in simulated combat environments. Take part in missions that span the capabilities of a Special Forces detachment, including unconventional warfare, direct action, surveillance and reconnaissance and Combat Search and Rescue.
- Detailed Special Forces equipment and military hardware Building on the equipment available in Americas Army: Operations, Americas Army: Special Forces adds the M4 Carbine featuring the Picatinny rail mod system for attaching laser-aiming devices and sighting systems; the MP5SD6 Remington 870 shotgun for forced entry; the AT4, a shoulder-fired anti-tank rocket and the BDM, a shoulder-fired bunker demolition munition.
- Accurate Soldier behavior Players are bound by the laws of land warfare, Army values (honor, duty and integrity) and realistic rules of engagement as they navigate challenges in teamwork-based multiplayer force vs. force operations. Mission accomplishment standings are evaluated based on team effort and adherence to a set of values and norms of conduct.
<<lessAmericas Army: Special Forces is the follow-up to Americas Army: Operations, which was released on July 4, 2002.
In Americas Army: Special Forces, players attempt to earn Green Beret status by completing individual and collective training missions drawn from the Special Forces Assignment and Selection (SFAS) process.
Players who complete the SFAS process have the opportunity to take on elite Special Forces roles and are qualified to play in multiplayer missions with units ranging from the elite 82d Airborne Division to the 75th Ranger Regiment.
Includes the complete game Americas Army: Operations.
Main features:
- Authentic U.S. Army experience Realistic depiction of the values, units, equipment and career opportunities that make the Army the worlds premier land force continually updated to incorporate new occupations, units, technologies and adventures.
- Realistic roles Including Weapons Specialist (18B), Intelligence (18F), Engineer (18C), Communications (18E) and Combat Medic (18D).
- Challenging Green Beret training Complete training missions drawn from the SFAS process at Fort Bragg. Successfully complete SFAS and advance to Special Forces Qualification Course (Q-Course) missions to explore new Special Forces roles.
- Intense Special Forces action Intense Special Forces action Experience multiplayer missions in simulated combat environments. Take part in missions that span the capabilities of a Special Forces detachment, including unconventional warfare, direct action, surveillance and reconnaissance and Combat Search and Rescue.
- Detailed Special Forces equipment and military hardware Building on the equipment available in Americas Army: Operations, Americas Army: Special Forces adds the M4 Carbine featuring the Picatinny rail mod system for attaching laser-aiming devices and sighting systems; the MP5SD6 Remington 870 shotgun for forced entry; the AT4, a shoulder-fired anti-tank rocket and the BDM, a shoulder-fired bunker demolition munition.
- Accurate Soldier behavior Players are bound by the laws of land warfare, Army values (honor, duty and integrity) and realistic rules of engagement as they navigate challenges in teamwork-based multiplayer force vs. force operations. Mission accomplishment standings are evaluated based on team effort and adherence to a set of values and norms of conduct.
Download (126MB)
Added: 2006-02-24 License: Freeware Price:
1337 downloads
service menu management to kcontrol 2
service menu management to kcontrol is a service menu suggested idea for kcontrol. more>>
I suggested a kcontrol option for enabling and disabling ACTIONS for different file types. This way, service menus would be installed and managed easier (if that control center window has that function too,it would be nice) aand maybe you will have the option to choose which actions that KIM (kde image service menu)(for example) is capable of is shown in your right click menu when you choose a jpg file...
Also an option to install the service menu just for the user that opened kcontrol (somewhere in /home/~/.kde/.../konqueror/services...) or for all users [the checkbox],requiring a root password (to copy the needed files in the needed by the service menu directories)...
Also the service menu management control center should have the option to move up and down a service menu in the -right-click-ACTIONS> sub menu.
There should be the option to pick selectably the submenus from the installed service menu and add only the ones you would like to have for the file type(for instance you can add kim-resize picture and under it you can take a submenu from a k3b service menu (add to data disc) and put it right under it for the jpg filetype (see the screenshot).
Some service menus,like kims selected "webexport" should have a > sign at the end of their names,showing that they have an included submenu,that cannot be picked/changes sepparatelly.So if web export is added,you dont have the option to pick which webexport options should be included in the web export submenu (we have to have some borders,right?)..
Another suggestion is that if a service menu is installed for all users (using the root password),it should be marked with red fonts in the service list and if promped for uninstallation,it should ofcourse ask for the root password.
And...since the kde service menus were handled the old fashionate way since this idea popped into my mind (with install.sh scripts that coppied a bunch of files,orr by hand with a READme instruction (which is a pain in the neck really)),service menus should be able to be installed the old fashionate way too,but they should be packed in special kde service menu packages,that are handled by kcontrol.This would greatly improve kdes support for service menus.
This will also resolve the clutterness/bloatness that some service menus tend to create,giving the choice in the hands of the user as to what from the service menu he/she would like to be included in the right-click menu.
Enhancements:
- added a new mockup,which is more simple and intuitive
<<lessAlso an option to install the service menu just for the user that opened kcontrol (somewhere in /home/~/.kde/.../konqueror/services...) or for all users [the checkbox],requiring a root password (to copy the needed files in the needed by the service menu directories)...
Also the service menu management control center should have the option to move up and down a service menu in the -right-click-ACTIONS> sub menu.
There should be the option to pick selectably the submenus from the installed service menu and add only the ones you would like to have for the file type(for instance you can add kim-resize picture and under it you can take a submenu from a k3b service menu (add to data disc) and put it right under it for the jpg filetype (see the screenshot).
Some service menus,like kims selected "webexport" should have a > sign at the end of their names,showing that they have an included submenu,that cannot be picked/changes sepparatelly.So if web export is added,you dont have the option to pick which webexport options should be included in the web export submenu (we have to have some borders,right?)..
Another suggestion is that if a service menu is installed for all users (using the root password),it should be marked with red fonts in the service list and if promped for uninstallation,it should ofcourse ask for the root password.
And...since the kde service menus were handled the old fashionate way since this idea popped into my mind (with install.sh scripts that coppied a bunch of files,orr by hand with a READme instruction (which is a pain in the neck really)),service menus should be able to be installed the old fashionate way too,but they should be packed in special kde service menu packages,that are handled by kcontrol.This would greatly improve kdes support for service menus.
This will also resolve the clutterness/bloatness that some service menus tend to create,giving the choice in the hands of the user as to what from the service menu he/she would like to be included in the right-click menu.
Enhancements:
- added a new mockup,which is more simple and intuitive
Download (0.72MB)
Added: 2006-09-18 License: GPL (GNU General Public License) Price:
1137 downloads
Albatross 1.36
Albatross is a small and flexible Python toolkit for developing highly stateful web applications. more>>
Albatross library is a small and flexible Python toolkit for developing highly stateful web applications.
The toolkit has been designed to take a lot of the pain out of constructing intranet applications although you can also use Albatross for deploying publicly accessed web applications.
In slightly less than 2600 lines of Python (according to pycount), you get the following:
An extensible HTML templating system similar to DTML that promotes separation of presentation and implementation for improved program maintainability. The templating system includes tags for:
- Conditional processing,
- Macro definition and expansion,
- Sequence iteration and pagination,
- Tree browsing,
Lookup tables to translate Python values to arbitrary template text. The ability to place Python code for each page in a dynamically loaded module, or to place each page in its own class in a single mainline.
Optional sessions, which can be either:
- Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),
- Server-side sessions via a supplied TCP session server,
- Server-side file based session store.
Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.
Over 120 pages of documentation including many installable samples. A primary design goal of Albatross is that it be small and easy to use and extend. The toolkit application functionality is defined by a collection of fine grained mixin classes. Eight different application types and four different execution contexts are prepackaged, allowing you to define your own drop in replacements for any of the mixins to alter any aspect of the toolkit semantics.
Object Craft developed Albatross because there was nothing available with the same capabilities which they could use for consulting work. For this reason the toolkit is important to Object Craft and so is actively maintained and developed.
Albatross is licensed under a liberal BSD open-source license.
Enhancements:
- Improvements and fixes were made to < al-for >, < al-macro >, < al-option >, NameRecorderMixin, and the FastCGI driver.
<<lessThe toolkit has been designed to take a lot of the pain out of constructing intranet applications although you can also use Albatross for deploying publicly accessed web applications.
In slightly less than 2600 lines of Python (according to pycount), you get the following:
An extensible HTML templating system similar to DTML that promotes separation of presentation and implementation for improved program maintainability. The templating system includes tags for:
- Conditional processing,
- Macro definition and expansion,
- Sequence iteration and pagination,
- Tree browsing,
Lookup tables to translate Python values to arbitrary template text. The ability to place Python code for each page in a dynamically loaded module, or to place each page in its own class in a single mainline.
Optional sessions, which can be either:
- Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),
- Server-side sessions via a supplied TCP session server,
- Server-side file based session store.
Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.
Over 120 pages of documentation including many installable samples. A primary design goal of Albatross is that it be small and easy to use and extend. The toolkit application functionality is defined by a collection of fine grained mixin classes. Eight different application types and four different execution contexts are prepackaged, allowing you to define your own drop in replacements for any of the mixins to alter any aspect of the toolkit semantics.
Object Craft developed Albatross because there was nothing available with the same capabilities which they could use for consulting work. For this reason the toolkit is important to Object Craft and so is actively maintained and developed.
Albatross is licensed under a liberal BSD open-source license.
Enhancements:
- Improvements and fixes were made to < al-for >, < al-macro >, < al-option >, NameRecorderMixin, and the FastCGI driver.
Download (0.25MB)
Added: 2007-03-19 License: Python License Price:
950 downloads
PAiN 0.46
PAiN is a new MUD code base written in Java. more>>
PAiN project is a new MUD code base written in Java.
PAiN is a new MUD codebase written in Java. It provides a general purpose persistence engine (PAiN DB) and the ability to do dynamic code reloading.
Main features:
- Pure Java database engine (transparent constant-time object access, tracking of the dirty state, transactions and savepoints support).
- Static server code (connection handling, support for code reloading and base interfaces).
- Dynamic reloadable set of action classes and plugins (virtual world logic code and plugins).
- Graphical tool to administrate server and database
Enhancements:
- PAiNDB: Collections could be saved separately from object image.This option should be used if collection is not the only field of dbobject, it has size of 20-40 items and dbobject fields are changed often. Saving collection separately will reduce flushing and object backup time inside transactions.
- PAiNDB: DbObject.provideSchema() is now static method and required for all non-abstract DBObject impls. This allows to import class schema into db without object instantiation.
- GUITool: fully rewritten, modules concept added.
- Codebase: more admin console commands.
- Tinylyb: roles removed: Reset, ResetGroup. SpaceGroup was renamed to Area.
- Tinylib: more shell implemented(this shell should be used to show multipage output)
- Tinylib: online builder bugfixing.
- PAiNDB: fixed bug with error on objects removal with non-empty StringMap type fields.
- Tinylib: bugs in @build mode fixed. More complete visualization for array-type fields
- Tinylib: number of small enhancements.
<<lessPAiN is a new MUD codebase written in Java. It provides a general purpose persistence engine (PAiN DB) and the ability to do dynamic code reloading.
Main features:
- Pure Java database engine (transparent constant-time object access, tracking of the dirty state, transactions and savepoints support).
- Static server code (connection handling, support for code reloading and base interfaces).
- Dynamic reloadable set of action classes and plugins (virtual world logic code and plugins).
- Graphical tool to administrate server and database
Enhancements:
- PAiNDB: Collections could be saved separately from object image.This option should be used if collection is not the only field of dbobject, it has size of 20-40 items and dbobject fields are changed often. Saving collection separately will reduce flushing and object backup time inside transactions.
- PAiNDB: DbObject.provideSchema() is now static method and required for all non-abstract DBObject impls. This allows to import class schema into db without object instantiation.
- GUITool: fully rewritten, modules concept added.
- Codebase: more admin console commands.
- Tinylyb: roles removed: Reset, ResetGroup. SpaceGroup was renamed to Area.
- Tinylib: more shell implemented(this shell should be used to show multipage output)
- Tinylib: online builder bugfixing.
- PAiNDB: fixed bug with error on objects removal with non-empty StringMap type fields.
- Tinylib: bugs in @build mode fixed. More complete visualization for array-type fields
- Tinylib: number of small enhancements.
Download (0.33MB)
Added: 2006-12-19 License: GPL (GNU General Public License) Price:
1039 downloads
Americas Army v2.8.0 (Coalition) with Dedicated Server for Linux
Americas Army is one of the five most popular action games played online. more>>
Americas Army is one of the five most popular action games played online. It provides players with the most authentic military experience available, from exploring the development of Soldiers in individual and collective training to their deployment in simulated missions in the War on Terror.
Americas Army: Special Forces is the follow-up to Americas Army: Operations, which was released on July 4, 2002.
In Americas Army: Special Forces, players attempt to earn Green Beret status by completing individual and collective training missions drawn from the Special Forces Assignment and Selection (SFAS) process.
Players who complete the SFAS process have the opportunity to take on elite Special Forces roles and are qualified to play in multiplayer missions with units ranging from the elite 82d Airborne Division to the 75th Ranger Regiment.
Includes the complete game Americas Army: Operations.
Main features:
- Authentic U.S. Army experience Realistic depiction of the values, units, equipment and career opportunities that make the Army the worlds premier land force continually updated to incorporate new occupations, units, technologies and adventures.
- Realistic roles Including Weapons Specialist (18B), Intelligence (18F), Engineer (18C), Communications (18E) and Combat Medic (18D).
- Challenging Green Beret training Complete training missions drawn from the SFAS process at Fort Bragg. Successfully complete SFAS and advance to Special Forces Qualification Course (Q-Course) missions to explore new Special Forces roles.
- Intense Special Forces action Intense Special Forces action Experience multiplayer missions in simulated combat environments. Take part in missions that span the capabilities of a Special Forces detachment, including unconventional warfare, direct action, surveillance and reconnaissance and Combat Search and Rescue.
- Detailed Special Forces equipment and military hardware Building on the equipment available in Americas Army: Operations, Americas Army: Special Forces adds the M4 Carbine featuring the Picatinny rail mod system for attaching laser-aiming devices and sighting systems; the MP5SD6 Remington 870 shotgun for forced entry; the AT4, a shoulder-fired anti-tank rocket and the BDM, a shoulder-fired bunker demolition munition.
- Accurate Soldier behavior Players are bound by the laws of land warfare, Army values (honor, duty and integrity) and realistic rules of engagement as they navigate challenges in teamwork-based multiplayer force vs. force operations. Mission accomplishment standings are evaluated based on team effort and adherence to a set of values and norms of conduct.
<<lessAmericas Army: Special Forces is the follow-up to Americas Army: Operations, which was released on July 4, 2002.
In Americas Army: Special Forces, players attempt to earn Green Beret status by completing individual and collective training missions drawn from the Special Forces Assignment and Selection (SFAS) process.
Players who complete the SFAS process have the opportunity to take on elite Special Forces roles and are qualified to play in multiplayer missions with units ranging from the elite 82d Airborne Division to the 75th Ranger Regiment.
Includes the complete game Americas Army: Operations.
Main features:
- Authentic U.S. Army experience Realistic depiction of the values, units, equipment and career opportunities that make the Army the worlds premier land force continually updated to incorporate new occupations, units, technologies and adventures.
- Realistic roles Including Weapons Specialist (18B), Intelligence (18F), Engineer (18C), Communications (18E) and Combat Medic (18D).
- Challenging Green Beret training Complete training missions drawn from the SFAS process at Fort Bragg. Successfully complete SFAS and advance to Special Forces Qualification Course (Q-Course) missions to explore new Special Forces roles.
- Intense Special Forces action Intense Special Forces action Experience multiplayer missions in simulated combat environments. Take part in missions that span the capabilities of a Special Forces detachment, including unconventional warfare, direct action, surveillance and reconnaissance and Combat Search and Rescue.
- Detailed Special Forces equipment and military hardware Building on the equipment available in Americas Army: Operations, Americas Army: Special Forces adds the M4 Carbine featuring the Picatinny rail mod system for attaching laser-aiming devices and sighting systems; the MP5SD6 Remington 870 shotgun for forced entry; the AT4, a shoulder-fired anti-tank rocket and the BDM, a shoulder-fired bunker demolition munition.
- Accurate Soldier behavior Players are bound by the laws of land warfare, Army values (honor, duty and integrity) and realistic rules of engagement as they navigate challenges in teamwork-based multiplayer force vs. force operations. Mission accomplishment standings are evaluated based on team effort and adherence to a set of values and norms of conduct.
Download (2100MB)
Added: 2007-01-08 License: Freeware Price:
1019 downloads
Firefox for Linux 2.0.0.6
Mozilla Firefox 2 for Linux version. more>> Mozilla Firefox is a fast, full-featured Web browser that makes browsing more efficient than ever before. Firefox includes pop-up blocking; a tab-browsing; integrated Google searching; simplified privacy controls that let you cover your tracks more effectively; a streamlined browser window that shows you more of the page than any other browser; and a number of additional features that work with you to help you get the most out of your time online.
Session Restore
Losing your place while youre doing things on the Web is a pain. Now, with Session Restore, if Firefox has to restart or closes when it comes back youll pick up exactly where you left off. The windows and tabs you were using, the text you typed into forms, and the in-progress downloads you had running will all be restored. You can even set Firefox 2 to always restore your previous session instead of loading a home page, so youll never lose your place again.
Web Feeds (RSS)
What do news headlines, indie rock podcasts, and pictures of kittens have in common? Theyre all things that you can subscribe to with Web feeds. Firefox 2 gives you full control over Web feeds, showing you a preview and letting you choose how you want to subscribe. You can use a Firefox Live Bookmark, or a feed reader that youve installed on your computer, or through a Web service such as My Yahoo!, Bloglines or Google Reader.
Firefox for Linux System Requirements
Please note that Linux distributors may provide packages for your distribution which have different requirements.
Linux kernel - 2.2.14 with the following libraries or packages minimums:
glibc 2.3.2
gtk+2.0
XFree86-3.3.6
fontconfig (also known as xft)
libstdc++5
Thunderbird has been tested on Linux Fedora Core 4<<less
Download (9.22MB)
Added: 2009-04-18 License: Freeware Price: Free
213 downloads
Trophy 1.1.5
Trophy project is an action car racing game. more>>
Trophy project is an action car racing game.
Trophy is an action car racing game for Linux. Its 2D (top-view) but aims to provide high quality graphics.
You can shoot, drop bombs, and drive against the other players.
<<lessTrophy is an action car racing game for Linux. Its 2D (top-view) but aims to provide high quality graphics.
You can shoot, drop bombs, and drive against the other players.
Download (8.9MB)
Added: 2007-08-08 License: GPL (GNU General Public License) Price:
820 downloads
Rails Live CD 0.2.1
Rails Live CD is based on PCLinuxOS which is a great Linux distribution for creating LiveCDs. more>>
Rails Live CD project was born on Ezra Zygmuntowicz blog and realized with help from Brian Ketelsen. Rails Live CD is based on PCLinuxOS which is a great Linux distribution for creating LiveCDs. More information at PCLinusOS.com
To use it, just download, burn and reboot! Or if you have a virtualization or emulation engine like Qemu, Parallels or VMWare it is even easier.
Many people are curious about Ruby on Rails but dont want to go through the pain of installing it locally. The Rails Live CD solves this problem by allowing you to have a fully operating Ruby on Rails development environment without even touching your hard drive!
Others are interested in developing Ruby on Rails applications in Linux but dont have the skills or the patience to do the installation and compiling required to get Ruby on Rails running on a typical Linux installation.
Rails Live CD allows you to install directly to your hard drive and walks you through the process. No compiling or ./configure ./make ./make install dancing required.
Enhancements:
- Rails 1.1.16
- RadRails 0.7.1
- jEdit
- emacs
- Subversion
- MySQL 5 & MySQL Administrator
- SQLite
- PostgreSQL 8
- Firefox 1.5 with several web development extensions
- Gems : ZenTest, Rake, Rails, OpenID, Mogrel, Capistrano
- KDevelop, Kate
- TightVNC
<<lessTo use it, just download, burn and reboot! Or if you have a virtualization or emulation engine like Qemu, Parallels or VMWare it is even easier.
Many people are curious about Ruby on Rails but dont want to go through the pain of installing it locally. The Rails Live CD solves this problem by allowing you to have a fully operating Ruby on Rails development environment without even touching your hard drive!
Others are interested in developing Ruby on Rails applications in Linux but dont have the skills or the patience to do the installation and compiling required to get Ruby on Rails running on a typical Linux installation.
Rails Live CD allows you to install directly to your hard drive and walks you through the process. No compiling or ./configure ./make ./make install dancing required.
Enhancements:
- Rails 1.1.16
- RadRails 0.7.1
- jEdit
- emacs
- Subversion
- MySQL 5 & MySQL Administrator
- SQLite
- PostgreSQL 8
- Firefox 1.5 with several web development extensions
- Gems : ZenTest, Rake, Rails, OpenID, Mogrel, Capistrano
- KDevelop, Kate
- TightVNC
Download (587.7MB)
Added: 2006-10-19 License: GPL (GNU General Public License) Price:
1101 downloads
gladder 1.2.0.2 for Firefox
gladder is an extension that eases the pain of Internet censorship in mainland China. more>>
gladder is an extension that eases the pain of Internet censorship in mainland China.
Get over Great Firewall with Great Ladder!
This extension eases the pain of Internet censorship in mainland China.
Main features:
- Automatically try to open a banned page with a online proxy after you entered the address
- Only auto-redirects pages when you are not using a proxy
- Automatically redirects banned links to visitable URLs in ThunderBird
- If you failed to open a page, click the button on the status bar, it will use a default online proxy to open the page
- List of banned pages is being updated from the Internet every hour
<<lessGet over Great Firewall with Great Ladder!
This extension eases the pain of Internet censorship in mainland China.
Main features:
- Automatically try to open a banned page with a online proxy after you entered the address
- Only auto-redirects pages when you are not using a proxy
- Automatically redirects banned links to visitable URLs in ThunderBird
- If you failed to open a page, click the button on the status bar, it will use a default online proxy to open the page
- List of banned pages is being updated from the Internet every hour
Download (0.010MB)
Added: 2007-07-19 License: MPL (Mozilla Public License) Price:
830 downloads
Apt-get Install / Remove Packet 1.0
Apt-get Install / Remove Packet is a tool to install/remove packets with debian apt-get. more>>
Apt-get Install / Remove Packet is a tool to install/remove packets with debian apt-get.
About Apt-Get:
Advanced Packaging Tool, or APT, is a package management system used by Debian and its derivatives. APT was originally designed to work with .deb packages on Debian systems, but it has since been modified to work with RPM packages via apt-rpm, and to run on other operating systems such as Mac OS X (see fink). On systems with package management based on .deb, such as Debian, APT is a front-end for dpkg.
APT simplifies the process of installing and removing software on Unix systems, by automating the retrieval, (from the Internet, local network, or CD) the configuration, the compiling (sometimes) and the installation of software from APT sources.
There is no apt program per se; APT is a C++ library of functions that are used by several command line programs for dealing with packages, most notably apt-get and apt-cache.
APT front-ends can upgrade the system or specific packages. Packages can be installed or removed. When installing one or several packages, APT front-ends can list the dependencies of these packages, ask the administrator if packages recommended or suggested by newly installed packages should be installed too, automatically install dependencies and perform other operations on the systems packages to allow the installation of the packages. Similarly, to update one or several packages, front-ends can install, remove or update other packages.
APT is often hailed as one of Debians best features, giving Debian the reputation of being a "pain to install, but a joy to maintain", although with Debian 3.1 and its Debian-Installer, Debians installation might be too easy nowadays to keep this true.
<<lessAbout Apt-Get:
Advanced Packaging Tool, or APT, is a package management system used by Debian and its derivatives. APT was originally designed to work with .deb packages on Debian systems, but it has since been modified to work with RPM packages via apt-rpm, and to run on other operating systems such as Mac OS X (see fink). On systems with package management based on .deb, such as Debian, APT is a front-end for dpkg.
APT simplifies the process of installing and removing software on Unix systems, by automating the retrieval, (from the Internet, local network, or CD) the configuration, the compiling (sometimes) and the installation of software from APT sources.
There is no apt program per se; APT is a C++ library of functions that are used by several command line programs for dealing with packages, most notably apt-get and apt-cache.
APT front-ends can upgrade the system or specific packages. Packages can be installed or removed. When installing one or several packages, APT front-ends can list the dependencies of these packages, ask the administrator if packages recommended or suggested by newly installed packages should be installed too, automatically install dependencies and perform other operations on the systems packages to allow the installation of the packages. Similarly, to update one or several packages, front-ends can install, remove or update other packages.
APT is often hailed as one of Debians best features, giving Debian the reputation of being a "pain to install, but a joy to maintain", although with Debian 3.1 and its Debian-Installer, Debians installation might be too easy nowadays to keep this true.
Download (0.032MB)
Added: 2006-03-22 License: GPL (GNU General Public License) Price:
1319 downloads
stephanie 3.0
stephanie is a program for hardening OpenBSD for multiuser environments. more>>
stephanie is a program for hardening OpenBSD for multiuser environments.
Mmmmm, OpenBSD. Functional, secure, free. With an emphasis on security and integrated cryptography, it carries an excellent reputation for plain old "you-just-cant-hack-this-ness". Not perfect, but nothing is, at least theyre not wearing suits and lying to you.
There are a few roles where i believe OpenBSD fits perfectly. One of these is in multiuser environments, where you have large numbers of possibly malicious users with local access. Here the OpenBSD teams commitment to auditing and fixing code provides a level trust in the environment which is hard to find elsewhere. Also, their efforts to provide integrated cryptography means setting up secure access is easy. So, lets take advantage of the freely available source and tailor it to our specific needs.
Details:
In Phrack 54, route|Mike Schiffman wrote a series of patches for OpenBSD 2.4 for Trusted Path Execution (TPE). Stephanie brings a modified version of these up to speed for OpenBSD 2.8 - 3.0, along with some additional features. A trusted path is one where the parent directory is owned by root and is neither group or other writeable. The TPE works off an internal list of trusted user ids. If a given user tries to execute a file not in a trusted path, and their user id is not in the kernels trusted list, they are denied execution privileges. In real terms, this means they cant download, compile and run krad-sploit.c.
In addition to the TPE, a series of privacy patches came along too. Originally supplied as patches for the individual utilities, these are now implemented through kvm(3), and honour trusted users (ie, trusted users are allowed to see all system information). As a practical example, this means that untrusted users will only be able to see information about processes they own, and the stat tools (netstat, iostat, vmstat, etc) will generally be broken for them. It has been pointed out that by going through trying to kill every possible process id you can find other users processes, but you cant really gain any information on them, so this is not really a great concern.
The original TPE patches had one known way of bypassing the execution restrictions, which was using shell redirection to allow arbitrary interpreted language scripts to be run (perl, sh, etc). This has been fixed up, but could possibly be a big pain in the ass, so please pay attention. When an interpreter is invoked, like most things, it creates a new process group with a job count of one. When a series of commands are connected via the | character on the command line, all the commands belong to the same process group and the job count represents the number of commands eg ps -ax | grep something | awk {print $1} has a job count of three, and the ps, grep and awk processes all belong to the same process group.
The one exception to this is when a user logs in, where we find their shell has its job count set to zero. So how can we use this to prevent shell redirection for a given set of programs? We need to be able to distinguish between ordinary commands and interpreters. At the moment this is done by setting the immutable flag on them. So, in kern_exec(), if we find an untrusted user executing something with the immutable flag set and a job count greater than zero, we flag the process as being potentially dodgy. Then in other system calls we disallow read()ing from fd 0 (stdin) and things like dup2(0, n) if the process has been flagged.
There are two main disadvantages to this. First is the system will need to be brought down to single user mode if the interpreter needs to be patched, and secondly, people will have a hard time suing to an untrusted user. Of course, when a user has shell, they can still type any commands that could otherwise be placed in a shell script, but at the least, this will raise the bar a bit.
Finally, Stephanie brings restricted symbolic links, ala the openwall patches for linux. As time permits, im still working on adding additional features, and will add bits of the openwall stuff i like. The basic goal is to add an extra layer of security without being a monumental pain in the ass to legitimate users, so some things wont be there. I havent added the additional hard link restrictions of the openwall patch, but will do something about this later as time permits.
Installing:
Step by step instructions are presented in the install guide which comes with the source. Read it all first, but its reasonably straight forward. It would be a good idea to read the original article (local copy) if you havent already.
Its distributed under the original two clause BSD license, mess with it all you want, but dont get cranky at me if it breaks something.
You can also read the tpe_adm(8) man page online.
<<lessMmmmm, OpenBSD. Functional, secure, free. With an emphasis on security and integrated cryptography, it carries an excellent reputation for plain old "you-just-cant-hack-this-ness". Not perfect, but nothing is, at least theyre not wearing suits and lying to you.
There are a few roles where i believe OpenBSD fits perfectly. One of these is in multiuser environments, where you have large numbers of possibly malicious users with local access. Here the OpenBSD teams commitment to auditing and fixing code provides a level trust in the environment which is hard to find elsewhere. Also, their efforts to provide integrated cryptography means setting up secure access is easy. So, lets take advantage of the freely available source and tailor it to our specific needs.
Details:
In Phrack 54, route|Mike Schiffman wrote a series of patches for OpenBSD 2.4 for Trusted Path Execution (TPE). Stephanie brings a modified version of these up to speed for OpenBSD 2.8 - 3.0, along with some additional features. A trusted path is one where the parent directory is owned by root and is neither group or other writeable. The TPE works off an internal list of trusted user ids. If a given user tries to execute a file not in a trusted path, and their user id is not in the kernels trusted list, they are denied execution privileges. In real terms, this means they cant download, compile and run krad-sploit.c.
In addition to the TPE, a series of privacy patches came along too. Originally supplied as patches for the individual utilities, these are now implemented through kvm(3), and honour trusted users (ie, trusted users are allowed to see all system information). As a practical example, this means that untrusted users will only be able to see information about processes they own, and the stat tools (netstat, iostat, vmstat, etc) will generally be broken for them. It has been pointed out that by going through trying to kill every possible process id you can find other users processes, but you cant really gain any information on them, so this is not really a great concern.
The original TPE patches had one known way of bypassing the execution restrictions, which was using shell redirection to allow arbitrary interpreted language scripts to be run (perl, sh, etc). This has been fixed up, but could possibly be a big pain in the ass, so please pay attention. When an interpreter is invoked, like most things, it creates a new process group with a job count of one. When a series of commands are connected via the | character on the command line, all the commands belong to the same process group and the job count represents the number of commands eg ps -ax | grep something | awk {print $1} has a job count of three, and the ps, grep and awk processes all belong to the same process group.
The one exception to this is when a user logs in, where we find their shell has its job count set to zero. So how can we use this to prevent shell redirection for a given set of programs? We need to be able to distinguish between ordinary commands and interpreters. At the moment this is done by setting the immutable flag on them. So, in kern_exec(), if we find an untrusted user executing something with the immutable flag set and a job count greater than zero, we flag the process as being potentially dodgy. Then in other system calls we disallow read()ing from fd 0 (stdin) and things like dup2(0, n) if the process has been flagged.
There are two main disadvantages to this. First is the system will need to be brought down to single user mode if the interpreter needs to be patched, and secondly, people will have a hard time suing to an untrusted user. Of course, when a user has shell, they can still type any commands that could otherwise be placed in a shell script, but at the least, this will raise the bar a bit.
Finally, Stephanie brings restricted symbolic links, ala the openwall patches for linux. As time permits, im still working on adding additional features, and will add bits of the openwall stuff i like. The basic goal is to add an extra layer of security without being a monumental pain in the ass to legitimate users, so some things wont be there. I havent added the additional hard link restrictions of the openwall patch, but will do something about this later as time permits.
Installing:
Step by step instructions are presented in the install guide which comes with the source. Read it all first, but its reasonably straight forward. It would be a good idea to read the original article (local copy) if you havent already.
Its distributed under the original two clause BSD license, mess with it all you want, but dont get cranky at me if it breaks something.
You can also read the tpe_adm(8) man page online.
Download (0.014MB)
Added: 2006-03-10 License: GPL (GNU General Public License) Price:
1326 downloads
mop(e)snake 0.5
mop(e) snake is a classic snake game which pits you against all the pain in the world. more>>
mop(e) snake is a classic snake game which pits you against all the pain in the world. mop(e)snake project runs on Linux, Windows, and GP2X.
You can try its innovative one-finger control method or stick with a more traditional style of play.
Playing mop(e)snake
Press any key to start, and use the arrow keys to control your snake. Eat the pain.
Alternatively, you can use the good old fashioned O, P, Q, A key layout you remember from your ZX Spectrum days. You can also redefine the keys by modifying the config file in ~/.mopesnake/config. Figuring out the format of that file is left as an exercise for the reader.
Press ESCAPE on the title screen to enter the menu, which allows you to change the skill level (Easy, Medium or Hard) and the game mode (Normal or One-button). Press ESCAPE during the game to pause or quit.
In one-button mode, press any key to start, and any key to turn in the direction in which the arrow is pointing. Its tricky at first, but try to get into the rhythm. Its quite fun.
Enhancements:
- mop(e)snake now continues to run if the sound fails to initialize.
- The ability to turn music and sound effects on and off has been added.
<<lessYou can try its innovative one-finger control method or stick with a more traditional style of play.
Playing mop(e)snake
Press any key to start, and use the arrow keys to control your snake. Eat the pain.
Alternatively, you can use the good old fashioned O, P, Q, A key layout you remember from your ZX Spectrum days. You can also redefine the keys by modifying the config file in ~/.mopesnake/config. Figuring out the format of that file is left as an exercise for the reader.
Press ESCAPE on the title screen to enter the menu, which allows you to change the skill level (Easy, Medium or Hard) and the game mode (Normal or One-button). Press ESCAPE during the game to pause or quit.
In one-button mode, press any key to start, and any key to turn in the direction in which the arrow is pointing. Its tricky at first, but try to get into the rhythm. Its quite fun.
Enhancements:
- mop(e)snake now continues to run if the sound fails to initialize.
- The ability to turn music and sound effects on and off has been added.
Download (0.37MB)
Added: 2006-12-21 License: GPL (GNU General Public License) Price:
1040 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above pain demolition trophies 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
