[1264] in linux-security and linux-alert archive
Re: [linux-security] ncpmount/ncpumount
daemon@ATHENA.MIT.EDU (Alan Cox)
Fri Oct 25 08:50:21 1996
From: Alan Cox <alan@cymru.net>
To: baba@beckman.uiuc.edu
Date: Fri, 25 Oct 1996 09:31:11 +0100 (BST)
Cc: zarq@1stnet.com, linux-security@tarsier.cv.nrao.edu
In-Reply-To: <199610211627.LAA10870@tigger.beckman.uiuc.edu> from "Baba Z Buehler" at Oct 21, 96 11:27:48 am
> > I haven't had a chance to look at the source code yet, but it appears that
> > ncpmount and ncpumount suffer from exactly the same problem that mount and
> > umount did. In fact, the mount exploit that was so widely circulated works
> > with ncpumount with no modifications.
> Wouldn't the best thing to do be to roll ncp(un)mount, smb(un)mount into the
> standard Linux mount command?
Unquestionably. I'm going to look at changing the exact rules Linux
uses to decide if you can mount over something to allow mounting directly
over a current directory. That way mount can cd to the directory to mount
and mount over . (which isnt going to move)
Alan