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 > Also, is it possible to create the stuff that dosemu would want to > create in .dosemu, somewhere else such as /tmp that the user will always > be able to write to; or else disable creating the sockets and such > entirely? That way, dosemu would not need write permissions anywhere to > start up. With a little experimenting it turns out that read access is enough without any changes to the source code. HOME=/root dosemu.bin -o /dev/null works as long as the user who invokes it can see /root/.dosemu HOME=/tmp dosemu works too. I'm not sure if that's sufficient for you but at least it's something. Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
