> It's yet another case of implementations being driven by funding rather than
> requirements.
>
> As you say, a central ban list that sites download periodically would be really
> simple. Simple to use, but the downside is it would have been simple to
> implement, and not something you could write papers about.
>
> You could knock it up in an afternoon rather than spending years on it.
Argus central authorization wasn't written for banning/central security emergency suspension, it was written as an authorization service. The idea of additionally using Argus for central security emergency suspension came later, if my memory serves me correctly.
--
Scanned by iCritical.
|