[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Tiger-user] Where should tiger grow towards?
From: |
Javier Fernández-Sanguino Peña |
Subject: |
[Tiger-user] Where should tiger grow towards? |
Date: |
Mon, 25 Nov 2002 16:37:39 +0100 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have some ideas as to where Tiger should grow towards but have different
options, developers could be encourage to either:
1.- add new check for new software that is currently not supported. For
example, I have recently added a new 'check_apache' module to check
Apache's configuration [1]
2.- Test Tiger in new platforms and offer platform-specific scripts (such
as patches analysis in Solaris or AIX or the recent check
'check_network_config' I have included for Linux [2] )
3.- Try to integrate tiger better with other software (including
john/crack, integrit/samhain/aide/tripwire, logcheck/loganalysis) or
include a version of such software within Tiger (for user account tests,
filesystem checks or logchecks respectively)
4.- Try to improve the current existing checks with new subtests that might
be relevant.
Since resources are scarse (well, as a matter of fact I'm the only one
updating the CVS sources) I'm afraid that I can work on all the four
directions at the same time so I'm seeking feedback on this issue.
Hello? Anybody out there? :-)
Javi
[1]
http://savannah.nongnu.org/cgi-bin/viewcvs/tiger/tiger/scripts/check_apache
[2]
http://savannah.nongnu.org/cgi-bin/viewcvs/tiger/tiger/systems/Linux/2/check
_network_config
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1.1
iQA/AwUBPeJDv6O1I0N5hzVfEQIhaACfRv2r5usYaVQHmgB0WGtedDTG3rQAn27x
tYVoFvrVhZ5WxCyMBjnRKsW/
=QSb1
-----END PGP SIGNATURE-----
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Tiger-user] Where should tiger grow towards?,
Javier Fernández-Sanguino Peña <=