Re: Shared memory and FreeBSD's jail()

From: Douglas McNaught <doug(at)mcnaught(dot)org>
To: lister <lister(at)primetime(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Shared memory and FreeBSD's jail()
Date: 2005-05-19 15:10:41
Message-ID: m264xf9rpq.fsf@Douglas-McNaughts-Powerbook.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

lister <lister(at)primetime(dot)com> writes:

> At the BSDCan tutorial last week on jails (and several other times)
> there was discussion regarding Postgres's use of system V style
> shared memory, and an unfortunate side effect of making jail() less
> secure. Specifically, to allow Postgres to operate in a jail()ed
> environment, the sysctl :
> jail.sysvipc_allowed=1
> has to be set. This allows ALL jails to access the memory, at the least
> leaving Postgres open to attack, at the worst allowing a door into who
> knows what security breach.
> Question : is there any way to run Postgres securely in a jail?

By your definition, not unless you remove the dependence on SysV
shmem, which would be a lot of work.

-Doug

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-05-19 15:14:09 Re: error explanation
Previous Message tmpmac 2005-05-19 14:49:27 unique index with bool