On Mon, May 27, 2013 at 2:59 AM, Dan Egli <[email protected]> wrote:
> When I asked him to clarify he said > that he wants to ensure that even if someone somehow was able to gain root > access through an exploit (buffer overrun, etc....) that all the hacker > would see is the web pages themselves. He is trying to make unauthorized > access to the files as difficult as possible by adding an additional layer > that the potential hacker would need to go through (in this case, the > Postgres engine). I'm sure there are easier/better ways of accomplishing > that, but I'll admit I drew a blank on what they were. Perhaps you guys > have suggestions? > Make sure he understands if they have root, they have everything. E.g. if the files are in Postgres and someone has the system root, they can reset the Postgres root password ( http://stackoverflow.com/questions/922804/is-there-a-way-to-break-into-a-postgresql-database-if-you-forgot-the-password ). If he's just worried about people accessing the file directly (e.g. yoursiet.com/some/file/path.zip), it's simple to have the file stored outside of the webroot and use your site as a gateway to serve the files. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
