From owner-freebsd-security Fri Aug 23 3:24:12 2002 Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4914837B400; Fri, 23 Aug 2002 03:24:06 -0700 (PDT) Received: from antalya.lupe-christoph.de (pD9E8862A.dip0.t-ipconnect.de [217.232.134.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B24A43E6E; Fri, 23 Aug 2002 03:24:05 -0700 (PDT) (envelope-from lupe@lupe-christoph.de) Received: by antalya.lupe-christoph.de (Postfix, from userid 1000) id D7AF25EB; Fri, 23 Aug 2002 12:24:02 +0200 (CEST) Date: Fri, 23 Aug 2002 12:24:02 +0200 To: Jan Srzednicki Cc: Johan Karlsson , freebsd-bugs@FreeBSD.org, freebsd-security@FreeBSD.org Subject: Re: kern/22142: securelevel does not affect mount Message-ID: <20020823102402.GC26115@lupe-christoph.de> References: <200208230144.g7N1itTB030484@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i From: lupe@lupe-christoph.de (Lupe Christoph) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday, 2002-08-23 at 09:43:15 +0200, Jan Srzednicki wrote: > On Thu, 22 Aug 2002, Johan Karlsson wrote: > > Synopsis: securelevel does not affect mount > > Responsible-Changed-From-To: freebsd-bugs->freebsd-security > > Responsible-Changed-By: johan > > Responsible-Changed-When: Thu Aug 22 18:41:46 PDT 2002 > > Responsible-Changed-Why: > > Lets get -security's opinion about this. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=22142 > I'm afraid changin securelevel's behaviour would break some system schemes > out there, which is rather unwanted thing for -STABLE. One thing we can do > is to wait for MACs in -CURRENT. Maybe a better solution is to add another > sysctl just form mount? Like kern.mount_disabled, which, when set to 1, > cannot be reverted back. It would break my system disk cloning scheme. Currently I mount the cloning targets, rsync the live copy, and umount the clones. That way, they will not need fsck'ing when I need them. NO big thing, though. But on a different (Linux) machine, I write dumps to a Zip drive. The medium is umounted and ejected when it's full, to be replaced by the alternate medium. So I agree a finer grained control is need. Preferably even tunable per device, allowing the Zip drive to be mounted/umounted, but no other device. I haven't looked at -CURRENT at all. How fine grained are those MACs? (Excuse me for not having the time right now to read up on them.) Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | Big Misunderstandings #6398: The Titanic was not supposed to be | | unsinkable. The designer had a speech impediment. He said: "I have | | thith great unthinkable conthept ..." | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message