Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: root can't access files?
Date: Fri, 29 Aug 2003 14:01:24 -0500	[thread overview]
Message-ID: <20030829190124.GB32327@dbz.icequake.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0308291012180.8182-100000@enm-bo-lt.localdomain>


Hi Bart,

On Fri, Aug 29, 2003 at 10:37:27AM +0100, Bart Oldeman wrote:
> On Thu, 28 Aug 2003, Ryan Underwood wrote:
> 
> > Now, the other scenario is this:  we are root, and startup the bbs as
> > root.  The BBS this time is configured to setuid to another user for the
> > security reasons, so it setuids to 'bbs'.  dosemu is started as 'bbs',
> > but apparently checks the real uid to find where to access ~/.dosemu,
> > tries to write to files in /root/.dosemu which 'bbs' has no permissions
> > for, and quits immediately when it fails.
> 
> No, as far as I can't see simply uses $HOME/.dosemu. I can't see any
> extraction of the home directory name from /etc/passwd.
> 
> The easiest way to workaround would be to start using HOME=/home/bbs

Of course, I was up late and the obvious solution completely escaped me.
For some reason I was thinking the DOSEMU was getting the home directory
from the pwent instead of the environment $HOME.  Silly! :)

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

      reply	other threads:[~2003-08-29 19:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  2:50 root can't access files? Ryan Underwood
2003-08-03  3:01 ` Ryan Underwood
2003-08-04  2:00   ` Ryan Underwood
     [not found]     ` <20030804164736.28318.qmail@web14301.mail.yahoo.com>
2003-08-04 19:11       ` Ryan Underwood
2003-08-04 22:40     ` Bart Oldeman
2003-08-29  4:39       ` Ryan Underwood
2003-08-29  9:37         ` Bart Oldeman
2003-08-29 19:01           ` Ryan Underwood [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030829190124.GB32327@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox