From: Bruno Wolff III <bruno@wolff.to>
To: brew@theMode.com
Cc: pgsql-novice@postgresql.org
Subject: Re: Storing Large Objects
Date: Mon, 18 Apr 2005 10:21:18 -0500
Message-ID: <20050418152118.GA22606@wolff.to> (raw)
In-Reply-To: <Pine.BSF.4.58.0504180141480.94918@themode.com>
References: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se>
<Pine.BSF.4.58.0504180141480.94918@themode.com>
On Mon, Apr 18, 2005 at 02:09:10 -0400,
brew@theMode.com wrote:
>
> Since I've heard large objects were a bother I've written it so the mp3s
> were in files with long obfuscated filenames and have put them in a
> directory hidden behind basic authentication, planning a php front end to
> the basic authentication and storing the file urls in the database. Now
> I'm considering shortlived symbolic filenames to further make it difficult
> to rip off the mp3 files by other users with valid log in credentials that
> can get past the basic authentication.
Why not put the files somewhere where only the application can get at them
instead of under the document root. That way they have to compromise your
application to get at them. No amount of url guessing will give direct
access.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, brew@theMode.com, pgsql-novice@postgresql.org
Subject: Re: Storing Large Objects
In-Reply-To: <20050418152118.GA22606@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox