Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2F1312E2F64 for ; Wed, 16 Jan 2008 13:50:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74183-08 for ; Wed, 16 Jan 2008 13:50:46 -0400 (AST) Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51]) by postgresql.org (Postfix) with ESMTP id C3F372E30F6 for ; Wed, 16 Jan 2008 13:50:42 -0400 (AST) Received: by tamriel.snowman.net (Postfix, from userid 1000) id B1E338407D; Wed, 16 Jan 2008 12:50:41 -0500 (EST) Date: Wed, 16 Jan 2008 12:50:41 -0500 From: Stephen Frost To: Mischa Sandberg Cc: pgsql-hackers@postgresql.org Subject: Re: postgresql in FreeBSD jails: proposal Message-ID: <20080116175041.GQ5031@tamriel.snowman.net> Mail-Followup-To: Mischa Sandberg , pgsql-hackers@postgresql.org References: <1200501702.478e33c61b74e@webmail.telus.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WEb2cH/xkZZxp1fJ" Content-Disposition: inline In-Reply-To: <1200501702.478e33c61b74e@webmail.telus.net> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.6.22-2-amd64 (x86_64) X-Uptime: 12:33:53 up 107 days, 17:46, 26 users, load average: 0.11, 0.05, 0.01 User-Agent: Mutt/1.5.16 (2007-06-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/666 X-Sequence-Number: 112940 --WEb2cH/xkZZxp1fJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Mischa Sandberg (mischa_sandberg@telus.net) wrote: > Here (@sophos.com) we run machine cluster tests using FreeBSD jails. A > jail is halfway between a chroot and a VM. Jails blow a number of > assumptions about a unix environment: sysv ipc's are global to all > jails; but a process can only "see" other processes also running in the > jail. In fact, the quickest way to tell whether you're running in a jail > is to test for process 1. I've got a couple of concerns about this- #1: Having the shared memory be global is a rather large problem when it comes to something like PG which can have a fair bit of data going through that area that could be sensitive. #2: Isn't there already a uid check that's done? Wouldn't this make more sense anyway (and hopefully minimize the impact of a bad person getting control of the PG database/user in a given jail)? #3: At least in the linux-equivilant to jails (linux-vservers, imv anyway), they started w/o an init process and eventually decided it made sense to have one, so I'm not sure that this test will always work and the result might catch someone by suprise at some later date. Is there a better/more explicit test? Thanks, Stephen --WEb2cH/xkZZxp1fJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHjkPxrzgMPqB3kigRAhObAJ9+Uk5Xhz28gP0BG73WgfahMf4S6gCfSFLb FZ2/DoiiOgQkRxax28PTx7E= =kmBm -----END PGP SIGNATURE----- --WEb2cH/xkZZxp1fJ--