Putting a mandatory access block on the player to access the database is exactly what I was talking about. I don't think anyone was suggesting that only Emplode needs to present a password, and other clients (Jemplod etc) would get carte blanche. Obviously the player would have to be the gatekeeper and, if so configured, reject all clients that don't present a password.

I dunno. It's not as much of a concern as the machines I work with here at work. I'd much rather see cool new visualizations and such than password protection.