On Wed, Jan 26, 2005 at 01:29:53PM -0500, Alex Turner wrote:
> Generaly network security suggests that your database server should
> not allow connections from external addresses (including for services
> like ssh as well as pgsql). iptables can help acheive this if your
> servers are all on publ
Generaly network security suggests that your database server should
not allow connections from external addresses (including for services
like ssh as well as pgsql). iptables can help acheive this if your
servers are all on public IPs (also not a very good idea), otherwise
the best place to config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, that's all fine as long as the hacker does not connect directly
to the database server when attempting his attack. Check it in the app
yes, but if this is really a genuine concern, it should be reinforced
by the server as an added precaution.
On Wed, 2005-01-26 at 00:08 -0700, Michael Fuhr wrote:
> On Wed, Jan 26, 2005 at 12:27:17AM -0600, Dale Sykora wrote:
>
> > I would like to use a text field in a table and limit the size to
> > reduce the chance of denial-of-service/buffer overflow/etc. I assume I
> > can define table field
On Wed, Jan 26, 2005 at 12:27:17AM -0600, Dale Sykora wrote:
> I would like to use a text field in a table and limit the size to
> reduce the chance of denial-of-service/buffer overflow/etc. I assume I
> can define table fields similar to the following
> "field_name text check (len(field)
PostgreSQL users,
I would like to use a text field in a table and limit the size to
reduce the chance of denial-of-service/buffer overflow/etc. I assume I
can define table fields similar to the following
"field_name text check (len(field) < 160)" although my syntax is
probably wrong. Is check
