pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Roberto Mello <rmello@cc.usu.edu>
To: Chad N. Tindel <chad@tindel.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: Mysql -> Postgresql pitfalls
Date: Sat, 2 Aug 2003 15:21:17 -0600
Message-ID: <20030802212117.GA1948@cc.usu.edu> (raw)
In-Reply-To: <20030802171049.GB12300@calma.pair.com>
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>
	<20030802171049.GB12300@calma.pair.com>

On Sat, Aug 02, 2003 at 01:10:49PM -0400, Chad N. Tindel wrote:
> > 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".  

Whoever said there was? I didn't.
 
> > 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.

Nice strawmen. Too bad it's a logical fallacy.
 
> 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

How about people inside the company? Are they all nice people who live in
happy valley?

> get real work done.... they don't want things like "security" to get in the
> way because nobody is trying to hack those machines.

I digress.

-Roberto

-- 
+----|        Roberto Mello   -    http://www.brasileiro.net/  |------+
+       Computer Science Graduate Student, Utah State University      +
+       USU Free Software & GNU/Linux Club - http://fslc.usu.edu/     +
Backup not found: (Q)uem mandou usar o Stacker?



view thread (26+ messages)  latest in thread

Message-ID: <20030802212117.GA1948@cc.usu.edu>
Permalink:  ../20030802212117.GA1948@cc.usu.edu/
Also on:    postgresql.org/message-id/20030802212117.GA1948@cc.usu.edu

 · 

reply

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
  Subject: Re: Mysql -> Postgresql pitfalls
  In-Reply-To: <20030802212117.GA1948@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