From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 security...
Date: Fri, 13 Feb 2004 15:18:07 +0000 [thread overview]
Message-ID: <1076685487.4985.505.camel@zevon> (raw)
In-Reply-To: <ab8642526016f58ade156ffac050da2e@plan9.escet.urjc.es>
> Here we have a fileserver which serves the kernel for the
> terminals on dhcp.
There's your problem.
Any net-booted OS is going to have the same problem.
You'll have to do at least one of (in no particular order):
a) use a secure dhcp service
b) stop using dhcp
c) stop netbooting
d) get a physically secure network
Sorry!
Dave.
P.S. Don't forget those DNS DOS hacks too!
(Sorry!)
next prev parent reply other threads:[~2004-02-13 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:04 Gorka Guardiola Múzquiz
2004-02-13 15:18 ` Dave Lukes [this message]
2004-02-14 4:05 ` boyd, rounin
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=1076685487.4985.505.camel@zevon \
--to=davel@anvil.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).