CVE-Search more modular about cve-search HOT 2 CLOSED

@adulau
I've been thinking on how to do this, and most parts are easy to figure out, but some are a bit more dificult. What I thought of so far is:

• One file (lib.module) is a template for all modules, and will be extended by custom modules
• A module loader will give the users the ability to load or disable modules, even while the server is running (I've written something like this in previous projects, so this will be easy to implement)
• lib.module will contain several functions that can be overwritten by the module, like
  • loadCVEInfo - Gets triggered when you open a /cve/<cveid> page, and returns a subset of the page (for example the notes a user made), or takes other actions, (like marking CVEs as "seen")
  • update - Gets triggered by the updater script, and updates the database info

Things I'm still thinking about are:

• If you want modules to affect the index page data, how can we do this (for example mark as seen)? There are a few things to keep in mind:
  • Colouring entries gray, like the "seen" module, is currently done in the template
  • Extra filters could probably be added dynamically, but layout and functionality of the filters will change
• Modules like "bookmarked CVEs" need their own page. How do we accomplish this (in index.py)?

What's your opinion?

from cve-search.

Plug-in manager implemented in the latest release of CVE-Search (v2.0)

from cve-search.