I haven't played around with molet, so maybe that would suit my needs
better, but I like the web interface of snitch.
Three reasons come to mind as to why I would feel comfortable using
this as a plugin.
1: It's relatively small size and non-complex nature means I can get a
fair amount of understanding as to how it works by looking through it
for a little while. While I may not sit down and read the code line
by line, what I will do (and have done, to some extent) is check
specific things out, either because I'm curious, or because I want to
make some small change to better suit my application (such as the
formatting changes I mentioned in another post).
2: It is an output-only application, which means it is not vunerable
to Cross-Site Scripting or similar exploits.
3: It would be used as a monitoring system, and as such would only be
used by myself, and I trust myself to not to stupid things to the
server, and to tell when something is acting up and should be
investigated.
Really, the one reason I would be reluctant to use it as a plugin is
kind of a moot point. That is: I am uncomfortable giving it access to
my database. Now, that point is fairly moot because, while I could
give snitch-as-a-separate-app read-only access to the database, the
mole plugin itself requires write-access, and it's all written by the
same guy(s), as part of the same project. ..And I think that is really
the main point here: If I give part of the program (the mole part) a
certain access level, why would I not give the other part (snitch)
that same access?
On Apr 20, 8:32 am, "Fernand Galiana" <fernand.gali...@gmail.com>
wrote:
> Hi Patrick,
>
> Actually, we've started down that path initially, by bundling the snitch
> inside the
> mole plugin. Then I've thought that folks may be freaked out to deploy
> our app
> on their production servers ??
>
> -Fernand
>