From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: security - things to be aware of
Date: Thu, 19 Oct 1995 12:33:56 -0400 [thread overview]
Message-ID: <19951019163356.stAW8zmLFwE7mxE9GRttm0F7ogAZsurp8P8LEigYItE@z> (raw)
rob@plan9.att.com writes:
| One might argue what 'make available' means, but as things
| stand, and as we intended them, this means the source
| should not be installed on an Internet-visible machine,
| regardless of the account structure.
What does 'internet-visible' mean? If chmod 770 isn't enough, will it
be satisfactory to filter 9p traffic on our internet gateway, or to
disable "none" in the fileserver?
next reply other threads:[~1995-10-19 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-19 16:33 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-19 15:16 dhog
1995-10-19 13:26 rob
1995-10-18 15:57 Steve
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=19951019163356.stAW8zmLFwE7mxE9GRttm0F7ogAZsurp8P8LEigYItE@z \
--to=9fans@9fans.net \
/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).