From: Chad N. Tindel <chad@tindel.net>
To: Roberto Mello <rmello@cc.usu.edu>
Cc: pgsql-docs@postgresql.org
Subject: Re: Mysql -> Postgresql pitfalls
Date: Sat, 2 Aug 2003 13:10:49 -0400
Message-ID: <20030802171049.GB12300@calma.pair.com> (raw)
In-Reply-To: <20030802063346.GA24640@cc.usu.edu>
References: <20030801163555.GA32496@calma.pair.com>
<Pine.LNX.4.33.0308011426280.30340-100000@css120.ihs.com>
<20030801205110.GA63709@calma.pair.com>
<20030802063346.GA24640@cc.usu.edu>
> Hmmm?
>
> The point is something called security.
There is no such thing as a "proper amount of security that is correct for
all operating environments".
> > apache with some BIG_SECURITY_HOLE defined in order to run as root, which means
> > you can't just use the out of the box apache rpm. Its so stupid to write
> > *extra* code that keeps people from doing something that isn't even
> > fundamentally incorrect.</RANT>
>
> This has no logic. Security is fundamental. No security is fundamentally
> incorrect.
Well, you could make a box very secure by unplugging all the LAN cables from
it and putting it in a giant safe deposit box. However, I would say that such
a machine would be fundamentally incorrect for most operating environments.
Do you worry about whether or not someone snuck into your house at night and
installed some sort of keyboard logging device onto your PC so that they can
get your root password? Is that a "fundamental" part of your personal
security? Probably not, because *that* would be illogical for most people to
worry about.
Many people run their machines with "+ +" in root's .rhosts file because it
eases the task of doing administration. They work in a company where the box is
behind a firewall on some public network and they need there computers to
get real work done.... they don't want things like "security" to get in the
way because nobody is trying to hack those machines.
Chad
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-docs@postgresql.org
Cc: chad@tindel.net, rmello@cc.usu.edu
Subject: Re: Mysql -> Postgresql pitfalls
In-Reply-To: <20030802171049.GB12300@calma.pair.com>
* 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