Subversion Repositories vnag

Rev

Rev 2 | Rev 33 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
2 daniel-mar 1
 
32 daniel-mar 2
Important
3
---------
4
 
5
- owncloud_version: Security fix: Parse version.php instead of include it
6
- nextcloud_version: Security fix: Parse version.php instead of include it
7
- New plugin: hp_ssa
8
 
2 daniel-mar 9
TODO
10
----
11
 
12
- make proper documentation
13
- allow changing automatic help page to describe which individual ranges stand for (is it already possible, by getting the argument object and then changing its help text?)
14
- everywhere getter and setter instead of accessing class member variables
15
- ipfm monitor: dygraph has MIT license
16
- *.conf files: /daten sollte nicht in den example conf's stehen. irgendwie anders machen (Aber achtung: wir symlinken die config files in unserem /etc )
17
- idea: a script that converts the output of an EXISTING nagios plugin into VNag Weboutput. So an arbitary Nagios script can be forwarded to other systems over HTTP
18
- make all plugins "web enabled"
19
  In the framework create an easy function, which generates a simple default HTML header and footer
20
- should error details, e.g. defective hard disks at the mdstat monitor be Verbosity=Summary, or Verbosity=AdditionalInformation ?
21
- idea for a new plugin: sudo /daten/scripts/tools/check_etc_perms | grep -v "world readable" | grep -v "world executable"
22
- should putputID, passwordOut and privateKey be a default argument? Then you can use encryption/signing for all plugins by default
23
- In re syntax checking/getopt:
24
  * Evaluate if PHP 7.1 (with getopt()'s $optind) is able to detect unexpected CLI parameters for us (so we can output a syntax warning)
25
  * Limit warning range numbers (avoid user adds too many, e.g. "-w A,B,C" although only 2 are allowed)
26
 
27
Future
28
------
29
 
30
- For arguments (warning/critical), also accept mixed UOMs, e.g. MB and %
31
- In re usage page:
32
  * Automatic creation of usage page. Which arguments are necessary?
33
  * Automatically generate syntax?
34
- Allow individual design via CSS
35
- Check if regex of validateLongOpt() is accurate
36
 
37
Unsure
38
------
39
 
40
- Automatically encrypt/sign via a global config setting?
41
- Should we also allow other UOMs?