Because if it's done that way, the player is still accessable via Jemplode/emptool unless similar locks are put there. Putting a mandatory password block on the player to access the database would seem to be a solution, but then it has to be implemented in JEmplode and emptool.

I'm guessing empeg would want to implement a secure solution, instead of one that simply looks secure from one program. Building the HSX from the ground up made that much more possible, compaired to the empeg code base starting on a device that couldn't speak ethernet. Plus the fact that the HSX will most likely be connected all the time...