Difference between revisions of "ASL Release Schedule"
(→Next Release is: 2.0.4) |
|||
| Line 1: | Line 1: | ||
| − | == Current Release is: 2.0 == | + | == Current Release is: 2.0.6 == |
| − | == Next Release is: 2.0. | + | == Next Release is: 2.0.7 == |
available in [asl-2.0-testing] now | available in [asl-2.0-testing] now | ||
| Line 9: | Line 9: | ||
== Tasks in progress == | == Tasks in progress == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * Extend clamav support to cover email (This is now Complete, and available in asl-2.0-testing) | |
| − | + | ||
| − | + | ||
- Create basic configuration interface for Plesk (PSA will be a dependency) | - Create basic configuration interface for Plesk (PSA will be a dependency) | ||
| Line 32: | Line 23: | ||
[http://www.atomicrocketturtle.com/atomic-scanner3.png Atomic Scanner stats page part 2] | [http://www.atomicrocketturtle.com/atomic-scanner3.png Atomic Scanner stats page part 2] | ||
| − | + | == Feature Candidates == | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == Feature Candidates== | + | |
AtomiCommunity - RBL/Reputation based system to share/use attack/spammer data with ASL community. | AtomiCommunity - RBL/Reputation based system to share/use attack/spammer data with ASL community. | ||
Revision as of 22:25, 27 January 2009
Contents |
Current Release is: 2.0.6
Next Release is: 2.0.7
available in [asl-2.0-testing] now
Tasks in progress
- Extend clamav support to cover email (This is now Complete, and available in asl-2.0-testing)
- Create basic configuration interface for Plesk (PSA will be a dependency)
Screenshots of what we now call "Atomic-Scanner"
Atomic Scanner showing individual user settings
Atomic Scanner stats page part 2
Feature Candidates
AtomiCommunity - RBL/Reputation based system to share/use attack/spammer data with ASL community.
AtomiRBL - Local RBL functionality - to share attack data with trusted nodes (Your boxes basically)
suphp support, this would include some kind of graphical integration with plesk
Add vendor updates to vulnerability checks (ie, did you update your box?). This is a major expansion to the vulnerability checks on the system. Orders of magnitude larger
Enterprise Auditing Shell support. This tracks commands from shell accounts and allows you to replay what happened. Kind of like a tivo.
Expand Active Response blocklist to collect the specific attack event, instead of just the OSSEC rule ID.
Standalone ASL web interface, that does not require plesk. As a bonus, this feature would allow us to password protect the ASL gui in plesk as well.
Firewall gui
