From: Roberto Mello <rmello@cc.usu.edu>
To: Chad N. Tindel <chad@tindel.net>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Mysql -> Postgresql pitfalls
Date: Sat, 2 Aug 2003 00:33:46 -0600
Message-ID: <20030802063346.GA24640@cc.usu.edu> (raw)
In-Reply-To: <20030801205110.GA63709@calma.pair.com>
References: <20030801163555.GA32496@calma.pair.com>
<Pine.LNX.4.33.0308011426280.30340-100000@css120.ihs.com>
<20030801205110.GA63709@calma.pair.com>
On Fri, Aug 01, 2003 at 04:51:11PM -0400, Chad N. Tindel wrote:
>
> <RANT>As a programmer, I personally would never write code that kept people from
> running things as root. I mean, what is the point? If an administrator
Hmmm?
The point is something called security.
> wants to run postgresql or apache as root, why shouldn't they be allowed
> to make that conscious decision for themselves? As it is, you have to recompile
Because administrators have too much to worry about. If an application
makes a conscious decision to allow itself to run in a knowingly insecure
manner, that application is doing the admin a disfavor, and should be
ditched.
> 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.
-Roberto
--
+----| Roberto Mello - http://www.brasileiro.net/ |------+
+ Computer Science Graduate Student, Utah State University +
+ USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ +
---------------/ NO INSPIRATION TODAY /-------------------
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: rmello@cc.usu.edu, chad@tindel.net, scott.marlowe@ihs.com
Subject: Re: Mysql -> Postgresql pitfalls
In-Reply-To: <20030802063346.GA24640@cc.usu.edu>
* 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