3 projects tagged "bash scripts"
Updated 03 Mar 2011
RedWolf Security Threat Generator
| Pop | 104.31 |
|---|---|
| Vit | 2.64 |
RedWolf is a security threat simulator that tests security system effectiveness. Its threat generation capabilities include email, IM, malware, P2P, social networking, VoIP, DDoS, and many more. The guiding philosophy is that by generating realistic scenarios in a wide variety of categories, an auditor or organization can assess the effectiveness of network defenses. The scenario suite allows one to verify compliance with PCI-DSS, Sarbanes-Oxley, or HIPAA controls. RedWolf helps identify data loss risks and provides expert recommendations concerning risk mitigation. It reports present findings, recommendations, best practices, and blocking guidance in a straightforward, easily readable format. RedWolf also acts as a 'Red Team' agent, running drills to measure the readiness of your operations staff.
Updated 09 Jun 2010
colormake2
| Pop | 19.80 |
|---|---|
| Vit | 32.87 |
colormake2 is a fork of colormake, a program to colorize output from "make" executions, mostly focused on compiler output. This makes it much easier to find the relevant error when compiling a program results in a long list of error messages.
Updated 26 Nov 2011
DUST
| Pop | 14.53 |
|---|---|
| Vit | 23.35 |
DUST (Driver UpdateS Tool) is designed to "just work" for building kernel driver modules. The concept is similar to DKMS, though this has the benefit of being simpler, easier to test and use, and easier to integrate. DUST enables you to package up a driver pack, install it into the dust directory, and prepare for upgrading. Each driver pack has 3 components: an install file (populates a tree with stuff needed to build a working driver); the driver payload (tarball, zip file, etc.); and the update script, which will do nothing but copy the old driver kernel modules to a backup directory, build/install a new copy of the driver kernel, run depmod if needed, and mkinitramfs, mkinitrd, or dracut if needed. The install file is very trivial. It is easy to recode this as an RPM or deb. As long as it moves the driver payload and update script to the right location, you can use any mechanism to do this.
