From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] tftpd vs assumptions about user none? (to have or have not home dir)
Date: Thu, 27 Jan 2005 10:38:45 +0900 [thread overview]
Message-ID: <31210468ab0a3b26d1840341520b0129@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <200501261553.j0QFr9w28322@zamenhof.cs.utwente.nl>
Hello
I examined tftpd.
Current source code tftpd.c is this order:
chdir(dir) -> listen -> setuser()
But I suspect distributed binary:
term% ls -l /n/sources/plan9/386/bin/ip/tftpd
--rwxrwxr-x M 105 glenda sys 129444 Dec 27 13:33
/n/sources/plan9/386/bin/ip/tftpd
term% sum /n/sources/plan9/386/bin/ip/tftpd
ec968664 129444 /n/sources/plan9/386/bin/ip/tftpd
is not this order.
Because
term% ps
...
none 766 0:00 0:00 144K Open tftpd
..
If we compile the source that should be
term% ps
...
arisawa 722 0:00 0:00 120K Open 8.tftpd
...
I am uneasy if tftpd is running as hostowner.
because that can make security problem.
therefore I hope tftpd.c is coded in this order:
setuser() -> listen -> chdir(dir)
I want farther...
1. read only option
2. name space configuration
Kenji Arisawa
next prev parent reply other threads:[~2005-01-27 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 15:53 Axel Belinfante
2005-01-27 1:38 ` arisawa [this message]
2005-01-27 2:21 ` [9fans] tftpd vs assumptions about user none? (to have or have Sape Mullender
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=31210468ab0a3b26d1840341520b0129@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).