From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tftpd vs assumptions about user none? (to have or have
Date: Wed, 26 Jan 2005 21:21:06 -0500 [thread overview]
Message-ID: <ca3eada2f0258994fbe573a288535c96@plan9.bell-labs.com> (raw)
In-Reply-To: <31210468ab0a3b26d1840341520b0129@ar.aichi-u.ac.jp>
> I examined tftpd.
>
> Current source code tftpd.c is this order:
> chdir(dir) -> listen -> setuser()
> But I suspect distributed binary:
Nicely spotted! I changed that code because, although it runs
fine on a cpu, it doesn't seem to work in a terminal. Now the
setuser happens after the listen completes but before any of
the work is done. I had presotto and ehg look at it and they
both believe it's safe the way it is now. In other words, the
process becomes none before it opens any files.
Sape
prev parent reply other threads:[~2005-01-27 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 15:53 [9fans] tftpd vs assumptions about user none? (to have or have not home dir) Axel Belinfante
2005-01-27 1:38 ` arisawa
2005-01-27 2:21 ` Sape Mullender [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=ca3eada2f0258994fbe573a288535c96@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).