Date: Thu, 18 Jan 2007 09:49:19 -0500 From: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> To: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> Cc: freebsd-current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [RFC] mount(8) can figure out fstype Message-ID: <CFDC5784-69D2-4309-8599-76FF72434EE9@ece.cmu.edu> In-Reply-To: <cb5206420701180614n3eb5bb6cla6c9fdf9ee6f1a9@mail.gmail.com> References: <20070118134936.GA7391@crodrigues.org> <cb5206420701180614n3eb5bb6cla6c9fdf9ee6f1a9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 18, 2007, at 9:14 , Andrew Pantyukhin wrote: > On 1/18/07, Craig Rodrigues <rodrigc@crodrigues.org> wrote: >> In this patch, I only modified the userland mount program. >> If the user does not specify "-t vfstype" to mount, >> the mount program gets a list of local filesystems from the >> vfs.conflist >> sysctl. It then tries to mount the filesystem, always >> starting with "ufs", and then iterating through the list if >> the nmount() fails with EINVAL. > > I would love to have this usability enhancement around! > > 1. Are there any (what are the) security implications? > 2. "mount -t auto" might be closer to POLA ISTR from back when Linux added this that the bigger problem is that the msdos filesystem may sometimes accept filesystems it shouldn't, because the only way to catch an invalid filesystem is heuristics. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CFDC5784-69D2-4309-8599-76FF72434EE9>