#4 fusion subsystem plugins have no type information

[Chris Thomas]

fusion subsystem plugins have no way of identifying
themselves, so fusion knows the subsystem it's loading,
is compatible with the subsystem it's about to assign
it to. which would mean a crash or exploit could be
made, by incorrectly specifying a plugin to the wrong
part of the system. Not good.

a new export is going to be required, since you cannot
put this information into the plugin, cause then it'll
have to be created/loaded in order to gain access to
it. a new export would mean simple a new dll call,
thats it. It should specify that subsystem it's
applicable too, of course that means a problem when it
comes to building a dll, perhaps a malicious hacker
would create a bad plugin deliberately for this
purpose, it's possible, but I'm unsure how to thwart
that kind of attack.

For now a simple export, returning the subsystem the
plugin creates an object of, would suffice for innocent
problems