pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Lamar Owen <lowen@pari.edu>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Silvana Di Martino <silvanadimartino@tin.it>
Cc: Alex Page <alex.page@cancer.org.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Database Encryption (now required by law in Italy)
Date: Sat, 6 Mar 2004 08:55:12 -0500
Message-ID: <200403060855.12265.lowen@pari.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0403051333120.17467-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0403051333120.17467-100000@css120.ihs.com>

On Friday 05 March 2004 03:34 pm, scott.marlowe wrote:
> Sorry, but that's the wrong answer.  Once someone has root on a unix box
> her can do ANYTHING he wants.  and he can cover his tracks. 

This is what things like the capabilities system and SELinux are designed to 
prevent in the Linux world.  As Fedora Core 2 will ship with SELinux 
installed and enabled, it will become much more difficult for someone to 
randomly get root and do damage.  It is quite simple with SELinux to prevent 
any of the attacks you mentioned.  Root is no longer root.  Things on an 
SELinux system, or a system fully implementing the kernel capabilities model, 
can indeed be locked away from root, at least in network attached multiuser 
mode.  This does, of course, make maintenance of the data more difficult; one 
must be at the console in a special mode to do full maintenance.  But someone 
remotely cracking root no longer is the threat they once were, when some 
system like SELinux is in use.
-- 
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC  28772
(828)862-5554
www.pari.edu



view thread (65+ messages)  latest in thread

Message-ID: <200403060855.12265.lowen@pari.edu>
Permalink:  ../200403060855.12265.lowen@pari.edu/
Also on:    postgresql.org/message-id/200403060855.12265.lowen@pari.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: lowen@pari.edu, scott.marlowe@ihs.com, silvanadimartino@tin.it, alex.page@cancer.org.uk
  Subject: Re: Database Encryption (now required by law in Italy)
  In-Reply-To: <200403060855.12265.lowen@pari.edu>
  References: <Pine.LNX.4.33.0403051333120.17467-100000@css120.ihs.com> <200403060855.12265.lowen@pari.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