summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorBjoern Tropf <asymmail@googlemail.com>2009-07-23 20:42:52 +0200
committerBjoern Tropf <asymmail@googlemail.com>2009-07-23 20:42:52 +0200
commit01c57949e986f590a80a8146bcfb517855a23845 (patch)
treeab47505dd5785c57245fb76412ad7335c35a4f4d /TODO
parentBackup commit (diff)
downloadkernel-check-01c57949e986f590a80a8146bcfb517855a23845.tar.gz
kernel-check-01c57949e986f590a80a8146bcfb517855a23845.tar.bz2
kernel-check-01c57949e986f590a80a8146bcfb517855a23845.zip
Change max line length to 79
Start work on documentation Fix some minor bugs Edit the TODO list
Diffstat (limited to 'TODO')
-rw-r--r--TODO54
1 files changed, 9 insertions, 45 deletions
diff --git a/TODO b/TODO
index b6bc596..49b2516 100644
--- a/TODO
+++ b/TODO
@@ -1,52 +1,16 @@
Todo
====
-- Fix all TODO markers
+- Fix all inline TODO/FIXME markers
- Find a solution for <ref source url/>
-- Rename functions
+- Use telling function- and variable names
- Rework interval class and all interval functions (expand?)
- Rework cves.refs
-- class(object) (new class)
- Use exeptions instead of debug()
-- Break lines
-
-Clean code
-==========
-- Use telling variables
-- Use proper Descriptions
-- Remove unused code / find better ways
-- Add error handling
-
-Documentation
-=============
+- Add further error handling
+- [kernel +<version] -> [+kernel <version]
+- Ignore vserver whiteboard
+- Find a way to insert arch into bugzilla
+- Implement find_cve() (return bugid)
+- Write a proper documentation
- Implement DTD
-- Function documentation / manpages
-
-Intervall documentation
-=======================
-
-name: String, the name of the vulnerable release. This can either be "linux" to
- specify the upstream release was vulnerable, "genpatches" (or abbreviated "gp")
- or a specifc ebuild name such as "hppa-sources" (or abbreviated "hppa").
-
-lower: String, the lower boundary.
-
-upper: String, the upper boundary.
-
-lower_inclusive: Boolean, whether or not the lower boundary is inclusive.
-
-upper_inclusive: Boolean, whether or not the upper boundary is inclusive.
-
-expand: Boolean, defines whether the entry is shadowing less specific entries of the same version range:
- linux is less specific than genpatches which is less specific than the name.
- Example:
- (1) [linux >= 2.6.18 < 2.6.24.3] [gp+ >2.6.16-1 < 2.6.23-8]
- (expand=True)
-
- (2) [linux >= 2.6.18 < 2.6.24.3] [gp < 2.6.23-8]
- (expand=False)
-
- In (1), a vulnerability seemingly has been backported to genpatches-2.1.16-1
- and was fixed in 2.6.23-8. A genpatched Kernel 2.6.17 is vulnerable. In (2),
- a patch fixing the vulnerability has been backported to the genpatches.
- Kernels 2.6.17 and earlier are not affected.
-
+- Remove unused code and find better ways